ownCloud Infinite Scale: A Self-Hosted File Sync and Sharing Platform

Purpose

ownCloud Infinite Scale (oCIS) is ownCloud’s platform for file synchronization and sharing, aimed at data management deployments where users and organizations want to operate their own file service. The repository describes it as self-hosted and is licensed under Apache License 2.0. GitHub does not mark the repository as archived.

This is more than a browser file list. The README lists Web, Android, iOS, and Desktop clients. Its backend is based on reva and exposes open APIs including WebDAV and CS3. Teams with existing identity or directory infrastructure may therefore consider oCIS for a centralized file service, but client versions, integrations, and production scale still need to be checked against the official documentation.

Known features and suitable users

Authentication uses OpenID Connect. Administrators can use an external identity provider such as Keycloak or the embedded LibreGraph Connect provider. oCIS may fit teams that need centralized sign-in, desktop and mobile synchronization, or shared file spaces. The project also documents integration with Collabora Online, OnlyOffice Docs, and Microsoft Office Online Server. Collaborative editing is supported through the WOPI application gateway. This describes an integration path; it does not mean every office component is included or configured automatically.

The README describes delivery as a single binary or container and says the system can be expanded toward Kubernetes by changing configuration and running multiple services. It presents deployment paths starting with small devices, a single server, or a virtual machine. However, the supplied sources do not establish a universal minimum hardware profile, capacity limit, or performance figure, so those claims should not be inferred.

Limitations and deployment considerations

A production deployment should not simply copy an evaluation quickstart. The project recommends reading its prerequisites, deployment, and general information documentation first. Operators should plan persistent data storage, backup and recovery, domain and TLS handling, reverse-proxy behavior, logging and monitoring, and the choice between an external or embedded identity provider. Online office integration also requires separate review of the office service, WOPI routing, and permission mapping.

Identity synchronization deserves particular attention. The v8.2.0 release notes say that OIDC group synchronization became opt-in and list fixes involving authentication, permissions, and sharing. Before upgrading, administrators should read the release notes and test groups, link shares, permission changes, token caching, and existing clients in a staging environment. The same release also mentions preventing internal error details from appearing in WebDAV error responses; this is a documented change, not a substitute for an organization’s own security assessment.

For source builds, the README positions the method for development and mentions Go and a C compilation environment. The supplied material does not provide a general production hardware baseline. In practice, oCIS is better suited to self-hosters prepared to operate identity, storage, network entry points, monitoring, and upgrade procedures than to users seeking a fully managed, maintenance-free service.

Sources

• GitHub repository metadata
• Project README
• Official release
• Official project page

Sources checked: 2026-09-24