ownCloud Infinite Scale

Self-hosted file sync & share, honestly reviewed. For founders who want Dropbox out of their stack without inheriting someone else’s PHP legacy.

TL;DR

• What it is: A complete ground-up rewrite of the original ownCloud file sync platform — rebuilt in Go, microservices architecture, no PHP, no database required [2][README].
• Who it’s for: IT administrators and technical buyers at organizations that need fast, scalable, enterprise-grade file sync. Not a beginner’s first self-hosted project [docs].
• Cost savings: Community edition is free (Apache-2.0). Enterprise features and support require a commercial license through Kiteworks (pricing not publicly listed) [docs][README].
• Key strength: Genuinely fast. The Go rewrite and microservices architecture are cited across reviews as a meaningful improvement over legacy PHP-based platforms [1][2]. Scales from a single binary on a Raspberry Pi to a full Kubernetes cluster without re-architecting [README].
• Key weakness: ownCloud Infinite Scale is now under the Kiteworks corporate umbrella, raising real questions about long-term open source commitment. It also deliberately strips the kitchen-sink feature set that many Nextcloud users expect — no chat, calendar, or contacts unless you add them separately [1][2].

---

What is ownCloud Infinite Scale

ownCloud is one of the original self-hosted file sync platforms, dating back to 2010 [2]. For most of its life it ran on PHP with a traditional relational database — the same architecture that eventually drove some of its original developers to fork the project and start Nextcloud in 2016 [2].

Infinite Scale (internally called oCIS) is ownCloud’s answer to that fork: a complete rewrite of the platform from PHP to Go, using a microservices architecture instead of the original monolith [2][README]. The project’s GitHub README describes it as “the new file sync & share platform that will be the foundation of your data management platform” — more infrastructure pitch than product pitch, which tells you something about the target customer [README].

The “Infinite Scale” in the name is literal. The architecture is designed to run as a single binary on a Raspberry Pi or as a distributed Kubernetes cluster, by changing configuration and starting multiple services as needed — not by rewriting the deployment entirely [README][docs]. This is a meaningful engineering bet that the old PHP architecture never could have made.

One important business context point: the official documentation header now reads “A Kiteworks Company,” indicating that ownCloud has been folded into the Kiteworks enterprise content platform business [docs]. Kiteworks is primarily an enterprise compliance and governance vendor. That acquisition context matters when evaluating the long-term direction of the open source community edition.

At 1,910 GitHub stars, oCIS sits well behind Nextcloud in community visibility — but star count isn’t the relevant metric here. This is built for organizations, not hobbyists.

---

Why People Choose It Over Nextcloud

The self-hosted file sync debate is basically always Nextcloud vs something else, and for ownCloud Infinite Scale the comparison is especially loaded given the shared history.

The performance argument. The strongest case for oCIS is speed. The Go rewrite is consistently cited as producing a meaningfully faster product than Nextcloud’s PHP stack [1][2]. The Contabo comparison article notes that file transfers “feel instant, and the interface is incredibly snappy” [2]. The Reddit thread from r/selfhosted has users specifically mentioning that Nextcloud bugs and quirks drove them to evaluate oCIS [1]. For organizations moving large files — media assets, scientific data, large archives — the performance gap can matter more than any feature comparison [2].

The architecture argument. The microservices approach means you can scale individual components under load rather than throwing more resources at a monolith. The “no PHP, no database required” pitch is real — oCIS ships with its own embedded storage and authentication, removing two significant operational dependencies [README][docs]. For teams running Kubernetes already, oCIS fits naturally into that infrastructure pattern.

The Spaces concept. oCIS replaces traditional personal folder hierarchies with “Spaces” — data rooms that exist independently of any single user account [2]. The practical impact: a Space doesn’t disappear when the user who created it leaves the organization. For business file management where folders are owned by teams rather than individuals, this is a meaningful change. One Contabo reviewer notes this is designed specifically for teams that need “data rooms that exist independently of any single user” [2].

The honest counterpoint. oCIS is explicitly not trying to be Nextcloud’s all-in-one hub. As of the Reddit thread from the r/selfhosted community, there are no bundled mail, calendar, contacts, or chat features [1]. If you want those things, you integrate them separately or choose Nextcloud. The Contabo review describes oCIS as better suited for businesses handling large data volumes, while Nextcloud is described as the better choice for “home users who want a simple install-and-forget solution with a lot of fun add-ons” [2].

---

Features

Based on the README and official documentation:

File sync and share core:

• File sync across web, Android, iOS, and desktop clients [README]
• WebDAV API for standard client compatibility [README]
• CS3 API for deeper integrations [README]
• “Spaces” — team-scoped data rooms independent of individual user accounts [2]
• Version history and file restoration [docs]

Web office integration:

• Collabora Online (via WOPI protocol) [README]
• OnlyOffice Docs [README]
• Microsoft Office Online Server [README]
• WOPI application gateway for collaborative editing [README]

Authentication and identity:

• OpenID Connect (OIDC) authentication [README]
• External IdP integration (Keycloak and others) [README]
• Embedded LibreGraph Connect identity provider for deployments that don’t already have an IdP [README]

Deployment and operations:

• Single binary deployment (Linux, apt packages) [merged profile]
• Docker and Docker Compose [README]
• Kubernetes with Helm charts [merged profile]
• Scales from Raspberry Pi to full cluster without architecture change [README]
• Environment variable-based configuration with optional config files [docs]
• REST API [merged profile]

What it doesn’t include out of the box: calendar, contacts, chat, video calls, Kanban, or the app store ecosystem that Nextcloud has spent a decade building [1][2].

---

Pricing: Community Edition vs Enterprise Math

Community edition (Apache-2.0):

• Software license: $0 [README]
• You get the full file sync platform, Spaces, office integration, mobile/desktop clients, REST API
• VPS to run it on: roughly $5–20/month depending on your scale and provider

Enterprise / commercial tier:

• Required for enterprise support, advanced compliance and governance features, and SLA-backed deployments
• Managed through Kiteworks — specific pricing is not publicly listed on the documentation site; you contact sales [docs]

Nextcloud for comparison:

• Community edition: $0 (AGPL license)
• Nextcloud Enterprise: starts around €1,900/year for 50 users (publicly listed on Nextcloud’s site)
• Nextcloud Hub (managed): tiered pricing based on users and storage

Self-hosted cost math for a 20-person team: A 20-person organization currently paying for Dropbox Business Plus (~$18/user/month = $360/month) could run oCIS on a mid-range dedicated server ($30–60/month) and pay nothing for the software license. That’s roughly $3,600–$4,000/year saved, not counting the one-time setup investment. The enterprise license cost from Kiteworks would reduce that savings figure — but for organizations that don’t need enterprise support, the community edition covers the core use case.

The missing data point: Kiteworks doesn’t publish enterprise pricing, which makes accurate comparison to Nextcloud Enterprise impossible. If compliance features, SSO, or vendor SLAs are requirements, get a quote before assuming cost savings.

---

Deployment Reality Check

The README’s quickstart is straightforward — five Docker commands to get a running instance with a browser UI [README]. That’s the easy path.

What you actually need for a real deployment:

• A Linux server (or Kubernetes cluster) with adequate disk and RAM — documentation doesn’t specify minimum requirements in the scraped content, but file sync platforms generally need 2–4GB RAM minimum for small teams
• Docker or a container runtime
• A domain and reverse proxy with TLS for external access
• If you want external identity management: a Keycloak instance or another OIDC-compatible IdP
• If you want web office: a separate Collabora or OnlyOffice container with WOPI configuration

What can go sideways:

• The microservices architecture is a double-edged sword: powerful when everything is configured correctly, harder to debug when it isn’t. The original ownCloud had a PHP/Apache stack most sysadmins already understood. oCIS’s Go microservices are less familiar territory for generalist administrators.
• The r/selfhosted thread includes users describing oCIS as “lacking polish” on non-core features compared to what they expected from ownCloud’s legacy [1]. The platform is fast and the core sync works, but edge cases in the interface draw criticism.
• The EULA note in the documentation deserves attention: ownCloud ships with a separate End-User License Agreement on top of the Apache-2.0 license, clarifying usage rights by user group [docs]. For Apache-licensed software this is unusual and worth reviewing before enterprise deployment.
• The Kiteworks acquisition creates uncertainty about how aggressively the community edition will remain full-featured as the company pushes enterprise deals. This is a real governance risk for anyone making a 5-year infrastructure commitment.

Realistic time estimate for a technical sysadmin: 1–3 hours for a basic working deployment. A proper production setup with external IdP, HTTPS, and office integration: a full day or more. For a non-technical founder: this is not the project to start with unless you have someone technical running it.

---

Pros and Cons

Pros

• Genuinely fast. The Go rewrite produces real performance improvements over PHP-based file sync platforms. Consistently mentioned across independent reviews as a headline differentiator [1][2].
• Apache-2.0 license — more permissive than Nextcloud’s AGPL. You can embed, integrate, and build on it without GPL propagation concerns [README].
• No PHP, no database required. Removes two major operational pain points and dependencies [README][docs].
• Scales without re-architecting. Single binary to Kubernetes cluster is a real path, not marketing copy — the microservices design enables it [README].
• Spaces concept solves a real enterprise problem: team-owned data rooms that survive user account changes [2].
• Strong office integration. Collabora, OnlyOffice, and Microsoft Office Online all supported via WOPI [README].
• Standard open protocols. WebDAV and CS3 APIs mean client compatibility is broad [README].
• OIDC-native. Integrates cleanly with enterprise identity stacks (Keycloak, Okta, Azure AD) or ships its own embedded IdP [README].

Cons

• No bundled productivity suite. No chat, calendar, contacts, or task management. If you need that, you’re adding separate services or choosing Nextcloud [1][2].
• Kiteworks acquisition risk. The open source community edition is now governed by an enterprise compliance company. That changes the incentive structure for what gets shipped in the free tier versus the commercial tier [docs].
• 1,910 GitHub stars is low relative to Nextcloud’s visibility. Smaller community means fewer community integrations, fewer guides, and slower unofficial support channels [merged profile].
• EULA on top of Apache-2.0. For an open source platform this is an unusual step and warrants legal review before enterprise deployment [docs].
• Steeper operational complexity than single-process alternatives. The microservices architecture pays off at scale, but adds surface area for configuration errors [docs][README].
• “Home user unfriendly” is the phrase multiple reviewers use [2]. The Contabo piece explicitly notes it’s less suited for home users looking for simple install-and-forget with fun add-ons.
• Pricing opacity at enterprise tier. Kiteworks doesn’t publish commercial license pricing, making budget planning harder without a sales call [docs].

---

Who Should Use This / Who Shouldn’t

Use ownCloud Infinite Scale if:

• You’re an IT administrator or technical buyer at an organization that needs file sync at scale, not a home user.
• Performance and throughput on large file volumes matter — media, scientific, or engineering data that would stress a PHP stack.
• You’re already running Kubernetes and want a file sync platform that fits that infrastructure model.
• You have an existing enterprise IdP (Keycloak, Okta, Azure AD) and want OIDC integration without adding a custom auth layer.
• You need an Apache-2.0 license specifically — fewer restrictions than Nextcloud’s AGPL for embedding or commercial products.
• You want file sync and office editing without the broader collaboration suite and the complexity it brings.

Skip it (pick Nextcloud instead) if:

• You want a one-stop self-hosted Google Workspace replacement: calendar, contacts, chat, video calls, and file sync in one install.
• You’re deploying this yourself for the first time and want a large community, a mature app store, and extensive documentation for beginners.
• Long-term open source governance certainty matters — Nextcloud’s structure is clearer than ownCloud’s current Kiteworks situation.

Skip it (pick Seafile instead) if:

• You want best-in-class performance specifically for file sync without the Spaces/governance features.
• You’re a developer-focused team that wants a clean, minimal file sync with solid client libraries.

Skip it (use managed cloud) if:

• You have fewer than 10 users and no technical administrator, and the core value proposition is just “not paying Dropbox.” At that scale, the operational overhead of running oCIS is higher than the SaaS bill.

---

Alternatives Worth Considering

• Nextcloud — the obvious comparison and the market leader in self-hosted file collaboration. More features, bigger community, more integration options, AGPL license. Choose oCIS over Nextcloud when performance at scale and deployment simplicity matter more than breadth.
• Seafile — strong file sync performance with a smaller feature footprint. Community edition is free, but some features (WebDAV, versioning) are gated behind the professional tier.
• Filecloud — enterprise-focused, proprietary. The Contabo review covers it directly as a Nextcloud/ownCloud alternative for compliance-heavy organizations [2]. Better enterprise support story than oCIS community edition, but fully closed source.
• Syncthing — peer-to-peer sync without a central server. No sharing, no web UI, no office integration — but zero infrastructure overhead and genuinely simple for pure device sync use cases.
• Pydio Cells — another Go rewrite of a legacy PHP file platform (Pydio). Similar architectural philosophy to oCIS, fewer users, but worth evaluating side-by-side.
• MinIO + custom frontend — for engineering teams that want raw S3-compatible object storage with maximum control and don’t need a consumer-facing sync client.

The realistic shortlist for a technical team choosing between self-hosted file platforms is oCIS vs Nextcloud. Choose oCIS when you need speed, a clean Kubernetes deployment, and Apache-2.0 licensing. Choose Nextcloud when you need breadth, community, and confidence in long-term open source governance.

---

Bottom Line

ownCloud Infinite Scale is a technically impressive rewrite that fixes most of what was wrong with the original ownCloud — the PHP monolith, the database dependency, the scaling ceiling. For organizations with real throughput requirements and technical teams capable of running it, it’s a legitimate choice. The Go architecture is fast, the deployment is cleaner than most self-hosted file platforms, and the Apache-2.0 license is genuinely permissive.

The caveats are real though. The Kiteworks acquisition puts a corporate compliance company in charge of a project that serves the self-hosted community, and that tension will play out over time in what gets gated behind the commercial tier. The community is smaller than Nextcloud’s. And this is built for sysadmins, not founders — if you’re evaluating it because you’re tired of paying Dropbox and you’ve never touched a Kubernetes cluster, there are more approachable starting points.

If you have the technical capacity to run it, or someone to run it for you — which is exactly what unsubbed.co’s parent studio upready.dev deploys for clients — oCIS earns its place in the enterprise self-hosted file sync conversation.

---

Sources

1. r/selfhosted — “Anyone using ownCloud Infinite Scale (OCIS) instead of Nextcloud?” (Reddit thread, 2023). https://www.reddit.com/r/selfhosted/comments/14f7ewd/anyone_using_owncloud_infinite_scale_ocis_instead/
2. Contabo Blog — “Nextcloud vs OwnCloud vs Filecloud - Which One To Use In 2026”. https://contabo.com/blog/nextcloud-vs-owncloud-vs-filecloud/

Primary sources:

• GitHub repository and README: https://github.com/owncloud/ocis (1,910 stars, Apache-2.0 license)
• Official documentation: https://doc.owncloud.com/ocis/next