OpenCloud

Last reviewed Sep 13, 2026 · 811 words

OpenCloud is ownCloud Infinite Scale under new management. The engineers who built oCIS left after ownCloud's acquisition, forked the Apache-licensed Go codebase in early 2025 under Heinlein Group backing, and have shipped continuously since. That history tells you most of what you need: the code is far more mature than a 2025 start date suggests, it is fast and light, and it is deliberately a file platform rather than a Nextcloud-style everything suite.

No database, no PHP, one binary

The architecture is the pitch. OpenCloud is a set of Go microservices that ship as a single binary and run as one process by default, with files stored on the filesystem, metadata in the same tree, and search in a bundled index. There is no PostgreSQL or MariaDB to size, no Redis, no PHP-FPM tuning. Compare that to the effort required to make Nextcloud fast, and the 512 MB RAM figure stops looking optimistic. On a 2-core VPS it serves a handful of users with a responsive web UI and nothing to cache.

The trade is that the storage format is OpenCloud's own. Its "decomposed" filesystem stores blobs and metadata under node IDs rather than as a mirror of the user's folder tree, so you cannot just browse the data directory with ls. A POSIX storage driver that keeps the human-readable layout exists and is the direction the project is heading; check its status in the official docs before you depend on it, because the answer changes between releases.

Compose setup is short, but TLS and the URL are not optional

The quickest sane path is the opencloud-compose repository. For a first look, the single-container form is enough to understand the moving parts:

services:
  opencloud:
    image: opencloudeu/opencloud-rolling:latest
    ports:
      - "9200:9200"
    environment:
      OC_URL: https://cloud.example.com
      IDM_ADMIN_PASSWORD: change-me-now
    volumes:
      - opencloud-config:/etc/opencloud
      - opencloud-data:/var/lib/opencloud
    entrypoint: ["/bin/sh", "-c", "opencloud init || true; opencloud server"]

OC_URL must match what browsers and desktop clients actually hit, because OpenCloud issues OpenID Connect tokens from its built-in identity provider and clients validate the issuer. Put Caddy in front with a real certificate, set OC_INSECURE=true only for a LAN test with a self-signed cert, and the desktop and mobile clients (the ownCloud ones work; OpenCloud publishes its own too) log in via a browser flow. Skipping this step is the source of nearly every "the client says unauthorized" report.

Collaboration comes from Collabora, not from OpenCloud

Web editing of documents is via WOPI to Collabora Online or OnlyOffice, and the Compose repository wires Collabora in with one extra profile. Spaces (shared team folders with their own quota and managers), share links with passwords and expiry, and full-text search of document contents are built in. Calendar, contacts, mail, video calls and the app store are not, and there is no plan for them to be. If your household or team uses Nextcloud Talk or the calendar daily, OpenCloud is not a replacement; it is a much better file server.

Where it sits against the alternatives

Nextcloud remains the safer pick for anyone who wants one login for files, calendar, contacts and chat, and its ecosystem is 20 times the size. Seafile is the other lean file server; it has years more production mileage and better delta sync for large files, but its client polish and web UI lag. ownCloud Infinite Scale itself continues under Kiteworks, but the community energy visibly moved to the fork. And if you only need sync between your own devices without a web interface or sharing, the Nextcloud vs Syncthing piece explains why a server may be the wrong shape entirely.

Young project risks, stated plainly

Version cadence is fast and breaking config changes happen. The extension surface is small, so the "there's an app for that" reflex from Nextcloud does not transfer. Third-party guides are scarce and many still describe oCIS variable names. And backup means snapshotting the data directory and the config directory together, consistently; there is no database dump step, which is simpler, but there is also no partial restore of one user's files without the tooling that the project is still building.

What I'd do

For a small team or a household that wants Dropbox-style sync and sharing with document editing, and does not use Nextcloud's calendar or chat, I would run OpenCloud today: the Compose stack with Collabora, behind Caddy, on a 2 GB VM, with nightly filesystem snapshots. Pin a version and read release notes before upgrading. For anyone who needs the full groupware suite, or who cannot tolerate a config migration every few months, stay on Nextcloud and check back in a year.