ownCloud / oCIS is built for enterprise scenarios: mandatory IdP, Spaces, multi-tenant rollouts. Cotton is built for personal and small-team file work. This is not a scoreboard with fake certainty; it is a product-fit comparison for self-hosted file cloud decisions.
ownCloud Server (the PHP product) is in maintenance mode — the vendor pushes oCIS, a Go rewrite. They have different storage models, different deployment shapes, and different feature sets. When comparing to Cotton, oCIS is the relevant product for new deployments; ownCloud Server is for legacy estates.
oCIS introduces a Spaces abstraction — each user, project, and shared area is a separate Space with its own permissions and lifecycle. Useful for multi-tenant enterprise. Heavy for a small team that just wants a private folder tree. Cotton uses a free folder structure with sharing and permissions as normal product behavior, not a structural concept you organize around.
oCIS requires an external OIDC identity provider for any non-trivial deployment — LDAP, Keycloak, Azure AD, etc. That is correct for enterprise rollouts. For a home server or 5-person team it is overkill - a passport check to get into your own kitchen. Cotton ships with built-in accounts + passkeys + TOTP + session revoke, and can integrate with external auth when that becomes a real requirement.
Browser file UX for non-enterprise users: audio waveform, STL/OBJ/3MF viewer, mobile PDF text layer, video seek on encrypted storage, realtime SignalR sync, auto-restore DB from own backup, integrity signatures on sensitive database rows. oCIS focuses on the platform layer; Cotton focuses on what users actually click on every day.
If you are buying for an organization with enterprise requirements (mandatory IdP, multi-tenant Spaces, vendor support contracts), pick ownCloud / oCIS. If you are running a file cloud for yourself, your family, or a small team, and you want it to feel finished, pick Cotton.
Cotton does not need to beat every long-established ecosystem on every surface. The useful comparison is narrower: storage behavior, privacy posture, recovery model, deployment shape, and product focus.
Cotton stores file content as chunks and manifests, so deduplication, verification, versions, snapshots, and cleanup share one mental model.
Compression and AES-GCM encryption sit in the normal storage path; the site does not sell isolated crypto speed as user-visible ingest speed.
Snapshots, versions, trash, and reclaim are positioned as ordinary file-cloud workflows, not emergency-only backend chores.
Cotton deliberately stays narrower than broad collaboration suites: files, previews, sharing, WebDAV, recovery, and operator visibility.
Cotton is the cleaner story when files, previews, shares, snapshots, versions, WebDAV, passkeys, admin diagnostics, and a compact Docker/Postgres deployment are the main problem.
Organizations already aligned with ownCloud's enterprise platform or Infinite Scale direction.
You want a focused self-hosted file cloud with content-addressed storage, streaming crypto, snapshots, previews, WebDAV, sharing, passkeys, and a compact Docker deployment.
You need enterprise file storage and collaboration, vendor-led deployment paths, and existing ownCloud estates more than the Cotton storage-engine and recovery-model strengths.
Cotton is not trying to be a bigger suite than ownCloud. It is trying to be the sharper file cloud when the file engine itself is the product decision.
If the goal is a focused open-source file cloud with a smaller product surface and storage-first technical proof, Cotton is the sharper bet.
Last reviewed June 2026. Every line below links to its receipt - the actual issue, doc, or commit it came from. Competitors move fast; if a link goes stale, open an issue and we fix it.
Receipts
Not always. Cotton is a focused file cloud, not a clone of every app and integration in the older ecosystems. It fits best when file storage, previews, sharing, snapshots, WebDAV, security, and deployment simplicity are the main problem.
Because people searching for a self-hosted file cloud often start with the familiar names. The comparison makes the tradeoff explicit instead of pretending every product has the same goal.
If you need enterprise platform direction, vendor-led process, mandatory external IdP, or multi-tenant Spaces, ownCloud / oCIS is built for that lane. Cotton is built for personal and small-team file work.