When is the free Nextcloud edition enough, and when does Enterprise pay off?
The community edition is enough for many self-hosted teams, and the decision does not turn on licensing. Nextcloud Server is AGPL-3.0 in both cases, so the question is whether you need contracted support, a longer maintenance lifecycle, early security patches and clustering help that the subscription adds. A team that can staff its own upgrades, has a tolerance for finding fixes through public channels, and runs a single instance can usually run the free edition well. Remember that the Enterprise tiers carry a 100-user minimum, so a smaller organization cannot buy them at all.
The free edition fits best when your own engineers can absorb the upgrade work. Nextcloud publishes a new major version every four months and supports each one for one year through monthly maintenance releases, so an unpatched install falls out of support quickly. Nextcloud does not allow skipping major releases, so you must step through each version, back up before every upgrade and disable third-party apps until they are confirmed compatible. If you cannot schedule that cadence, or your organization needs a contractual response time, the Standard tier's 1-year lifecycle and 2 business day reaction time become the first thing to weigh. Confirm current terms on the Nextcloud pricing page before you plan around them.
A paid tier starts to pay off when clustering, upgrade stand-by support or a 5-year lifecycle matter to your risk plan. Premium and Ultimate add support for clustered instances and upgrade stand-by support, which Standard lacks, and Ultimate offers support up to 24/7 with response times down to 1 hour. Ask Nextcloud GmbH in writing which of these you would receive, what hours apply and what a quote covers at your user count, because list prices change at the 200-user threshold. If your user count is below 100, the vendor directs you to Nextcloud One, a managed service hosted in Germany, which is a different commercial and hosting decision.
Which Nextcloud features are paid, and which are free?
This table sets the Nextcloud vendor's documented Enterprise split beside the community edition. Read the Standard, Premium and Ultimate columns as the published tier split, and treat community cells marked to confirm as questions to check in the Nextcloud documentation and your own configuration. The main takeaway is that the code stays AGPL in every tier, so the subscription buys support, lifecycle and hardening under the same license.
| Capability | Community edition | Standard | Premium and Ultimate |
|---|---|---|---|
| SAML authentication | Documented as a user authentication backend; confirm the app and setup steps | Included | Included |
| Password policies | Not listed in the vendor split; confirm what the community build enforces | Included | Included |
| Audit-ready logging | Not listed as audit-ready; confirm which logging app covers your audit needs | Included | Included |
| Workflow handling | Not listed in the vendor split; confirm available workflow apps | Included | Included |
| Nextcloud Guard monitoring | Not listed for community; confirm with Nextcloud before assuming it is absent | Included | Included |
| Security and stability patches | Monthly maintenance releases per major line, one-year support window | Early access to patches | Early access to patches |
| Maintenance lifecycle and reaction time | One year per major line; no reaction-time commitment | 1-year lifecycle; 2 business day reaction | 5 or more years; Premium 1 business day, Ultimate 1 to 24 hours |
| Clustered instance support | Not listed; confirm with Nextcloud if you plan clustering | Not included | Included |
| Extended support, consulting, upgrade stand-by | Community documentation and upgrade rules apply; no stand-by support | Not included | Included, with extended support sessions and custom integrations |
What licence, support and update terms apply to each edition?
Nextcloud Server stays under AGPL-3.0-only whether you run the community edition or a paid tier. What changes between them is support, maintenance lifecycle, response times and upgrade help, so the decision rests on how long you need fixes and who answers when something breaks.
Same licence in every tier
Nextcloud Server is licensed under AGPL-3.0-only, and the pricing page lists every Enterprise tier as fully open source under the AGPL. An Enterprise subscription buys support and lifecycle commitments, not a different licence or locked code. Confirm with Nextcloud GmbH in writing that the code you deploy is the same upstream release, and ask what contractual terms apply to any custom patches DeployOpen or your team adds.
Standard: one-year lifecycle
Standard includes a one-year maintenance lifecycle and a reaction time of 2 business days. That fits teams that can upgrade to each new major release within its support window. Check whether your change calendar can absorb an upgrade roughly every year, because the lifecycle does not extend automatically.
Premium and Ultimate: five years or more
Premium and Ultimate carry a maintenance lifecycle of five or more years. Longer support lets regulated teams plan fewer major upgrades, which matters where each upgrade needs testing, change approval and evidence. Ask Nextcloud to state the exact end date for the version you will deploy, since the pricing page gives only the minimum.
Reaction times from 2 days to 1 hour
Standard responds within 2 business days, Premium within 1 business day, and Ultimate offers reaction times of 1, 4, 12 or 24 hours. Reaction time is not resolution time. Ask which severity levels map to each reaction window, how a critical outage is raised outside business hours, and whether the window you pick is the one written into the contract.
24/7 support is an Ultimate term
Ultimate is the only tier that lists support up to 24/7. If your file service must stay available through nights and weekends, the 24/7 cover and the matching reaction window should be explicit in the order form. Teams that only need weekday cover can compare Premium against Ultimate on hours of support rather than on lifecycle alone.
Community releases every four months
The community edition receives a new major version every four months, and each major version gets one year of support through monthly maintenance releases. Nextcloud 35 was released on 16 September 2026 and reaches end of life in September 2027. Without a subscription, your team owns the upgrade cadence, the testing and the rollback plan for each major release.
How the community edition is maintained and what it lacks for enterprise use
The community edition is patched on a short, fixed cycle, and that cycle is the first thing a regulated team has to plan around. Nextcloud 35.0.2, 34.0.5 and 33.0.10 were all published on October 15, 2026, so three major lines receive maintenance at the same time. Each major release gets one year of monthly maintenance releases that address known critical bugs and security problems. Support for Nextcloud 33 ends in February 2027, 34 in June 2027 and 35 in September 2027. Build the calendar from these end dates, and confirm the current dates on the Nextcloud maintenance and release schedule before you commit to a upgrade window.
The upgrade rule shapes the work more than the patch cadence does. Nextcloud does not allow skipping major releases, so an installation on 33 must pass through 34 before it reaches 35. Each step needs a verified backup, a test run on a copy of production, and a decision about third-party apps, which stay disabled until their developers confirm compatibility. For an auditable process, record each step, the rollback point and the sign-off for every major. Nextcloud 36 is scheduled for 17 February 2027, which falls close to the end of support for 33, so a team on the oldest line may face two upgrades within a few months.
The subscription addresses the operational gaps that regulated teams usually write into their own requirements. The pricing page gives Standard a 1-year maintenance lifecycle and a 2 business day reaction time, while Premium adds a lifecycle of 5 or more years, a 1 business day reaction time, support for clustered instances and upgrade stand-by support. Early access to security and stability patches is included in every tier. If your policy sets a fixed response time, a minimum support lifetime or high availability through clustering, ask Nextcloud to confirm in writing which tier provides each one, and check that the community edition's one-year cycle meets your internal patch deadlines.
What does a Nextcloud Enterprise subscription cost per user?
This table sets the published Nextcloud Enterprise list prices against the costs a subscription does not cover, such as internal admin time and upgrade work. Read the price rows first, then the cost component rows, and use the final row to build the written quote you request from Nextcloud or a partner.
| Item | Published figure or cost driver | What to confirm or ask for |
|---|---|---|
| Standard, 100 or more users | 71.29 euros per user per year, net of VAT (Nextcloud pricing page) | Confirm the tier covers your user count and that the price is per user, per year, billed as recurring |
| Premium, 100 or more users | 104.99 euros per user per year, net of VAT (Nextcloud pricing page) | Confirm whether a 5-year-plus lifecycle and clustering support are included in the quoted line |
| Ultimate, 100 or more users | 204.75 euros per user per year, net of VAT (Nextcloud pricing page) | Confirm response times and 24/7 coverage are itemized, since these drive the tier choice |
| Lower rates from 200 users | 53.17, 81.99 and 183.75 euros per user per year for Standard, Premium and Ultimate, net of VAT (Nextcloud pricing page) | Ask whether the step-down applies to your full seat count or only to seats above 200 |
| 100-user minimum and recurring fee | Subscriptions start at 100 users and renew annually as a recurring cost, so a 60-user team cannot buy a tier directly | If you are under 100 users, ask Nextcloud which path applies, and compare the Nextcloud One managed option |
| Internal admin time | Your staff run upgrades, monitor the server and handle user issues, a cost that continues whether or not you hold a subscription | Estimate hours per month with your own team and record who owns patching and upgrades |
| Infrastructure and backups | Servers, storage, database, backup and monitoring are paid to your cloud or data center provider, regardless of tier | Ask whether the quote assumes your existing infrastructure or includes any hosting, which Nextcloud states it does not offer |
| Third-party app compatibility testing | Each app update or major upgrade needs testing, and Nextcloud advises disabling third-party apps until confirmed compatible | Budget test time in a staging environment and confirm which apps your team depends on |
| Implementation and upgrade services | Consultants, integrators or your own staff are paid for setup, SAML or LDAP integration, and one-major-version-at-a-time upgrades | Request a fixed-scope statement of work listing deliverables, timelines and what is excluded |
Which team should choose the community edition, Standard, Premium or Ultimate?
Nextcloud Enterprise subscriptions are sold only from 100 users, so a team below that count cannot buy one directly. Nextcloud's pricing page points organizations with fewer than 100 users to Nextcloud One, a managed service that the vendor says is hosted in Germany and operated by epiKshare GmbH. That route moves hosting and operations to a third party, which changes the data location and control questions, not just the price.
- Subscription floor: Enterprise tiers start at 100 users, so smaller teams are not offered the paid tiers at all.
- Vendor-stated route: Nextcloud One, operated by epiKshare GmbH, is the path the pricing page names for smaller organizations.
- Hosting change: A managed service means someone else runs the servers, so confirm where data sits and who holds administrator access.
- Self-hosting option: A team that wants to keep the server in its own infrastructure stays on the AGPL community server and carries the upgrade and patch work itself.
- Lifecycle awareness: Community releases are supported for one year through monthly maintenance, so plan a major upgrade roughly every four months.
Before you choose, confirm the current terms for Nextcloud One directly with the provider and check whether the community server meets your hosting requirements.
A team that already runs PHP, database and web server stacks, and that can apply a major upgrade every few months, can run the AGPL community edition without a subscription. The code is the same AGPL code in every tier, so the subscription buys support, lifecycle and response commitments, not extra features in the core server. The condition that matters is staffing: someone must own patching, backups and upgrades on a fixed rhythm.
- Same code base: The pricing page lists every tier as open source under the AGPL, so the community server is not a reduced build.
- Upgrade discipline: Nextcloud does not allow skipping major releases, so each upgrade goes one major version at a time.
- Pre-upgrade steps: Back up before every upgrade and disable third-party apps until they are confirmed compatible.
- Deployment help: Nextcloud All-in-One is the official installation method and bundles caching, PostgreSQL and backups, which reduces setup work for a small in-house team.
- Support gap: Without a subscription, fixes come through community channels and your own testing rather than a contracted response time.
Check whether your team can hold a monthly patch window and a major upgrade cycle before you rely on the community edition for production.
A regulated organization often needs a written answer to a simple question: who responds, and how fast, when a production file service fails. This is where a subscription matters. Nextcloud's pricing page gives Standard a 2 business day reaction time, Premium 1 business day, and Ultimate reaction times of 1, 4, 12 or 24 hours with support up to 24/7. The tier choice then depends on how quickly your incident and audit procedures require a response.
- Standard response: A 2 business day reaction time and a 1-year maintenance lifecycle suit teams whose service targets allow a slower response.
- Premium response: A 1 business day reaction time and a lifecycle of 5 or more years suit teams that need longer support continuity.
- Ultimate response: Reaction times down to 1 hour and support up to 24/7 suit services with overnight or weekend obligations.
- Security features: All tiers include SAML authentication, password policies, audit-ready logging and early access to security patches.
- Evidence: Subscriptions do not issue audit reports, so the assessor still needs your own control evidence.
Ask the vendor for the contract's exact reaction times, escalation path and lifecycle dates, and map them to your own recovery commitments before signing.
Clustered and multi-site deployments are where the pricing page draws its clearest line. Premium and Ultimate add support for clustered instances, along with extended support sessions, custom consulting and integrations, and upgrade stand-by support, which Standard does not include. If your design runs several application nodes behind a load balancer or spans sites, the choice narrows to Premium or Ultimate on the vendor's stated terms.
- Clustered support: Only Premium and Ultimate list support for clustered instances.
- Upgrade stand-by: Premium and Ultimate include upgrade stand-by support, which matters when a major upgrade touches several nodes at once.
- Custom integrations: Consulting and integration work is included in the higher tiers, which helps when directory or storage integrations are non-standard.
- Database choice: Nextcloud 35 supports MySQL 8.4 or 9.7, MariaDB 10.11 to 12.3 and PostgreSQL 14 to 18, and Oracle requires an enterprise subscription.
- Ultimate versus Premium: Ultimate adds faster response and 24/7 coverage, which matters only if the cluster carries overnight obligations.
Confirm with the vendor how each tier covers your exact topology, including storage backends and database, before you size the subscription.
How to move from the community edition to Enterprise, or back
The sequence confirms your current major version and its support window, moves the instance onto a subscription configuration, and uses single-major-version upgrades with backups and app testing to keep the change controlled. Because the code is the same AGPL code in both editions, most of the work is configuration, support onboarding and change control.
Confirm the current major version and support end date
The administrator records the Nextcloud major version the instance runs, its installed point release and the end-of-life date for that line, using the maintenance and release schedule. Nextcloud supports each major version for one year through monthly maintenance releases, so the date shapes how urgently the upgrade path has to be planned. The step is done when the team has a written record of the version, the support end date and the list of installed apps, with each app's maintainer noted. Confirm the exact support terms for your version with Nextcloud before relying on them.
Decide the tier and sign the subscription
The buyer compares the Standard, Premium and Ultimate tiers against the lifecycle, response time, clustering and upgrade support the organization needs, and checks that the user count meets the 100-user minimum. Procurement receives a quote built from the written scope, which should state the user count, the tier, the billing term and whether the price is net of VAT. Subscriptions are the only paid element, so the signed order and the account that will open support tickets should be confirmed in writing before the configuration work starts. For lower user counts, ask Nextcloud which option applies, since the pricing page points smaller organizations to a managed service instead.
Apply the Enterprise configuration to the existing instance
The platform team activates the subscription key and enables the Enterprise-only features the organization chose, such as SAML authentication, password policies, audit-ready logging and Nextcloud Guard monitoring, using the vendor's configuration guidance. The Enterprise build contains the same source, so the change is mostly settings and enabled components rather than new software. Test each feature in a staging copy first, and record the configuration changes in version control. The step is complete when a test user can sign in through the new identity path and the audit log records the test events.
Plan a single-major-version upgrade path
If the current version is not the one the subscription targets, the team maps each intermediate major release, since Nextcloud does not allow skipping major releases during upgrades. Each hop is scheduled as a separate change with its own rollback point, and the team checks that database, PHP and web server versions still meet the system requirements for the target release. The output is a dated upgrade plan signed off by the change board, with each hop listed as a discrete item. Confirm the number of hops and the order with Nextcloud support, because the path depends on the starting version.
Back up before every upgrade
Before each major or point upgrade, the operator takes a full backup of the data directory and the database, stores it outside the instance and verifies that it can be restored. Nextcloud's upgrade guidance calls for a backup before every upgrade, so this is a required gate rather than an optional safeguard. The step is complete when a restore has been tested on a separate host and the team has recorded the backup identifier in the change ticket. Backup tooling is the operator's choice, and the team should confirm which backup method its storage setup supports.
Test third-party apps against each target version
The administrator disables third-party apps before each upgrade, then re-enables them one at a time only after the app maintainer confirms compatibility with the target release. Apps that are not confirmed stay disabled, and the business owner is told which features are affected. Test results go into the change record, with each app marked compatible, pending or removed. The step is done when every app that the business uses is confirmed for the target version or has an agreed replacement or removal plan.
Onboard support and set change control
The organization names the people who can open support requests, sets the escalation path and runs a short onboarding session with the vendor's support team so responses match the reaction times in the chosen tier. Change control then requires a ticket, a tested backup and an app compatibility record for every upgrade. The output is a support contact list, a published change calendar and a runbook that the on-call team can follow. Moving back to the community edition follows the same sequence in reverse: the subscription is ended, the Enterprise-only settings are reviewed for removal, and the instance continues on the AGPL code it already runs. Confirm with Nextcloud what happens to enterprise-only settings and support access when a subscription ends.
What do buyers ask before paying for Nextcloud Enterprise?
Do I need an Enterprise subscription if Nextcloud is AGPL licensed?
No. The code is AGPL-3.0 under every tier, so a self-hosted Nextcloud can run and be modified without a subscription. What you pay for is the subscription itself: support, a maintenance lifecycle, early access to security and stability patches, and features such as SAML authentication, password policies, audit-ready logging and Nextcloud Guard monitoring. Ask whether those services matter to your change process and audit evidence. If your team can handle patching, upgrades and incident response on its own, the community edition may be enough. If you need a contractual response time or a longer supported lifecycle, the subscription is the purchase.
How much does Nextcloud Enterprise cost per user, and why does the 100-user minimum matter?
The Nextcloud pricing page lists per-user, per-year list prices for 100 or more users of 71.29 euros for Standard, 104.99 euros for Premium and 204.75 euros for Ultimate, net of VAT. From 200 users the list prices fall to 53.17, 81.99 and 183.75 euros. Subscriptions start at 100 users, so a 40-person team cannot buy a tier at all. Multiply the per-user price by your headcount and tier, then ask the vendor for a written quote, since list prices may not match your final terms. Teams below 100 users are pointed to Nextcloud One, a managed service, rather than a self-run subscription.
How long does it take to move to Nextcloud Enterprise or upgrade an existing instance?
The subscription itself has no install step, but the upgrade path does. Nextcloud does not allow skipping major releases, so an instance several versions behind must be moved one major version at a time, with a backup before each step. Nextcloud 35 was released on 16 September 2026, Nextcloud 34 is supported until June 2027 and Nextcloud 33 until February 2027, so the number of hops depends on your current version. Duration depends on instance size, database, third-party apps and how many upgrades remain. Ask for a written scope and timeline before work starts, and confirm which apps are compatible with each target version.
What must our team supply to run Nextcloud well, with or without a subscription?
The team must provide administration skills for the web server, PHP runtime and database, plus a backup process and recovery testing. Each major upgrade requires a fresh backup, disabling third-party apps until they are confirmed compatible, and a change window long enough to finish the upgrade and check the result. Directory integration through the LDAP app, OpenID Connect or SAML also needs an identity owner who can maintain attribute mappings. Keep a named on-call contact for incidents. A subscription adds vendor support hours and response times, but it does not replace these internal tasks.
Can an outside partner run the community edition for us instead of buying Enterprise?
Yes, a partner can plan, install, harden, back up, upgrade and document a self-hosted Nextcloud inside your own cloud accounts, data centers or air-gapped networks. DeployOpen works this way for open-source platforms, usually under a fixed scope agreed in writing before work starts, with ongoing support available as a retainer. That arrangement covers operations work, but it does not give you Nextcloud GmbH's vendor support or the Enterprise maintenance lifecycle. Ask any partner which upgrade and patch windows they commit to, who responds to incidents, and whether the contract names specific deliverables. DeployOpen does not publish a price list, so a quote follows from the scope.
Which Enterprise features matter for clustering and high availability?
Premium and Ultimate include support for clustered instances, along with extended support sessions, custom consulting and integrations, and upgrade stand-by support. Standard does not include clustered instance support according to the pricing page. If your design runs multiple application nodes, confirm with Nextcloud which tier covers your topology before you buy, and confirm how your database, object or local storage and cache layers are shared between nodes. Ask whether the vendor's clustering support applies to your exact architecture.
What does Ultimate add over Premium, and when is it worth the difference?
Premium gives a maintenance lifecycle of 5 or more years, while Ultimate also gives that lifecycle with support up to 24/7 and reaction times that go down to 1 hour, compared with reaction times of 1, 4, 12 or 24 hours. The price difference is 204.75 minus 104.99 euros per user per year at list price. Ultimate suits organizations whose outage tolerance is measured in hours and who must show a 24/7 support path to auditors or regulators. Premium may be enough when a business-hours response and a multi-year lifecycle cover your risk. Confirm the reaction time you need for your most critical services in writing.
How DeployOpen scopes and supports either Nextcloud edition
Whichever Nextcloud edition you run, the server code is the same AGPL-3.0 software, so the real questions are who plans, hardens, backs up and upgrades it. DeployOpen works in that operations layer inside your own infrastructure, under written scope. Subscription terms and vendor support stay with Nextcloud GmbH.
Who DeployOpen is and is not
DeployOpen is a Chainscore Labs company that plans, implements, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms in your own cloud accounts, data centers or air-gapped networks. DeployOpen is not Nextcloud GmbH, is not a reseller, and is not a certified partner of Nextcloud. Route Enterprise subscription, tier and pricing questions to Nextcloud directly.
Fixed-scope written agreements
Most engagements start with a written scope that names the Nextcloud version, the database and web stack, the apps in use, the identity source, the backup targets and the deliverables and timelines. Ask for the list of exclusions in writing. If you stay on the community edition, the scope should still name who owns security patch application and major version upgrades.
Hardening and identity integration
Hardening covers the server configuration, database access, administrator accounts and the identity integration you choose, such as LDAP or Active Directory, OpenID Connect or SAML. Confirm which SAML or directory features your chosen path needs, because the Enterprise tiers list SAML authentication as an included feature while community deployments depend on the apps and configuration you set up.
Backups and major upgrades
Nextcloud does not allow skipping major releases, so each upgrade is a planned step with a backup taken first and third-party apps checked for compatibility. Define in the scope who runs the backup restore test, who signs off each step, and how long a rollback window is kept. These are recurring tasks, so ask whether they sit in a fixed project or a retainer.
Retainers for ongoing support
Ongoing patching, upgrade windows, monitoring reviews and testing are typically handled through a retainer, separate from the initial build. Ask what response times the retainer commits to, what is covered outside business hours, and whether vendor tickets are handled by DeployOpen or passed to Nextcloud. Nextcloud subscription response times are a vendor matter that you confirm with Nextcloud.
Documentation and compliance evidence
DeployOpen can document configuration, runbooks and control evidence for your own compliance assessments. DeployOpen does not issue audit reports, attestations or certifications, and independent auditors make those determinations. Ask the assessor which evidence they need before scope is written so the documentation matches what they will test.
