Box cost vs self-hosted Nextcloud

Does self-hosted Nextcloud cost less than Box for your users?

If your Box renewal is driving this review, the short answer is that the Nextcloud community edition has no license fee, so the comparison is really between Box subscriptions and the infrastructure, implementation, upgrade and staff time you would carry yourself. Nextcloud Hub is licensed under the AGPL and is free to self-host. Paid Nextcloud Enterprise support is optional, and it is what you would add if you need vendor maintenance, longer support windows or clustered instance support. The supplied list prices for Nextcloud Enterprise, per user per year for 100 or more users, start at 71.29 euros for Standard, 104.99 euros for Premium and 204.75 euros for Ultimate, according to the Nextcloud pricing page. Enterprise is sold with a 100-user minimum, so smaller teams should confirm the options with Nextcloud directly. For Collabora Online, the Business plan is listed at 3 euros per user per month for up to 99 users on the Collabora Online pricing page. CODE, the free edition, is not recommended for production by Collabora, so plan for Business or Enterprise support if editing is business-critical.

Box plan prices, per-user rates and the file size and version retention limits for each tier were not part of the research for this page. Take those figures from your own Box order form or admin console, including any add-ons for storage, security or governance, and compare them line by line with the Nextcloud and Collabora costs above. Ask Box for the exact per-user cost at your seat count and any multi-year discount, since those change the result.

The answer depends on three things: user count, total data volume and how much vendor support you need. Per-user subscriptions scale with headcount, while self-hosted storage scales with terabytes, backups and replicas, so a large group with modest data may favor Nextcloud differently than a small group with heavy media use. Model your own totals over three years, and include one-time costs such as migration, identity integration and a test environment, plus recurring costs such as hosting, backup storage, monitoring, the Nextcloud major version upgrades (one major release at a time) and the staff hours to run them. Ask any implementation partner for a quote built from written scope, so the components can be compared with your Box invoice.

Which cost components sit on each side, and which recur

This table lists each cost component of running Box and running Nextcloud on your own infrastructure, with who is paid and whether the cost is one-time or recurring. Box prices and tier limits are not set out here, so confirm them with Box. The main takeaway is that self-hosting moves most recurring cost from a vendor invoice to your storage, staff time and any support you choose to buy.

Cost component	Box side	Self-hosted Nextcloud side	One-time or recurring
Subscription or license	Per-user plan. Confirm current price and tier limits with Box.	Nextcloud Server is AGPL-3.0 and free to self-host. Enterprise starts at 71.29 euros per user per year (Nextcloud pricing page).	Recurring, if you buy Enterprise or Collabora Business
Infrastructure	None on your side. Box runs the platform.	Servers or VMs, database, PHP and web server. Collabora production pods are sized at 8 cores and 8000 MiB each (Helm chart README).	Hardware one-time or recurring if cloud-hosted
Storage growth	Included storage depends on the plan. Confirm pooled or per-user limits and overage terms.	Disks you buy or rent. Version history, trash and previews add capacity over time.	Recurring
Backups	Retention is set by Box. Confirm what you can export and how long versions are kept.	Backup targets, offsite copies and restore testing are yours. All-in-One bundles BorgBackup-based backups.	Recurring storage, one-time setup
Implementation	Admin setup only. Little or no external work for most teams.	Installation, LDAP or SSO, Collabora integration and hardening. Fees follow the written scope from DeployOpen or another implementer.	One-time
Migration	Bulk download over FTPS or SFTP. Files over FTPS are capped at 32 GB (Box Support).	Import, permission mapping, link rebuilds and user checks. Mostly staff time during cutover.	One-time
Support	Included by plan. Confirm response times and any paid support tiers.	Community support is free. Enterprise adds maintenance and response commitments. Collabora Business is 3 euros per user per month up to 99 users.	Recurring, if you buy support
Upgrades	Vendor-managed. Your team validates admin and integration changes.	A new Nextcloud major every four months, each supported for one year. Upgrade one major at a time, with backups, and check apps first.	Recurring staff time
Internal skills	Admin console and sharing policy knowledge.	Linux, PHP, database, web server and backup operations. Kubernetes skills if you run Collabora there.	Recurring staff time or outsourced support

What moves the Box and Nextcloud totals most

Six drivers decide whether a move to self-hosted Nextcloud with Collabora Online lowers total cost or only shifts it. Each one pushes Box and the self-hosted side in different directions, so check them against your own user counts, data volumes and staffing before comparing quotes.

User count and edition thresholds

Nextcloud Enterprise carries a 100-user minimum, so a team just under that line may pay for community support only, while crossing it adds a per-user subscription. Collabora's Business plan covers up to 99 users at 3 euros per user per month, and the Enterprise plan for 100 or more users is quoted with volume discounts. Ask the vendor how each price changes at 100 users and whether licences are counted by named user or by active account.

Data volume and growth

Box charges by plan storage and per-file limits, so growth may push you to a higher tier. On self-hosted Nextcloud, the cost moves to disks, object storage and backup copies, which grow with every retained version. Estimate current stored terabytes, annual growth and the number of versions kept, then ask Box for its storage terms at your expected size.

Edition and support level

Community Nextcloud is free to self-host, but production support, maintenance lifecycles and response times come from Nextcloud Enterprise tiers. Box support is included in its plans, so the comparison should match support levels, not list prices. Ask Nextcloud which tier covers the response times and maintenance period you need, and ask Box which support tier applies to your contract.

Availability and maintenance windows

A hosted service carries uptime commitments on the vendor side, while self-hosting makes you pay for redundancy, clustering and patch windows. Collabora notes that horizontal autoscaling is disabled and that replicas are set manually, with load balancers routing by WOPISrc, which adds design and operations work. Confirm the uptime you need, whether a clustered Nextcloud setup is required, and how many engineer hours a monthly maintenance window will take.

Version retention policy

Box plan tiers set how much version history you keep, and longer retention raises both Box fees and storage on your side. Self-hosted Nextcloud keeps whatever your own policy and disk allow, so a retention decision becomes a direct storage cost. Write down the retention rule you need for compliance, then ask Box which retention limits apply to your tier and whether extending them requires a higher plan.

Skills already on staff

A team that already runs PHP applications, Linux servers, PostgreSQL and reverse proxies will carry Nextcloud upgrades and backups at lower cost. Nextcloud does not allow skipping major releases, so each upgrade is a planned, staged task that needs a backup first and a review of third-party apps. Count the people who can own upgrades and restores, and decide whether to buy support or outsource that work.

Where storage growth and backups drive the recurring bill

Storage growth is the cost line that compounds fastest in a self-hosted Nextcloud estate. On your own infrastructure you pay for capacity per terabyte, whether that is a SAN, a hypervisor volume, an object store or a block volume from a cloud provider. Every file a user uploads is only the first charge. File versions kept in Nextcloud, items sitting in the trash for the retention period you configure, previews and sync copies all consume the same pool. Before you size anything, pull a sample of your current Box usage and ask which version history and deleted-item retention your current plan actually includes, because Box retention depends on the tier. Confirm that figure in writing with Box, then model Nextcloud storage against it rather than against assumptions about file counts.

Backups are the second multiplier, and they are a separate purchase from the application. A common pattern is to keep at least one copy of the data outside the primary storage, which means paying for backup capacity that grows with retention depth, not just with live data. Nextcloud All-in-One bundles BorgBackup-based backups, so the software cost of backup is zero, but the target is not. Size the repository on the backup host or the object store, and budget for the daily and monthly retention you need to meet your recovery commitments. Also plan for restore testing, since untested backups are an expense without a guarantee.

The recurring bill therefore depends on decisions you control: how many versions Nextcloud keeps, how long trash is retained, how deep backups go and which storage tier holds each layer. Ask your infrastructure team to price those components per terabyte per month, and ask any implementation partner to show the storage and backup assumptions in the written scope. Keep the version and retention settings in the same model as the Box comparison so the two bills can be checked line by line.

How to build the Box versus Nextcloud model with your own numbers

This sequence turns Box and Nextcloud into a side-by-side model built on your own user counts, storage and version history, so each line item traces to a source you can defend in a renewal or board discussion.

Export your current Box inventory
Pull user counts, active storage, file counts and version history from the Box admin console and its reports. Separate active users from licensed seats, and record how much content sits in folders with long version chains, because version retention drives storage growth more than user count does. Done when you have one sheet listing users, total stored gigabytes, file counts and the largest folders by size and version depth, dated for the export.
Confirm Box tier limits and renewal terms in writing
Ask your Box account team to state in writing the per-user price, the plan tier that applies to you, the per-file upload limit, the version retention setting for your tier, storage allocation, and the renewal and price-increase terms. Do not rely on public plan pages alone, because limits and entitlements can differ by contract. Done when you hold a written statement you can cite line by line in the model.
Size Nextcloud and Collabora resources
Use the Nextcloud 35 system requirements to choose a supported database, PHP and web server combination, then size CPU, memory and storage from your user and file inventory. For Collabora Online, start from the Helm chart guidance on production resource limits per pod (8 CPU cores and 8000 MiB of memory as limits, 4 cores and 6000 MiB as requests) and the rule that replicas are set manually. Multiply pods by the number of collaboration instances you plan to run. Done when you have a bill of materials for compute, memory, database, object or block storage and load balancing, each tied to a documented requirement.
Add subscription options with their list prices
Decide whether you will run Nextcloud Hub on the community code, use Nextcloud Enterprise, or use Nextcloud One managed hosting if you have fewer than 100 users. For Enterprise, the Nextcloud pricing page lists Standard, Premium and Ultimate tiers with a 100-user minimum and list prices from 71.29, 104.99 and 204.75 euros per user per year for 100 or more users. For Collabora, the Business plan lists at 3 euros per user per month for up to 99 users, and Enterprise is quoted by volume. Record the source date for each price, because list prices change. Done when every subscription line shows its vendor, tier, unit, list price and source.
Cost backup and disaster recovery
Price backup separately from the application. Nextcloud All-in-One includes BorgBackup-based backups, so compare that option with your existing backup platform, and include backup storage sized to your data growth plus retention. Add the recovery test effort and the backup step required before each Nextcloud upgrade, since the upgrade documentation requires a backup each time. Done when you can state recovery point and recovery time targets from your own policy and the matching storage and labor lines.
Estimate migration and implementation through written quotes
Use the Box bulk export over FTPS or SFTP to scope content transfer, noting the 32 GB per-file FTPS limit, and list separately the work to map permissions, shared links, integrations and identity. Ask implementation partners for a fixed-scope written quote that names deliverables, exclusions and acceptance checks. Ask internal teams to state the hours they will contribute. Done when you have one quote or internal estimate per workstream, with assumptions stated and no figures carried into the model that you cannot trace.
Run totals over a multi-year horizon
Build a sheet with one-time lines (migration, implementation, hardware, initial licensing, and any staff training) separate from recurring lines (Box renewals, storage growth, Nextcloud or Collabora subscriptions, hosting, backup storage, support and upgrade effort). Apply your Box renewal terms and your storage growth assumption to each year, and mark every assumption as a labeled estimate. Illustrative example: if storage grows each year, the recurring storage line grows with it while the Box line changes only at renewal. Done when the model shows cumulative cost per year for both options, every assumption is labeled, and you can explain each total to finance.

Which Nextcloud and Collabora subscription options change the bill

Nextcloud Hub is licensed under the AGPL and is free to self-host, so the software license itself carries no fee. Your cost in this model is the infrastructure, the people who install, patch and upgrade the platform, and any external help you buy by the job. Nextcloud publishes a new major version every four months and supports each for one year, so your team must plan a recurring upgrade cycle that moves one major version at a time.

Software fee: None for the AGPL community code, with no per-user charge.
Operations labor: Your staff or a partner handles patching, monthly maintenance releases, backups and monitoring.
Upgrade cadence: Major versions arrive about every four months, and skipped major releases are not supported.
Support path: Vendor support is not included, so you rely on community resources, internal expertise or a services contract.
Recurring costs: Storage growth, backup capacity and staff time continue every year.

Confirm with your team how many hours per month of platform operations you can staff, and whether you need a written support agreement before going live.

Costs teams forget on each side

The subscription line is the easiest number to compare and the least complete. Exit costs and retention limits on the Box side, and upgrade, scaling and staffing work on the self-hosted side, are where most total cost of ownership comparisons go wrong. The cards below list items to price and confirm before you compare totals, whichever way you decide.

Box exit and bulk export effort

Leaving Box means bulk downloading content over FTPS or SFTP, which Box describes as intended for bulk migration and occasional bulk download. FTPS transfers are capped at 32 GB per file, so large files need a separate route. Budget time for re-mapping collaborator permissions, shared links and integrations, since a plain download does not carry them. Ask Box which export options apply to your plan and contract before you set a cutover date.

Box retention and version limits

File size limits and version retention in Box depend on the plan tier, so the number you pay for today may not match what your teams rely on. Check how many versions each tier keeps, and whether older versions you need for audit or legal holds sit inside that window. Ask your account team to confirm these limits in writing for your exact contract.

Nextcloud upgrade path

Nextcloud does not allow skipping major releases, so each upgrade moves one major version at a time, with a backup taken before every step. Third-party apps must be disabled until their compatibility is confirmed, which can leave features unavailable during the window. Plan the release cadence, since Nextcloud publishes a new major version every four months and supports each for one year.

Collabora replica planning

Collabora's Helm chart disables horizontal pod autoscaling because scaling breaks collaborative editing and copy and paste, so replica counts are set by hand. Load balancers must route by the WOPISrc parameter so everyone editing one document reaches the same pod. Size the pods against the chart's recommended production resources, and test failover before you rely on it for live editing.

On-call coverage for an internal service

Once Nextcloud holds production files, someone must answer for sync failures, storage outages and failed upgrades, including outside business hours. Your staff cost for this coverage is recurring and often absorbed silently by existing IT teams. Compare it against Box's vendor-run operations, and decide whether you need an internal rota, a retainer or a paid support tier such as those listed on Nextcloud's pricing page.

Testing time for each upgrade

Each upgrade needs a staging copy, a restore test from the latest backup, a check of every third-party app and a user acceptance pass on Collabora editing. That work repeats several times a year because of the major release cadence and monthly maintenance releases. Ask for the testing effort in your scope, and record how many hours each cycle takes so you can compare it with the Box cost you avoid.

Questions buyers ask about Box and self-hosted Nextcloud costs

What do I need from my own data before a Box vs Nextcloud cost comparison means anything?

The comparison only holds if you know your own numbers: total stored data, number of named users and external collaborators, average and largest file sizes, how many versions you keep, and how much data grows each year. Box pricing depends on the plan tier, and file size limits and version retention also vary by tier, so pull those values from your current order form. On the Nextcloud side, the cost is driven by storage you provision, backup copies, server and database hosting, and staff time. Without the storage growth rate and backup retention you need, any total cost figure is guesswork. Build the model from your own usage data, then ask providers to price against it.

Can our team run Nextcloud without outside help, and what skills does it need?

A team with Linux administration, web server, PHP and database experience can run Nextcloud in-house, but it needs to own several ongoing tasks. These include applying major and monthly releases, taking backups before every upgrade, managing the database (MariaDB, PostgreSQL or MySQL), configuring caching and cron jobs, and integrating directory authentication. Collabora Online adds container or Kubernetes operations, and its Helm chart notes that replicas are set manually and load balancers must route by WOPISrc. Nextcloud All-in-One can simplify installation and bundles backups and ClamAV. Assess your team's capacity honestly, and consider whether a retainer for upgrades and monitoring is a better fit than full in-house operation.

How long does a migration from Box to Nextcloud take, and what changes the duration?

The duration depends on the volume of content, the number of users and shared links, how much version history you choose to carry over, and how cleanly permissions map to Nextcloud shares and groups. Bulk export from Box uses FTPS or SFTP for Business and Enterprise customers, and FTPS transfers are limited to 32 GB per file, so large or oversized files need a separate path. Box Notes and third-party integrations also need to be replaced. Instead of a fixed number, ask the provider to tie its timeline to a written inventory of your data and to a pilot group. The sibling migration guide walks through these steps in more detail.

How often do Nextcloud major versions arrive and how long is each one supported?

According to the Nextcloud maintenance and release schedule, Nextcloud publishes a new major version every four months and supports each one for one year with monthly maintenance releases for critical bugs and security problems. The schedule lists Nextcloud 35 (Hub 26 Summer) as released on 16 September 2026 with end of life in September 2027, Nextcloud 34 supported until June 2027, Nextcloud 33 until February 2027, and Nextcloud 36 (Hub 27 Winter) scheduled for 17 February 2027. Because you cannot skip major releases, plan a regular upgrade cadence, back up before each step, and disable third-party apps until they are confirmed compatible. Check the release schedule before you set a plan.

What does a Nextcloud Enterprise subscription add beyond the community edition?

Nextcloud Hub is free to self-host under the AGPL, and the Enterprise subscription is a paid offering from Nextcloud GmbH for support and additional features. Nextcloud sells Standard, Premium and Ultimate tiers with a 100-user minimum. According to Nextcloud's pricing page, Standard includes one-year maintenance, Premium adds a maintenance lifecycle of five or more years, extended support hours and clustered instance support, and Ultimate adds support up to 24/7 with response times down to one hour. Enterprise subscriptions also cover Oracle Database support, which the system requirements limit to that tier. Ask whether each tier's features match the controls and support hours your organization needs, and confirm current pricing directly with Nextcloud.

What should we ask a provider to include in a fixed-scope quote for a Nextcloud move?

A fixed-scope quote should list the deliverables, scope boundaries and timeline in writing before work starts. Ask the provider to specify the environment where Nextcloud and Collabora will run, the number of users and data volume covered, the migration method and the handling of version history, permissions, shared links and Box Notes. Request the items that recur after go-live, such as upgrade support, backup testing, monitoring and security patching, and whether they are included or sold as a retainer. Confirm which testing, hardening and documentation are included, and what acceptance criteria close the work. DeployOpen plans and implements these engagements against a written scope, and it does not publish a price list, so a quote follows from that scope.

Does a self-hosted setup remove the need to pay for Collabora Online licenses?

Collabora Online is licensed under MPL-2.0, and CODE is the free development edition, but Collabora describes CODE as suited to testing, home use or small teams and not recommended for production. For production, Collabora's pricing page lists a Business plan at 3 euros per user per month for up to 99 users, which includes long term support, an SLA, signed security updates and customer portal access. The Enterprise plan for 100 or more users is quoted with volume discounts. Cost planning should therefore separate the free software from the support and update commitment your risk team requires. Confirm current terms with Collabora before you budget.

How DeployOpen scopes a fixed-price Nextcloud implementation

DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted Nextcloud inside your own cloud accounts, data centers or air-gapped networks. Most engagements are fixed-scope, so the scope, deliverables and timelines for the Box exit are agreed in writing before any work starts.

How we scope

We inventory Box plans, user counts, file sizes, version retention needs and external sharing before quoting.
The written scope names which content, folders, users and integrations move to Nextcloud and which stay behind.
Collabora Online editing, Box Notes replacement and identity integration are listed as separate, confirmable deliverables.
Ongoing support, upgrades and continuous testing can be added as a retainer after handover.

How we build

We deploy Nextcloud in your environment and select a supported database, PHP and web server combination for the chosen release.
Collabora Online is configured for WOPI editing and sized for your concurrent editors, with the replica approach documented.
Directory integration through LDAP, OpenID Connect or SAML is configured and tested against your own identity source.
Backup jobs, antivirus scanning and upgrade paths are built and tested before any user content is loaded.

How we hand over

Migration runbooks record the export, import, permission mapping and shared link rebuild steps used for your content.
Architecture, configuration and backup and restore procedures are documented for your operations team.
Acceptance tests confirm file integrity, permissions, editing and sharing against the criteria in the written scope.
We prepare the controls and evidence that your compliance assessors may ask to review, without issuing any attestation.

How we support

Retainer support can cover monthly maintenance, upgrades to each supported Nextcloud major release, and security patching.
Upgrades follow Nextcloud's one-major-version-at-a-time rule, with backups taken before every step and third-party apps tested.
Continuous security testing of the deployed applications and APIs can run alongside the retainer if it is agreed in writing.
Your team keeps the pricing and support options from Nextcloud and Collabora in view when deciding on enterprise subscriptions.