ownCloud

Open-source file sync, share and content collaboration

File Sync & Storage ★ 8.8k stars Medium setup AGPL-3.0

ownCloud is a file sync and share server that lets organizations host their own cloud storage with sharing and collaboration features. It targets businesses and individuals wanting an established self-hosted alternative to commercial cloud storage. It is deployed via Docker or a traditional PHP stack.

Key features

  • Established sync and share platform
  • LDAP and enterprise integrations
  • Newer ownCloud Infinite Scale rewrite
  • Desktop and mobile clients

Pros & cons

Strengths

  • Mature and stable
  • Enterprise features available
  • Good admin controls

Trade-offs

  • Nextcloud forked away most momentum
  • Classic core in maintenance mode

ownCloud replaces

Last reviewed Aug 26, 2026 · 831 words

There are two products called ownCloud, and you must choose before installing anything. ownCloud Server, the PHP codebase that Nextcloud forked in 2016, is in maintenance mode: stable, working, and not where any new effort goes. ownCloud Infinite Scale (oCIS) is a ground-up Go rewrite that ships as a single binary, idles at a fraction of the RAM, and is the only ownCloud worth installing today. The catalogue's 8,831 stars and "classic core in maintenance mode" both describe the old one; the interesting decision is oCIS against Nextcloud.

Classic versus Infinite Scale

ownCloud Server (classic)ownCloud Infinite Scale
LanguagePHPGo
DeployDocker or LAMP stackSingle binary or one container
DatabaseMariaDB or PostgreSQL, plus RedisNone required; metadata on disk
Apps and pluginsLarge legacy catalogueSmall, built-in extensions
IdentityBuilt-in users, LDAP, SAMLBuilt-in IdP, LDAP, or external OpenID Connect
StatusMaintenanceActive development

Classic is the one to pick only if you already run it and have no appetite for a migration. Everything below is about oCIS.

Running oCIS: one container, one init

The container image is owncloud/ocis. The first run generates its configuration and an admin password; capture that password, because it is printed once.

services:
  ocis:
    image: owncloud/ocis:latest
    ports:
      - "9200:9200"
    entrypoint: /bin/sh
    command: ["-c", "ocis init || true; ocis server"]
    environment:
      OCIS_URL: https://files.example.com
      OCIS_INSECURE: "false"
      PROXY_TLS: "false"
      OCIS_LOG_LEVEL: warn
      IDM_ADMIN_PASSWORD: choose-this-yourself
    volumes:
      - ./ocis-config:/etc/ocis
      - ./ocis-data:/var/lib/ocis
    restart: unless-stopped

PROXY_TLS: "false" tells oCIS a reverse proxy is terminating HTTPS in front of it, which is the pattern that works with Caddy or Traefik; OCIS_URL has to be the exact public address or the built-in identity provider issues redirects to the wrong place and logins loop. Setting IDM_ADMIN_PASSWORD avoids hunting for the generated one. Files land in ./ocis-data as opaque blobs with metadata beside them rather than as a browsable tree, so your backup tool needs to take the whole directory, and you should not expect to ls your documents on the host.

Memory at idle is a few hundred megabytes, well under the 512 MB minimum listed for the classic version, and it stays flat under a handful of users because there is no PHP process pool and no database to feed.

What you lose against Nextcloud

Nextcloud is a groupware suite that happens to sync files: calendar, contacts, mail, Talk, office editing, an app store with hundreds of entries. oCIS is a file server. It does sharing, links with passwords and expiry, project Spaces with their own quotas and members, search, versioning, trash, and it integrates Collabora or OnlyOffice for editing in the browser. It does not try to be your calendar. For a household that wanted the whole suite, that is a loss; for an admin who watched Nextcloud's app store turn a file server into a slow monolith, it is the whole appeal, and the making Nextcloud fast post is a fair account of the alternative's upkeep.

The clients are the other thing to know. ownCloud's desktop and mobile apps are maintained and support oCIS, and the desktop client's virtual files mode is good. Third-party integrations, however, mostly target Nextcloud's APIs, and the classic app ecosystem does not carry over.

Where it fits in the category

The file sync category has three shapes. Nextcloud for the suite. Seafile and oCIS for fast, focused file sync with sharing, both storing data in their own layout rather than plain files. Syncthing for device-to-device sync with no server-side sharing at all, a split the Nextcloud versus Syncthing post walks through. oCIS's particular niche is organisations: LDAP, external OpenID Connect providers, Spaces for teams, and a company (Kiteworks, since it acquired ownCloud in 2023) selling support, which makes it easier to justify to a boss than most of this directory.

Moving off classic

There is no in-place upgrade from ownCloud Server to oCIS; the storage model is different. The practical route is to let the desktop client fully sync each user's files down, point it at the new server, and sync back up, or to copy over WebDAV with rclone. Shares, comments and app data do not transfer. Plan it as a migration with a cutover date, not as an update.

What I'd do

Install oCIS, never classic. One container behind Caddy, OCIS_URL set correctly on day one, the data directory in nightly backups as a unit. Pick it over Nextcloud when the job is files and sharing for a team, especially one with an existing identity provider, and when you want the server to stay boring. Pick Nextcloud when the household wants calendars and contacts in the same login. Either one replaces Dropbox; only one of them will still be idling at 300 MB a year from now.

Compare ownCloud

31 head-to-head comparisons.

Similar file sync & storage apps