OpenCloud 9.0 adds email guest access and makes sovereign sharing work without accounts
On October 27, 2026, OpenCloud shipped version 9.0 of its sovereign file-sharing platform, adding accountless guest access by email and OpenShift support. It is a rolling release: follow the documented upgrade path, then evaluate guest access if you share files with external partners.
October 27, 2026. OpenCloud ships version 9.0.0, a rolling release of its sovereign file-sharing and collaboration platform. October 27, 2026. The headline feature, guest access, lets you share with someone who has no account, identified by email. October 27, 2026. The Helm chart gains OpenShift support, and the release carries 146 bug fixes. Why it matters: the fork of ownCloud Infinite Scale closes its biggest gap against SaaS platforms — sharing with an external partner — without giving up sovereignty or the no-per-user-license model.
Guest access, the answer to the anonymous public link
Public sharing has a structural flaw: a link is anonymous. Whoever holds it has access, and no one can say who used it. That is fine for a one-off send, useless for ongoing work with a client or a contractor.
OpenCloud 9.0’s guest access cuts through the problem. You type the person’s email into the share dialog, pick a role — from viewer to editor, the same roles as an internal user — and you are done. The guest receives a single-use link, valid for 30 minutes, and starts working right away. Every access is logged against the email address: unlike a public link, a guest is always an identified person.
The mechanism is designed for minimal friction without sacrificing auditability. A session lasts 24 hours; fifteen minutes before it ends, the web client warns the guest, who renews it with a PIN sent by email. Like any share, guest access can carry an expiry date, after which no new links are issued. The administrator controls session lifetime, link and PIN lifetime, and renewal rate limits.
The limit to know: guest access is web-only, with no desktop or mobile sync. It is the right tool for an occasional external partner, not for a permanent collaborator — that person keeps a full account with a password or MFA.
The trade-off is deliberate. A public link is anonymous and ungoverned; a full account is heavyweight for someone who will never log in daily. Guest access occupies the middle — email-identified, single-use links, a renewable session — and it makes the auditing story concrete: administrators can show who had access, revoke it, and surface it in an audit log, which a public link can never provide.
A maturity release more than a rupture
The rest of 9.0 consolidates what exists rather than reinventing the product.
Search now covers tags. A search term matches tag names, not just file names and content; the matching tag is shown under each result, and the tag list becomes a first-class filter. Folders stay on top for every sort order, with a “Folders first” option you can turn off. Shares update live: a folder received appears in “Shared with me” without a page reload, and a revoked share disappears the same way — including for guests.
On the App Store side, the interface switches between grid and list, apps maintained by OpenCloud carry an official badge, and each app declares a compatible version range: if an update breaks an app, its status turns red with the explanation. Previews gain HEIC, HEIF, and AVIF support; the Apollon app adds collaborative UML diagrams; the interface is fully right-to-left for Arabic and Hebrew; and notification emails adopt a new design based on OpenCloud’s design system.
The number that sums up the discipline: 146 bug fixes, many found through AI-assisted exploratory testing. Before every rolling release, the team runs upgrade tests, exploratory tests, and the existing API/UI suites — a safety net rarely seen at this level in the self-hosted ecosystem.
Operationally, 9.0 remains a rolling release: there is no separate “stable” channel, but a continuous stream of versions tested before publication. The repository sets one explicit prerequisite — follow the 9.x upgrade instructions before switching — in part because custom email templates move from a single file to three (layout.html.tmpl, message.html.tmpl, digest.html.tmpl). A deployment that overrides the old template without adopting the new schema ends up with inconsistently rendered notifications after the upgrade.
Where OpenCloud sits in the self-hosted landscape
OpenCloud is not a newcomer. It is the fork of ownCloud Infinite Scale (oCIS), the cloud-native rewrite in Go whose components were co-developed with CERN. When ownCloud came under Kiteworks control in late 2023, part of the oCIS developer team founded OpenCloud GmbH in Berlin in September 2024, within the Heinlein group. Version 1.0 shipped in February 2025, 2.0 in March 2025 with the first commercial offering, under Apache 2.0 and AGPL-3.0 licenses.
This lineage matters: OpenCloud inherits a lightweight, single-binary Go architecture built to run on a NAS or a small VPS, without the heavy PHP stack of classic ownCloud. The “simple and sovereign” positioning targets European organizations that refuse to entrust their files to a US cloud but found the Nextcloud alternative too heavy to operate.
The Go choice is not cosmetic. Where classic ownCloud and Nextcloud rest on a multi-service, plugin-heavy PHP stack, oCIS and then OpenCloud bundle the essentials into a single binary: authentication, storage, sharing, and the API all run from one process. For a team that operates its own instance, that is less surface to maintain, patch, and secure — and a single Helm chart is enough to deploy it on a NAS, a VPS, or a Kubernetes cluster.
9.0 arrives as the ecosystem reshuffles: on the ownCloud side, the classic PHP server reached 11.0.0 on July 30, 2026, while Infinite Scale sat around 8.2.2 with a 9.0 candidate in testing. The fork now runs on its own rhythm, and version 9.0.0 marks a deliberate distance from upstream. For self-hosters tracking the space, the signal is simple: the fork now sets the pace, and the 9.0 line is where its own roadmap — guest access first — diverges from the upstream it left behind.
Verdict
If you already host OpenCloud, 9.0 justifies the upgrade for guest access alone — but it is a rolling release with a specific migration path: follow the 9.x upgrade instructions before switching, especially for custom email templates. If you regularly share files with external partners who have no account, guest access is a concrete trigger: it replaces the anonymous public link with an identified, logged, revocable partner, at the cost of web-only usage. If you are still on Nextcloud or classic ownCloud PHP, evaluate OpenCloud on two criteria: real sovereignty (hosted yourself, no per-user license) and operating cost — a single-binary Go stack is simpler to maintain than a plugin-heavy PHP stack. Guest access does not replace the full account; it adds the one thing it was missing to become a credible alternative to SaaS platforms.