OpenCloud

Open-source file sharing and collaboration, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (Apache 2.0) file management and sharing platform built on top of ownCloud Infinite Scale — think Nextcloud, but with a Go backend that skips the database entirely [1][2].
• Who it’s for: European public institutions, research organizations, and SMBs that need GDPR-compliant file storage with real data sovereignty, plus technical teams that want a modern self-hosted Dropbox/OneDrive replacement without the per-user SaaS pricing.
• Cost savings: Commercial cloud storage (Dropbox Business, OneDrive for Business) runs $15–25 per user per month. OpenCloud self-hosted runs on a VPS with no per-seat license cost — you pay for hardware, not headcount [1].
• Key strength: Apache 2.0 license is genuinely permissive — more so than Nextcloud’s AGPL and light-years from closed-source competitors. The Go backend stores everything in the filesystem with no database requirement, which simplifies both deployment and disaster recovery [2][README].
• Key weakness: The installation requires multiple subdomains and a wildcard DNS setup — a non-trivial prerequisite that will catch non-technical founders off guard [5]. Third-party reviews are sparse, the project has roughly 5K GitHub stars vs. Nextcloud’s 25K+, and public pricing for commercial support is not listed.

---

What is OpenCloud

OpenCloud is a self-hosted file management and collaboration platform. You get file sync, sharing, workspaces, an integrated office suite, and access control — the combination that most teams currently rent from Dropbox, Google Drive, or SharePoint. The GitHub description is the most honest summary: “OpenCloud is the open source platform for file management, sharing and collaboration. Simple and sovereign.” [README]

The history matters here. OpenCloud is a direct descendant of ownCloud Infinite Scale (OCIS), which was ownCloud’s modern rewrite in Go. After ownCloud GmbH changed ownership, many of the core engineering team left and regrouped under the Heinlein Group, a Berlin-based open-source IT firm with 30 years of history [5]. The gnulinux.ch write-up puts it plainly: OpenCloud grew out of ownCloud Infinite Scale after the investor transition, and the people who knew the codebase best moved with it [5]. This means OpenCloud is not a weekend project — it carries years of serious enterprise file-sync engineering under the hood, even if the GitHub star count doesn’t reflect that yet.

The technical choices are deliberate. The backend is written in Go. There is no relational database — all data lives in the filesystem under $HOME/.opencloud/ by default [README]. Authentication delegates to OpenID Connect, using either an external identity provider (Keycloak being the obvious pick) or the embedded LibreGraph Connect IdP that ships out of the box [README]. The result is an architecture that’s genuinely simpler to reason about at failure time: no Postgres replication to debug, no Redis cache to invalidate. If your disk is healthy, your data is healthy.

The project is maintained by OpenCloud GmbH, a subsidiary of the Heinlein Group. It sits at approximately 4,982 GitHub stars [merged profile] — small relative to Nextcloud, but growing, and backed by a company with paying enterprise customers rather than just volunteer momentum.

---

Why people choose it over Nextcloud, ownCloud, and Seafile

The available third-party coverage is thinner than for Nextcloud or Activepieces — there are no aggregated Trustpilot reviews, no dedicated comparison blogs. What exists is a LinuxLinks feature roundup [1], a German tutorial video [5], and the official documentation [2]. Reading across them alongside the homepage, a consistent positioning emerges.

Versus Nextcloud. This is the main fight, and it’s where OpenCloud’s architecture differentiates itself most clearly. Nextcloud runs on PHP with a relational database (MariaDB/Postgres) and Redis. That stack is proven but operationally heavier — more services to keep alive, more places for performance to degrade at scale. OpenCloud’s Go backend and filesystem-only storage is a simpler operational model, and the database-free design is particularly attractive for organizations that want straightforward backup strategies [README][2]. The Apache 2.0 license is also notably more permissive than Nextcloud’s AGPL, which matters for service providers who want to embed the platform or white-label it without triggering copyleft requirements.

Versus ownCloud (classic and Infinite Scale). This is where the lineage story becomes relevant. OpenCloud is ownCloud Infinite Scale, continued by the people who built it, under a new name and ownership structure [5]. The old ownCloud classic (PHP-based) is a different product line with a different architecture. If you’re evaluating ownCloud vs. OpenCloud, you’re essentially choosing between the legacy codebase and its spiritual successor.

On European data sovereignty. OpenCloud leans hard into the GDPR and public sector angle — the website explicitly calls out public authorities, research institutions, and educational organizations as primary audiences [website]. The Heinlein Group’s positioning as a zero-trust, on-premise-first provider resonates with European IT buyers who’ve spent years explaining to auditors why their files are sitting on US-based infrastructure. The “simple and sovereign” tagline isn’t marketing fluff for this audience; it’s the procurement checkbox.

On maturity and community. The honest counter-argument: Nextcloud has a decade of production deployments, thousands of plugins, and an enormous community. OpenCloud, despite inheriting OCIS engineering, has a smaller ecosystem. If you need a specific third-party integration or a community forum answer at 2am, Nextcloud wins on depth.

---

Features

Based on the README, official documentation, and the LinuxLinks feature roundup:

File management core:

• Fast, clean UI with keyboard shortcuts for file selection [1]
• Drag and drop upload [1]
• Powerful search: by name, full-text, OCR, file type, date, or tag [1]
• File history with version tracking and restore [1]
• Multi-device sync with offline access [1]
• Reliable fault-tolerant file synchronization [1]

Sharing and collaboration:

• Flexible sharing options: internal users, groups, public links [1]
• Workspaces — dedicated project folders designed for team collaboration [1]
• Real-time collaboration via integrated office suite [website]

Office and integrations:

• Collabora Office integration (bundled or external) [5]
• ONLYOFFICE integration (configurable) [5]
• Markdown Editor (ToastUI) [1]

Access and authentication:

• OpenID Connect with external IdP support (Keycloak, etc.) [README]
• Embedded LibreGraph Connect IdP for simpler setups [README]
• SSO support [merged profile]
• Two-factor authentication [website]
• Flexible access rights and permissions [website]

Security:

• Encryption [website]
• Secure versioning with ransomware protection described [website]
• Full GDPR compliance framing [website]
• Security contact: security@opencloud.eu [README]

Architecture:

• Go backend, no database dependency [README]
• Filesystem storage under ~/.opencloud/ [README]
• Docker and Docker Compose deployment [2][5]
• Quick install one-liner available [2]

What’s notable by absence: no native mobile app repository was mentioned in the sources, no app store comparable to Nextcloud’s plugin ecosystem, and no public roadmap page was available at review time.

---

Pricing: SaaS vs self-hosted math

This is where the review gets blunt: OpenCloud’s commercial pricing is not publicly listed. The website has a “Licences & Support” menu item and mentions both on-premise and SaaS-via-partners options, but no pricing tiers, no per-seat numbers, no self-hosted vs. managed comparison table [website]. If you need a commercial support contract or managed hosting, you contact sales.

The software itself is Apache 2.0 — free to download, self-host, and run [README]. What you pay for is the infrastructure and optionally enterprise support.

Self-hosted cost floor:

• Software: $0 (Apache 2.0)
• VPS: $6–20/mo depending on user count and storage (Hetzner, Contabo)
• Domain with wildcard DNS: ~$10–15/yr
• Your time: non-trivial (see Deployment section)

Comparable SaaS products for reference:

• Dropbox Business Plus: $20/user/month (minimum 3 users = $60/mo baseline)
• Microsoft 365 Business Basic (OneDrive 1TB + Teams): $6/user/month
• Google Workspace Business Starter: $6/user/month
• Nextcloud Enterprise: pricing by quote, similar to OpenCloud

For a team of 10 on Dropbox Business, that’s $200/month, $2,400/year. A self-hosted OpenCloud instance on a $20/mo Hetzner server handles the same workload at $240/year. The math works — but only if you have someone who can set it up and maintain it. If you’re paying an engineer $150/hr and it takes 8 hours to deploy and 2 hours/month to maintain, the break-even horizon is not as immediate as it looks.

---

Deployment reality check

The gnulinux.ch tutorial [5] is the most candid picture of what setup actually looks like, and it reveals the main friction point: you need multiple subdomains.

OpenCloud’s architecture runs several services (the main server, Collabora Office, ONLYOFFICE, Traefik reverse proxy) as separate containers, each needing its own domain or subdomain. That means you need a wildcard DNS setup — either a proper domain with wildcard support or individual subdomain records [5]. The tutorial walks through DynDNS wildcard configuration specifically because this is the step that blocks home lab setups without a real domain.

What you actually need:

• A Linux VPS or home server with Docker and Docker Compose
• A domain with wildcard DNS (or multiple subdomain records)
• Port forwarding (80/443) if running at home [5]
• Let’s Encrypt certificates (handled via Traefik in the recommended setup) [5]
• Admin email and password for initial setup [5]
• Enough storage for your files

The quick path: The documentation offers a one-liner installer [2]:

curl -L https://opencloud.eu/install | /bin/bash

This is the happy path for people who want to evaluate quickly. For production, the Docker Compose clone-and-configure path is what the tutorial covers [5].

What can go sideways:

• The wildcard domain requirement is the most common early blocker for non-technical users [5]. If your registrar doesn’t support wildcard DNS or you’re using a free dynamic DNS service, you may need to configure individual subdomains manually.
• The embedded LibreGraph Connect IdP works for single-instance setups, but if you’re integrating with an existing Keycloak or Azure AD, the OIDC configuration requires reading the documentation carefully [README].
• There are no third-party reviews documenting real production incidents — the review base is thin. This isn’t a red flag, but it means you’re taking on more unknown-unknowns than with a more battle-tested tool.

Realistic time estimate: 1–2 hours for a Linux-comfortable user following the documentation. Half a day to a full day for someone who hasn’t configured reverse proxies or DNS before, including troubleshooting the wildcard domain and Let’s Encrypt certificate provisioning.

---

Pros and Cons

Pros

• Apache 2.0 license — genuinely permissive. You can self-host, embed in products, offer as a managed service to clients, or white-label without legal complications [README]. Nextcloud’s AGPL has more strings attached for service providers.
• No database required — the Go backend stores everything in the filesystem [README]. Fewer moving parts, simpler backups, easier mental model for failure analysis.
• ownCloud Infinite Scale heritage — the engineering behind this codebase predates the GitHub repo. This isn’t a from-scratch project [5].
• SSO and OpenID Connect built in — not gated behind a paid tier [README][merged profile]. This is table stakes for organizations with existing identity infrastructure.
• Rich file capabilities — OCR-powered search, file versioning, workspaces, and integrated office editing are present out of the box, not as add-on purchases [1].
• European company, European compliance posture — Heinlein Group’s 30-year track record and explicit GDPR/zero-trust framing matters for EU public sector procurement [website].
• Clean UI — LinuxLinks specifically calls out the fast, simple, clean interface [1]. The homepage screenshots support this.

Cons

• Wildcard domain requirement raises the deployment bar for non-technical founders who don’t already manage DNS [5]. This is a real blocker, not a minor inconvenience.
• Small third-party review base — no Trustpilot profile, no G2 reviews found, no major head-to-head comparisons with Nextcloud from independent sources. Hard to calibrate community-reported bugs or long-term stability.
• Smaller ecosystem than Nextcloud — Nextcloud has hundreds of apps. OpenCloud has integrations with Collabora and ONLYOFFICE, but no equivalent plugin marketplace at this stage [1].
• Commercial pricing opaque — no public pricing for support contracts or managed hosting [website]. If you need an SLA, you’re going into a sales conversation without anchors.
• ~5K GitHub stars vs. Nextcloud’s 25K+ — smaller community means fewer community-written guides, fewer Stack Overflow answers, fewer third-party tutorials to fall back on when something breaks.
• No mobile app details in sources — unclear whether first-party mobile clients are production-ready or rely on third-party WebDAV clients.

---

Who should use this / who shouldn’t

Use OpenCloud if:

• You’re a European public institution, university, or research organization that needs GDPR-compliant self-hosted storage and the “sovereign” framing matters to your procurement committee.
• You’re a managed service provider who wants to resell a file-sync platform to clients without AGPL triggering copyleft obligations — Apache 2.0 is the right license for this.
• You have a technical person who can set up Docker Compose, configure DNS, and maintain a VPS, or you’ll pay someone to do it once.
• You want a database-free deployment model that simplifies your operational footprint.
• You’re migrating away from ownCloud Infinite Scale specifically — OpenCloud is the natural continuation of that codebase [5].

Skip it (pick Nextcloud instead) if:

• You need a mature plugin ecosystem — calendar sync, contacts, Talk video calling, hundreds of community apps. Nextcloud has a decade of extensions; OpenCloud doesn’t yet.
• You want large community forums, extensive documentation, and thousands of how-to guides written by other users. Nextcloud wins on sheer community volume.
• Your team is non-technical and you need a managed SaaS option with transparent pricing — Nextcloud has several well-established hosting partners with published pricing.

Skip it (stay on Dropbox/Google Drive) if:

• Your team has fewer than 5 people and you’re paying less than $50/month on existing storage — the break-even against a self-hosted setup is not there yet.
• Nobody on your team can manage a Linux server, and you have no budget to pay someone who can.
• You need mobile apps that work reliably today with documented first-party support.

---

Alternatives worth considering

• Nextcloud — the dominant self-hosted file sync platform. Massive plugin ecosystem, huge community, AGPL license, PHP/database stack. Pick this if ecosystem depth beats simplicity [1].
• ownCloud Classic — the legacy PHP-based version that predates both Nextcloud and OpenCloud. Still maintained but not receiving the architectural investment that OCIS-based projects are.
• Seafile — leaner, faster file sync focused on raw performance and reliability. Less collaboration polish, but excellent for teams that primarily want reliable sync rather than an office suite.
• Syncthing — pure peer-to-peer sync, no central server. Perfect for individuals; not suitable for team file management with access controls.
• Immich — not a general file manager, but worth mentioning if your primary use case is photo/video backup from mobile. More focused and better at that specific job.
• Filerun — commercial (freemium) self-hosted file manager with a polished UI and built-in Google Drive-style interface. Smaller community but actively maintained.

For a non-technical founder who genuinely needs file sharing plus real-time document editing in one self-hosted package, the realistic shortlist is OpenCloud vs. Nextcloud. Pick OpenCloud if the Apache 2.0 license, database-free architecture, or European company provenance matters. Pick Nextcloud if you want the broadest ecosystem and the most community support.

---

Bottom line

OpenCloud is an honest answer to a real question: what do you run if you want a self-hosted Google Drive equivalent, with permissive licensing, a modern Go architecture, and no database to maintain? The ownCloud Infinite Scale heritage gives it an engineering foundation that the GitHub star count undersells. The Apache 2.0 license makes it a legitimate option for managed service providers and organizations that need to embed file management into larger platforms without AGPL complications.

The honest caution is the ecosystem gap. Nextcloud has a decade of momentum, thousands of integrations, and an enormous community. OpenCloud has none of that yet — and the wildcard domain requirement means the path to a working instance is steeper than a casual installer expects. If you need a proven production system with abundant community support today, Nextcloud is the safer bet. If you’re building for European compliance requirements, want a simpler operational model, or are migrating from ownCloud Infinite Scale specifically, OpenCloud is worth the deployment effort.

If that deployment effort is the blocker, upready.dev deploys exactly this kind of self-hosted infrastructure for clients — one-time setup, you own it.

---

Sources

1. LinuxLinks — OpenCloud: self-hosted file sharing https://www.linuxlinks.com/opencloud-self-hosted-file-sharing/
2. OpenCloud Documentation — Welcome (Admin Docs, v4.0) https://docs.opencloud.eu/docs/admin/
3. gnulinux.ch — OpenCloud: Filemanagement & Sharing mit deinem eigenen Cloudserver (April 2025, Lioh Möller) https://gnulinux.ch/opencloud-filemanagement-sharing-mit-deinem-eigenen-cloudserver

Primary sources:

• GitHub repository and README: https://github.com/opencloud-eu/opencloud (4,982 stars, Apache 2.0 license)
• Official website: https://opencloud.eu
• OpenCloud GmbH: https://opencloud.eu (Heinlein Group, Berlin)