Nextcloud or Pydio Cells: when each platform fits a regulated file estate
Choose Nextcloud when you want one AGPL server that you can extend with apps and upgrade on a published schedule, and Pydio Cells when your priority is a published per-tier price that puts SSO, audit logs and access controls in the paid Connect and Enterprise editions. A team consolidating file shares for a regulated estate usually needs SSO, audit and an upgrade path it can support for years, and both platforms can meet those needs, but they pay for them in different places. The decision turns on five questions: how many users you have, how your identity provider must integrate, how much app extensibility you want, whether your database standard is already set, and whether your budget favors a subscription per user or a per-tier price.
Start with identity and audit. Nextcloud's LDAP app and its documented OpenID Connect and SAML backends are part of the community server, so confirm which of those your directory and sign-in flow require before you price anything. On the Pydio side, AD/LDAP, SSO through OpenID Connect, OAuth2, SAML or Azure ADFS, and white-labelling sit in the Connect tier, while role- and rule-based access control, multi-factor authentication and exportable audit logs sit in Enterprise. Check your audit and MFA requirements against those tier boundaries early, because they decide your budget line more than the server does.
Pydio's free Home edition is for home use and evaluation, so it is not an enterprise option for a regulated estate. Treat Cells v5 as a work-in-progress branch: the published release line you can deploy today is v4.4.18, and the Cells database requirement is MySQL 5.6 or higher or a MariaDB equivalent. Nextcloud 35 supports a wider set of databases, and its release cadence means each major line gets one year of maintenance, so plan your upgrade calendar around that. Confirm with Pydio how a v5 migration would work before you commit to a long-term architecture.
Which scenarios favor Nextcloud and which favor Pydio Cells
This table maps five common team situations to the platform that fits better and the condition that makes that fit hold. Read each row against your user count, directory setup, required apps and audit obligations, because the answer often changes when one of those conditions changes.
| Scenario | Better fit | Reason and the condition that makes it hold |
|---|---|---|
| Small team, a few dozen users, no directory | Nextcloud | The community server is AGPL-3.0 with no per-user fee, and Pydio Cells Home is free only for home use and evaluation. A small business should confirm that Home does not cover its use, and that the Connect price floor of 50 users does not apply to a smaller team. |
| Large estate integrated with Active Directory or LDAP | Pydio Cells | Pydio Cells Connect adds AD/LDAP and SSO through OpenID Connect, OAuth2, SAML or Azure ADFS, while Nextcloud reaches directories through its LDAP app and documented SSO backends. Pydio Cells fits when the directory is the primary identity source and it is acceptable to pay for Connect; confirm your directory and SSO features against both products' current documentation. |
| Team that needs calendar, chat and other collaboration apps | Nextcloud | Nextcloud is built as an app platform with a broad app ecosystem and Nextcloud Talk, while Pydio Cells is focused on file sharing, WebDAV and sync. This holds when apps beyond files are a daily need; if files are the only requirement, the extra app surface adds upgrade work that Nextcloud would bring with it. |
| Pure file service on a MySQL or MariaDB stack | Pydio Cells | Pydio Cells requires MySQL 5.6 or higher or a MariaDB equivalent, so a team with an existing MySQL or MariaDB estate and no need for PostgreSQL can keep one database engine. Nextcloud 35 also supports MySQL and MariaDB, so this only favors Pydio Cells when the team wants a file-only service with a Go microservice design rather than a PHP app platform. |
| Organization that must buy audit log export | Pydio Cells | Pydio Cells Enterprise lists exportable audit logs, and it starts at 4,380 euros per year for 50 users or 5,980 euros per year from 100 users, per the Pydio pricing page. Nextcloud's Enterprise tiers are sold with a 100-user minimum, so confirm with Nextcloud which audit capabilities are included in its subscriptions before choosing. |
How each platform is built and what that means for operations
Nextcloud and Pydio Cells take very different shapes: one is a PHP and JavaScript application with a long list of supported databases, the other is a Go microservice platform with a narrower database requirement. Each design sets a different upgrade rhythm, setup path and set of platform constraints, so the operating model matters as much as the feature list.
Nextcloud as a PHP and JavaScript platform
Nextcloud Server is written mainly in PHP and JavaScript or TypeScript, and it runs on a conventional web stack of Apache 2.4 or nginx with php-fpm. Your team will manage PHP versions, web server configuration and application code the way it already manages other PHP systems. Check that your PHP and web server standards match the Nextcloud 35 requirements before you pick a version, because the platform will not run on whatever PHP happens to be installed.
Broad database choice on Nextcloud
Nextcloud 35 supports MySQL 8.4 or 9.7, MariaDB 10.11 to 12.3 and PostgreSQL 14 to 18, and it recommends MariaDB 11.8 or PostgreSQL 18. Oracle is available only with an enterprise subscription, and SQLite has limitations. Pick the database your DBA team already backs up and patches, and confirm the chosen engine against the current requirements page before you build, since the supported range changes with each major line.
Pydio Cells as a Go microservice design
Pydio Cells is a Go rewrite of the earlier PHP Pydio project, built as a set of microservices. That design means more moving parts to observe, with service health, logs and restarts all needing a plan, even though the install is a single set of binaries. Ask the vendor or your own tests how the services are packaged, how they scale and which of them you must run for a minimal deployment.
Pydio Cells setup and MySQL or MariaDB
Pydio Cells requires MySQL 5.6 or higher or a MariaDB equivalent, and its setup runs through a ./cells configure wizard after you install the binaries. Your database choice narrows to the MySQL family, so a PostgreSQL-only shop would need a new database service. Confirm that MySQL 5.6 meets your security baseline, since older MySQL releases may be out of support in your own policy even when Pydio accepts them.
Nextcloud upgrades one major version at a time
Nextcloud does not allow skipping major releases, so each upgrade path moves through every intermediate major version. Nextcloud publishes a new major version every four months and supports each for one year, which means a fleet that falls behind must make several sequential upgrades. Plan a backup before every upgrade, disable third-party apps until they are confirmed compatible, and schedule the work into your change calendar.
Pydio Cells Windows support caveat
Pydio publishes binaries for Linux, macOS and Windows, but its README says Windows is not yet officially supported. If your server estate is Windows-based, treat Pydio Cells as a Linux or macOS deployment target, and confirm with Pydio whether that status has changed before you commit. Nextcloud's server requirements are built around Linux web stacks, so both platforms point you toward Linux hosting for production.
Side-by-side capabilities for SSO, audit, database and extensibility
This table sets Nextcloud and Pydio Cells side by side on the controls that usually decide a regulated shortlist: licensing, database, identity, audit and access control. Read each row against the edition you would actually buy, because Pydio gates several of these features behind paid tiers. Where a cell says to confirm, ask the vendor for the tier and version that includes that feature.
| Capability | Nextcloud | Pydio Cells |
|---|---|---|
| License | AGPL-3.0 for the server, with an Enterprise subscription sold alongside it | AGPLv3 for Cells, with Home free and Connect and Enterprise sold as paid editions |
| Free edition and paid tiers | Community server is free; Enterprise Standard lists from 71.29 euros per user per year with a 100-user minimum (Nextcloud pricing page) | Home is free for home use and evaluation; Connect starts at 3,280 euros per year for 50 users (Pydio pricing page) |
| Database needs | MySQL 8.4 or 9.7, MariaDB 10.11 to 12.3 or PostgreSQL 14 to 18 for Nextcloud 35; Oracle requires an enterprise subscription | MySQL 5.6 or higher or a MariaDB equivalent; confirm supported versions for the v5 rewrite before planning |
| Identity integration | LDAP and Active Directory app, with OpenID Connect and SAML backends documented; confirm which need Enterprise | AD/LDAP, OpenID Connect, OAuth2, SAML and Azure ADFS, included from the Connect tier |
| Audit logging | Confirm audit log coverage, export options and the edition that includes them | Exportable audit logs in the Enterprise tier only |
| MFA and role-based access control | Confirm multi-factor and role-based access options for your Nextcloud edition | Multi-factor authentication and role- and rule-based access control in the Enterprise tier |
| White labeling | Confirm branding options and whether any require an Enterprise subscription | White-labelling included from the Connect tier |
| Sync clients | Confirm the current desktop and mobile client list and supported versions with Nextcloud | WebDAV plus mobile and desktop sync included in Home |
| Platform support | Linux web stack with Apache 2.4 or nginx with php-fpm, running PHP 8.3 to 8.5 | Linux, macOS and Windows binaries; the README says Windows is not yet officially supported |
What each platform's license and paid tiers actually include
Nextcloud Server is licensed under AGPL-3.0-only, and the community edition is free to download, run and modify under those terms. Nextcloud GmbH sells Enterprise as a subscription on top of the same code, aimed at enterprise, public sector and education users. The subscription buys support, maintenance and lifecycle commitments rather than a different codebase.
- Standard tier: Includes one year of maintenance, per Nextcloud's pricing page. List prices start at 71.29 euros per user per year for 100 or more users.
- Premium tier: Adds a maintenance lifecycle of five or more years, extended support hours and clustered instance support, at a list price starting at 104.99 euros per user per year.
- Ultimate tier: Adds support up to 24/7 with response times down to one hour, at a list price starting at 204.75 euros per user per year.
- 100-user minimum: Enterprise subscriptions have a 100-user minimum, and lower per-user rates apply from 200 users.
- Community lifecycle: Each major release is supported for one year through monthly maintenance releases, so community deployments must plan regular major upgrades.
Confirm the current list prices, the minimum seat count and what each tier includes on Nextcloud's pricing page and in a written quote before budgeting, since per-user pricing scales with headcount.
Pydio Cells is licensed under AGPLv3, and its server is written in Go following a microservice design. Pydio sells Connect and Enterprise as paid tiers that add identity integration, white-labelling and governance features on top of the same open-source base. The Home edition is free, but it is limited to home use and evaluation.
- Home edition: Free for home use and evaluation, and includes sharing, WebDAV and mobile and desktop sync.
- Connect edition: Starts at 3,280 euros per year for 50 users. Adds AD/LDAP, SSO through OpenID Connect, OAuth2, SAML or Azure ADFS, and white-labelling.
- Enterprise edition: Starts at 4,380 euros per year for 50 users, or 5,980 euros per year from 100 users. Adds role- and rule-based access control, multi-factor authentication, terms of service validation and exportable audit logs.
- User counting: Pydio counts any individual given a unique username, and one credential may not be shared by more than one person.
- Scope of paid features: The published tiers list the features above, so confirm which support, lifecycle and upgrade commitments come with each tier before you sign.
Check Pydio's pricing page and the user-counting FAQ against your real headcount, including service accounts and shared mailboxes, because a shared credential may move you into a higher tier.
Both platforms use AGPL-licensed server code, so the license itself does not separate them. What differs is which features sit behind the paid tier, how support and maintenance are sold, and how each vendor counts users. Reading the license alone will not tell you what you will pay to run either platform.
- Identity features: Nextcloud documents LDAP, OpenID Connect and SAML authentication backends, and the paid tiers focus on support and lifecycle. Pydio places AD/LDAP and SSO in its Connect tier.
- Audit and access control: Pydio lists exportable audit logs and role-based access control in Enterprise. Confirm what Nextcloud's community edition and tiers log and how you would export it.
- Lifecycle commitments: Nextcloud's Premium tier adds a five-year or longer maintenance lifecycle. Ask Pydio for its written support and maintenance period for each tier.
- Seat counting: Nextcloud prices per user with a 100-user minimum, while Pydio prices from 50 users and counts every named individual.
- Upgrade effort: Nextcloud requires one major version at a time, which applies whether or not you pay.
Ask both vendors for a written quote tied to your user count, and confirm in writing which features and support hours are included.
A free path is viable for a small team that can carry its own support and upgrades, but the free tiers differ in what they cover. Nextcloud Server can be run as a community deployment with no subscription. Pydio Home is limited to home use and evaluation, so a business team cannot treat it as a free production tier.
- Nextcloud community: Free to run under AGPL-3.0-only, with community support and monthly maintenance for each supported major line.
- Pydio Home: Free for home use and evaluation only, with sharing, WebDAV and sync, but without the Connect or Enterprise features.
- Internal effort: Without a paid tier, your team owns patching, identity integration and major upgrades, which takes staff time that does not appear on a license invoice.
- Evaluation risk: Using Pydio Home for an evaluation is allowed, but a move to production usually means buying Connect or Enterprise.
- Migration cost: Moving users between platforms later costs time in both directions, so price that into the decision at the start.
Confirm whether your intended use fits Pydio's home and evaluation terms before you deploy, and ask Nextcloud which features your community deployment will lack compared with the paid tiers.
What the Cells v5 rewrite means for a Pydio decision today
The current published release is Pydio Cells v4.4.18, dated October 6, 2026, while the v5 line is a development branch that the project marks as work in progress. Any Pydio decision made today should be sized and contracted against v4.4.18 and the features it ships, not against what v5 may later bring. Treat v5 as a roadmap item to verify, not as a capability you can count on.
Before committing, confirm three things with Pydio in writing. First, the release timing: ask whether a stable v5 is planned, what the project's current status is, and whether v4 receives security fixes during the transition. Second, the migration path from v4 to v5: ask whether an in-place upgrade is supported, what data, index and configuration changes are involved, and whether a rollback path exists. Third, feature placement: map each requirement, such as SSO, audit log export, role-based access control or multi-factor authentication, to the edition and release where it ships today. Check the Pydio Cells releases page and the pricing tiers against that list.
If a required feature is only described for v5, the decision changes. Either accept v4 without it, add a compensating control, or delay the purchase until the feature is in a stable release. Ask for the outcome of this review in the quote, so that an upgrade from v4 to v5 is either priced as in scope or explicitly excluded. Compare this with Nextcloud, where the upgrade path is documented one major version at a time, and ask Pydio for an equivalent written statement before you sign.
What drives running cost on each side
Running cost in this comparison is less about the license fee and more about who you pay for support, how much database and administration effort the stack needs, and how many paid seats you buy as headcount grows. The cards below separate one-time setup from recurring spend so you can ask each vendor for the right numbers in a quote.
Infrastructure and database choice
Nextcloud 35 runs on PHP 8.3, 8.4 or 8.5 with MySQL, MariaDB or PostgreSQL, and it needs a web server and PHP-FPM you manage yourself. Pydio Cells is a Go microservice platform that requires MySQL 5.6 or higher or a MariaDB equivalent. Ask who will host and back up each database, how many services you must run, and whether your existing database platform already has a licensed support contract.
Administrator skills for each stack
Nextcloud administration sits in the PHP and web server world, where most operators already have experience and a large community of guides. Cells asks for Go service management, a wizard-driven ./cells configure setup, and familiarity with its microservice layout. Estimate the staff time for each side, and check whether your team or a partner can cover the on-call work for the chosen stack.
Support tier selection
Nextcloud Enterprise is sold in Standard, Premium and Ultimate tiers with a 100-user minimum, and Standard includes 1-year maintenance. Pydio Cells Connect and Enterprise are priced per user band with support terms that come with the paid edition. The support tier you need depends on response time, cluster support and how long you expect to run one major line, so price the tier that matches your outage tolerance rather than the cheapest option.
Upgrade effort on each major line
Nextcloud does not allow skipping major releases, so each upgrade is a sequence of steps, with a backup before each one and third-party apps disabled until confirmed compatible. Nextcloud 35 is supported until September 2027, which sets how often you must plan that sequence. Pydio Cells is moving from v4 to a v5 rewrite that is still marked work in progress, so budget time for a migration decision rather than a routine patch cycle.
User counting rules
Pydio counts a user as any individual given a unique username, and a single credential may not be shared by more than one person. That means service accounts, shared mailboxes and integration logins can change your paid seat count. Before you request a quote, list every account that will authenticate, including contractors and automated clients, and confirm how the vendor treats each one.
Growth in paid seats
Pydio Connect starts at 3,280 euros per year for 50 users, and Enterprise starts at 4,380 euros per year for 50 users or 5,980 euros per year from 100 users, so each added seat band raises the recurring bill. Nextcloud Enterprise list prices are per user per year from the 100-user minimum, with lower rates from 200 users. Model headcount growth for three years, and ask each vendor how band thresholds and mid-term additions are billed.
Moving users from Pydio Cells to Nextcloud, or the reverse
This sequence moves a team's accounts, folders and file data between Pydio Cells and Nextcloud without losing ownership or access. It ends with users signed in on the new platform, their sync clients connected, and the old system kept read-only for a fallback window.
Inventory users, groups and external sharing
The platform owner exports the list of accounts, groups and group memberships from the current system and records who owns which workspace. Pydio's pricing FAQ counts a user as any individual with a unique username, and one credential may not be shared, so flag any shared or service logins now for separate handling. The step is done when every active account has a named owner and a group, and each shared service login has a documented replacement or retirement decision.
Confirm the identity source before creating accounts
The identity team decides whether users will authenticate against the same directory, Active Directory or LDAP, or through OpenID Connect or SAML. Nextcloud's LDAP app lets directory users appear in Nextcloud and log in with their directory credentials, and Nextcloud also documents OpenID Connect and SAML user authentication backends. Confirm with the vendor and in your own environment which of these your Nextcloud edition and Pydio tier support, since SSO features differ by Pydio tier. The step is done when one identity source is signed off for each user group.
Map library and folder structure to target spaces
Team leads and the platform owner decide how each Pydio workspace becomes a Nextcloud folder, group folder or shared space, including which permissions apply at each level. Write the mapping as a table that lists source path, target path, owning group and the people who need read or edit access. Test the mapping on one small workspace first, with a named user who confirms access. The step is done when the mapping table is signed off and the test workspace behaves as expected.
Migrate file data and rebuild permissions
The migration engineer copies file content into the target platform and reapplies permissions from the mapping table, because file ownership and access rules do not carry over automatically between the two systems. Confirm with the vendor how each platform's export and import tooling handles metadata, versions and trash before you rely on it. Compare file counts, total sizes and a sample of checksums between source and target for each workspace. The step is done when every mapped workspace matches the source on counts and checksums and the permission spot checks pass.
Rebuild shares and sync client configurations
Shares, public links and sync client settings do not transfer as working items, so the platform team recreates the shares that still matter and each user reconnects their desktop and mobile clients to the new server address. Confirm which sync client versions each platform requires with the vendor before rollout. Ask a pilot group to sync a folder both ways and report conflicts or missing files. The step is done when the pilot group confirms a clean two-way sync and every critical share is listed as recreated.
Validate the target against the one-major-version rule
Before go-live, the engineer confirms the Nextcloud target version is a supported major line and records the upgrade path for later. Nextcloud does not allow skipping major releases during upgrades, so administrators must move one major version at a time, back up before every upgrade and disable third-party apps until they are confirmed compatible. Check the current release schedule and system requirements, including supported PHP and database versions, before you choose the starting version. The step is done when the target version, its end-of-life date and its upgrade path are written into the runbook.
Cut over users and retain the source read-only
The platform owner announces a cutover window, freezes writes on the old system, runs a final incremental copy and switches users to the new address. Keep the source platform read-only for a fallback period set by your own rollback policy, and confirm with the vendor how audit history will be retained, because audit records are not expected to move with the files. The step is done when all active users have signed in, support tickets for access problems are closed, and the source is archived with its export logs.
Where Nextcloud and Pydio Cells implementation projects usually run long
Directory and SSO integration is the first place both projects run long, and the cost depends on what the client can supply. On Nextcloud, the LDAP app lets LDAP and Active Directory users sign in with their directory credentials, and OpenID Connect and SAML backends are also documented, so the work is choosing one identity path, mapping group attributes and testing lockout and password policy against the real directory. On Pydio Cells, AD/LDAP, OpenID Connect, OAuth2, SAML and Azure ADFS sit in the paid Connect tier, so the licensing decision and the identity design happen together. Before any quote, the client should provide read access to the directory, a named owner for the service account, and a decision on which identity source is authoritative. Database provisioning follows: Nextcloud 35 recommends MariaDB 11.8 or PostgreSQL 18, while Pydio Cells requires MySQL 5.6 or higher or a MariaDB equivalent. Ask who owns backups, replication and tuning of that database, since a poorly sized instance is the most common cause of slow sync in either product.
On Nextcloud, third-party app compatibility is a recurring cost. Nextcloud does not allow skipping major releases, so each upgrade moves one major version at a time, with a backup before every step and third-party apps disabled until confirmed compatible. A scope should list every app in use, the owner who tests it, and the upgrade calendar that fits Nextcloud's four-month major release cadence. On Pydio Cells, the risk sits elsewhere: the README says Windows is not yet officially supported, and setup runs through the ./cells configure wizard, so any Windows server requirement must be confirmed before the platform choice is final. Clustering is another item to pin down in writing, since it is a paid feature only in some tiers and the design of shared storage and database connections depends on it. Storage and backup design is shared work for both. Data owners must decide retention, encryption expectations and restore time objectives, because these choices set the backup tool, the storage layout and the test schedule.
User onboarding is the last area that stretches timelines, and it is often underestimated. Data owners must decide which groups get which shares, who approves external sharing, and how departing staff lose access. Pydio's pricing FAQ counts a user as any individual given a unique username and says one credential may not be shared, so shared service accounts and generic mailboxes need an explicit decision before counting seats. Ask the implementation partner for a written scope that names each deliverable, the directory and network prerequisites, the data owner sign-offs and the acceptance tests for sign-in, sync and restore. A scope that leaves any of these open is a signal that the project will run past its estimate.
Questions buyers ask before choosing between Nextcloud and Pydio Cells
Does Nextcloud need an Enterprise subscription if the code is AGPL?
No. Nextcloud Server is licensed under AGPL-3.0, so a team can run the community edition without buying a subscription. The Enterprise subscription is a paid service on top of the same code, sold by Nextcloud GmbH, with support and maintenance terms that differ by tier. The tiers are Standard, Premium and Ultimate, with a 100-user minimum. Standard includes 1-year maintenance, Premium adds a maintenance lifecycle of 5 or more years and clustered instance support, and Ultimate adds support up to 24/7 with response times down to 1 hour. Decide based on how long you must receive patches, how fast you need answers, and whether you need clustering. Ask Nextcloud for the current terms in writing before you rely on them.
What do Pydio Cells Connect and Enterprise cost for my user count?
Pydio publishes prices in euros per year. Connect starts at 3,280 euros per year for 50 users and adds AD/LDAP, SSO through OpenID Connect, OAuth2, SAML or Azure ADFS, and white-labelling. Enterprise starts at 4,380 euros per year for 50 users, or 5,980 euros per year from 100 users, and adds role- and rule-based access control, multi-factor authentication, terms of service validation and exportable audit logs. Pydio counts a user as any individual with a unique username, and one credential may not be shared by more than one person, so count service accounts and shared mailboxes carefully. Ask Pydio for a written quote that states the user count, the edition and any support terms. Your own costs also include servers, database administration, backups and staff time, which Pydio's list prices do not cover.
Which platform fits a team that must have SSO and audit logging?
Pydio Cells places SSO through OpenID Connect, OAuth2, SAML or Azure ADFS and exportable audit logs in its paid tiers, so both features require a Connect or Enterprise subscription. Nextcloud documents OpenID Connect and SAML user authentication backends and LDAP or Active Directory login in its community edition, so identity integration can be built without a subscription. Audit depth is the point to test. Check which events each platform logs, where logs are stored, how long they are kept and whether they reach your SIEM. Run a proof of concept with your identity provider and your log pipeline before you decide. Confirm the exact audit fields with each vendor, since this comparison does not cover them in detail.
How long does a migration take, and what drives the timeline?
No supplied figure gives a migration duration, so treat any number you hear as a claim to verify. The main drivers are the volume and structure of data, the number of users and permission rules, whether you keep existing sharing links and sync client behavior, and how many third-party apps or integrations you depend on. Nextcloud requires upgrades one major version at a time with a backup before each step, which matters if you plan to move between versions after go-live. Pydio Cells runs on MySQL 5.6 or higher or a MariaDB equivalent, so database preparation is a separate workstream. Ask for a scoped plan with a test migration on a copy of your data and a rollback plan.
Can our team run either platform without a partner?
Yes, some teams run either platform in-house, but the answer depends on your skills and staffing. Nextcloud has an extensive installation and admin manual, and Nextcloud All-in-One is described as the official installation method, bundling a managed set of containers, caching, database and backups. Pydio Cells is a Go microservice design with a ./cells configure wizard, and its README states that Windows is not yet officially supported. Consider who will patch the platform, tune the database, manage upgrades and respond to incidents. DeployOpen plans, implements, hardens, backs up, upgrades and supports self-hosted platforms inside your own infrastructure under written, fixed-scope agreements, and ongoing support is available as a retainer. Compare that against your own staffing before you decide.
Should we wait for Pydio Cells v5 before choosing?
Probably not if you need a platform in production soon. Pydio Cells v4.4.18 was published on October 6, 2026, and the v5 development branch is marked as work in progress in its README and releases page. A work-in-progress branch can change its design, configuration and upgrade path before release. If you wait, set a decision date and ask Pydio for its v5 release plan, upgrade notes and compatibility guidance in writing. If you choose v4 now, plan for the upgrade as a separate project with its own test environment. Nextcloud publishes a new major version every four months and supports each for one year, so plan upgrades on either platform, not only on Pydio.
Which platform has the better long-term upgrade path?
Both platforms require a planned upgrade cadence, and neither should be run without a backup and test step. Nextcloud publishes a new major version every four months and maintains each major line for one year through monthly maintenance releases. Nextcloud 35 was released on 16 September 2026 with end of life in September 2027, and Nextcloud 36 is scheduled for 17 February 2027. Nextcloud does not allow skipping major releases, so each step must be tested. Pydio's public materials do not give a comparable support window in the sources reviewed, so ask Pydio for its release policy and end-of-life dates before you commit.
How DeployOpen helps choose, implement or migrate either platform
DeployOpen is a Chainscore Labs company that plans, implements, integrates, hardens, backs up and supports self-hosted platforms inside your own cloud accounts, data centers or air-gapped networks. The cards below cover the decisions and work that sit between choosing Nextcloud or Pydio Cells and running either one in production.
Fixed-scope planning and written quotes
Before any build starts, the scope, deliverables and timelines are agreed in writing. DeployOpen does not publish a price list, so a quote follows from that written scope. For this choice, the scope should name the user count, whether Nextcloud Enterprise or a Pydio Cells Connect or Enterprise edition is in play, and which identity source and database must be supported. Ask for each cost line to show who is paid for what and which items recur.
Identity integration with LDAP and SSO
Directory and single sign-on wiring is often the most expensive part of either platform. Nextcloud's LDAP app lets Active Directory users sign in with directory credentials, and OpenID Connect and SAML backends are documented. In Pydio Cells, AD/LDAP and SSO sit in the Connect tier. Confirm which of these paths your identity provider needs, and test group mapping and offboarding before cutover.
Database and infrastructure build
Nextcloud 35 supports MySQL, MariaDB and PostgreSQL, while Pydio Cells requires MySQL 5.6 or higher or a MariaDB equivalent. DeployOpen can size and build the database tier, web tier and storage inside your environment, then document the versions chosen. Ask the implementer which database versions are tested for the specific release you deploy and how backups of the database and file store stay consistent.
Hardening and security testing
Hardening covers the web server, PHP or Go service configuration, access controls, admin accounts and the audit trail. Pydio Cells places exportable audit logs and multi-factor authentication in its Enterprise tier, so the audit design depends on the edition you buy. DeployOpen can run application and infrastructure security testing against the chosen build before users arrive, and report findings you can track to closure.
Backup, upgrades and support retainers
Nextcloud requires one major version at a time, a backup before each upgrade and third-party apps disabled until confirmed compatible. Pydio Cells is still on a v4 line while a v5 rewrite is in development. DeployOpen can plan upgrade windows, test restores and offer ongoing support or upgrade retainers. Ask what the retainer covers, how upgrade testing is staged and who makes the call when a major release changes behaviour.
Compliance readiness evidence
DeployOpen prepares systems, controls and evidence for compliance assessments, including configuration records, access reviews, logging and change history. It does not issue audit reports, attestations or certifications. Independent auditors and certification bodies make that determination. Before engaging, confirm which assessment your organization faces and ask the auditor which evidence formats they accept from a self-hosted file platform.
