Training Example: ownCloud – Review the Data, Give Your Score & Compare to the Real AI Evaluation

Secure Cloud Platform

[H1] ownCloud
Infinite Scale

The new and most secure version of ownCloud real-time content collaboration platform.
Learn more about Infinite Scale

[IMG: ownCloud Secure file sharing]

[H2] Filesharing, trusted by 200 million users worldwide

[IMG: ownCloud customer and technology partner CERN]

[IMG: ownCloud customer ETH Zürich]

[IMG: ownCloud customer Daimler]

[IMG: ownCloud customer European Commission]

[IMG: ownCloud customer DB Mobility Networks Logistics]

[IMG: ownCloud customer Fujitsu]

[IMG: ownCloud Spaces]

[H2] Spaces

Spaces is a revolutionary project folder concept designed to boost seamless digital collaboration for remote teams of all sizes, while ensuring compliance, data control and security.  Spaces delivers an optimized user experience and significantly reduces admin workload.

[H2] Web office

Web Office provides a suite of powerful integrations: OnlyOffice, Microsoft 365, Collabora Online and Microsoft Office Online. This enables the user to collaborate seamlessly and securely irrespective of location and device.

[IMG: ownCloud Web office]

[H2] What Is the Kiteworks Open Source Program Office?
The Kiteworks OSPO is the organizational body responsible for open-source strategy, governance, licensing, community health, and ecosystem engagement. It is led by the Vice President, Open Source Program Office at Kiteworks, operates under the ownCloud brand, and sustains the platforms, security practices, and contributor community that make sovereign open-source data exchange work in production.

[IMG: ownCloud – Secure by Design]

[H2] Secure by design

Infinite Scale incorporates state-of-the-art security standards and best practices to ensure superior data protection and privacy. Infinite Scale is designed as a three-tier architecture separating storage, backend and frontend components communicating through secure, well-defined APIs.

[H2] For organizations with high data governance requirements

Control your data – always, anytime and anywhere. Deploy ownCloud on-premises, in a data center of your choice or in a hybrid setup. Regulations and certifications? Say no more. We keep your back! With multi-factor authentication, encryption and our elaborate file lifecycle management. Looking for 100% data ownership? Let’s get in touch now.
Contact us

[H3] Do you prefer SaaS? Check out ownCloud.online!

[H2] For smaller organizations and private users

No time for infrastructure management? ownCloud.online is your best choice for data sovereignty and the flexibility of a SaaS solution. Our platform, fully hosted in Germany, lets you start right away. Keep your data safe at any time. Compliant and without any maintenance. It’s just one click away.
Start now

[H2] Control who can access your data

Give staff an easy, flexible and secure way to share files and folders. Safely involve contacts outside your organization with select documents. Share public links shielded by passwords and expiration dates.
Say goodbye to slow VPN connections, unversioned documents attached to emails and shadow IT in public clouds of questionable security.
Share flexibly

[IMG: Access Control]

R

[H4] GDPR-ready
General Data Protection Regulation

R

[H4] LGPD-ready
Lei Geral de Proteção de Dados

R

[H4] CCRF-ready
Cloud Computing Regulatory Framework

R

[H4] HIPAA-ready
Health Insurance Portability and Accountability Act

R

[H4] CCPA-ready
California Consumer Privacy Act

[IMG: Increase productivity with ownCloud filesharing]

[H2] Increase productivity

Modern teams collaborate from anywhere and from any device. Make them more efficient by enabling them to store, share and work on their data and documents through a single point of access.
Work simultaneously on documents, create presentations together in real-time, annotate files and much more, thereby saving time on coordination and feedback processes.
We believe that the needs for data sovereignty and real-time collaboration can be reconciled in private clouds. Learn how we can help you gain digital sovereignty.
Collaborate efficiently

[H3] Convenient collaboration with internal and external parties without storing data in the public cloud. Open APIs and modularity let you integrate almost everything to your ownCloud – Data sovereignty by design.

[H2] Users love ownCloud

[IMG: ownCloud has an average rating of 4.2 on Capterra]

[H3] 4.2

[IMG: ownCloud has an average rating of 4.1 on G2]

[H3] 4.1

[IMG: ownCloud has an average rating of 4.5 on Gartner Peer Insights]

[H3] 4.7

[H2] Our latest news

[IMG: oCIS “Curie” is complete and you should update to 8.0.3 now]

[H2]
oCIS “Curie” is complete and you should update to 8.0.3 now
May 13, 2026If you’re running any oCIS (ownCloud Infinite Scale) version, please update to 8.0.3; The latest patch, released on May 11th 2026, contains security fixes.
read more

[IMG: Kiteworks Launches the ownCloud Open Source Program Office — Formalizing Governance, Retiring the CLA, and Committing to Sovereign, Open, Federated File Sharing for the Enterprise]

[H2]
Kiteworks Launches the ownCloud Open Source Program Office — Formalizing Governance, Retiring the CLA, and Committing to Sovereign, Open, Federated File Sharing for the Enterprise
May 6, 2026The relaunch of the original open-source, self-hosted File Sync and Share platform brings a published governance charter, relicensing to Apache 2.0, a DCO-based contribution model, and an AI-assisted contribution policy—together with new releases of ownCloud Infinite Scale, ownCloud Classic on PHP 8.3, and a new MCP Server.
read more

[IMG: Tomorrow, we put it all in writing. See you on the other side.]

[H2]
Tomorrow, we put it all in writing. See you on the other side.
May 4, 2026Founded 2010. Forked 2016. Acquired 2023. Forked 2025. Shipped throughout.
Now: governance, a manifesto, and a codebase that’s yours.
The Kiteworks OSPO for ownCloud launches May 5.
read more

Browse our ideas and insights

[H1] Contact us

[H4] We look forward to hearing from you!

We look forward to hearing from you! Just leave us a message and we will get back to you as soon as possible.

[H5] I am interested in an ownCloud Demo

[H5] I have a general contact inquiry

[H5] I am using the free ownCloud version and need help
Thank you for choosing ownCloud to store, sync and share your data!
If you are using the ownCloud Community Edition and need support or help, please visit our community forum at central.owncloud.org.
Due to our limited technical ressources, we unfortunately cannot support Community Edition admins and users at this time. Thank you very much for your understanding.
Do you nonetheless wish or require direct ownCloud technical support? Contact us in the form below and we’ll be happy to migrate your instance to the ownCloud Standard Edition, which includes technical support. Looking forward to hearing from you!

[H5] Customer Support

Contact options for our customers and help desk.

Contact customer support

[H5] Docs & guides

Find all links to our documentation and guidelines in one place.

Go to docs

[H5] Start Enterprise trial

30-day no-risk free ownCloud Enterprise trial.

Register for trial

[H2] Stay in sync

Follow us on social media, insightful updates promised

[H4] Twitter

[H4] LinkedIn

[H4] Facebook

[H4] Blog | development | Infinite Scale | News from ownCloud | ownCloud | Release | security | Updates

[H1] oCIS “Curie” is complete and you should update to 8.0.3 now

If you're running any oCIS (ownCloud Infinite Scale) version, please update to 8.0.3; The latest patch, released on May 11th 2026, contains security fixes.

[H2] If you’re running any oCIS (ownCloud Infinite Scale) version, please update to 8.0.3 today.
The latest patch, released on May 11th 2026, contains security fixes.
The upgrade is a binary swap with no configuration changes, no migrations, nothing else to do if you were running oCIS 8.0.x before.
Now for the full story of what the Curie release series has brought since February.
[H2] Curie
Each named production release of Infinite Scale is named after a female Nobel Prize laureate, a quiet but deliberate choice. These are the women whose work shaped the scientific and humanitarian foundations the modern world runs on. Naming a release series after them is at minimum a reminder that the infrastructure we build doesn’t exist in a cultural vacuum.
The Curie series is named for Marie Curie, two-time Nobel laureate in Physics and Chemistry. The next releases in development are Deledda, after Grazia Deledda (Literature, 1926), and Ebadi (Shirin Ebadi, Peace 2003), planned for Q3.
The Curie series shipped in four production releases between February and May, with an early access RC (Release Candidate) in the first week of Q1.
Patch numbering follows semantic versioning, the team doesn’t pre-decide whether something will be a major or minor; that’s determined by what actually lands.
What landed across Curie is substantial.
[H2] Multi-instance and federation
The centerpiece of the Curie series is multi-instance oCIS.
You can now connect multiple oCIS deployments to the same Identity Provider and share resources across them.
The UI gained an instance switcher and cross-instance resource references in the user context menu.
For federated school clouds, multi-tenant enterprise setups, or the growing number of deployments that need cross-organizational collaboration, this opens use-cases that previously required significant custom work.
Federation via Open Cloud Mesh (OCM) was substantially reworked for full specification compliance at the same time, enabling proper interoperability with other OCM implementations beyond just ownCloud.
This comes with a migration note:
existing OCM invitations and shares need to be recreated after upgrading from oCIS 7.x.
If you’re running OCM in production, plan for that window.
OCM permission change notifications for federated contexts were fixed in a subsequent patch, and internal link access control was tightened.
[H2] Security and hardening
Alongside the federation work, Curie brought a round of security improvements that are worth naming explicitly:
Public link brute-force protection is now enabled by default:
up to five failed password attempts per hour before a link is locked, with the threshold fully configurable.
The Referrer-Policy was tightened to no-referrer, removing any cross-origin leakage from outgoing requests.
PROXY_FORCE_STRICT_TRANSPORT_SECURITY was added to deployments where oCIS terminates behind an upstream proxy that was swallowing HSTS headers.
Server-provided strings are now properly escaped before rendering in the UI a category of issue that belongs in a security review regardless of whether a known exploitation path exists. Then there’s 8.0.3, which closes runtime-level CVEs in Go and libvips.
Many reasons you should Update now.
[H2] Office integration
The collaboration service (the WOPI layer that connects oCIS to e.g. Collabora) gained the ability to blacklist specific file extensions from specific editors.
In compliance environments where document type routing needs to be policy-controlled rather than left to users, this was a missing configuration knob.
A persistent user-facing error in OnlyOffice view-only mode was also closed.
OnlyOffice sends a WOPI Lock request every time it opens a document, even when the user only has read access. The oCIS WOPI handler was trying to acquire a write lock regardless of view mode, failing with a permission error that OnlyOffice surfaced as an error dialog on document load. The fix returns 200 OK immediately for read-only and view-only modes without touching the lock state which is exactly what the WOPI specification requires. If users were getting error pop-ups when opening shared documents they couldn’t edit, this is what closed it.
[H2] Identity and LDAP
Enterprise LDAP setups got meaningful attention across the series:
The Graph service can now provision users against an external ID attribute from LDAP rather than always generating its own, with a switch to enable it.
This is relevant for AD setups where the authoritative identifier lives upstream and oCIS shouldn’t be minting its own.
A regression that was writing empty externalID values to LDAP on user creation (blocking creation entirely in many configurations) was patched quickly.
Group creation was fixed to respect the objectClass configured in the server rather than always falling back to groupOfNames.
And a new environment variable (OCIS_LDAP_GROUP_ADDITIONAL_OBJECTCLASSES) lets you attach additional objectClasses to groups at creation time, closing a gap for LDAP schemas that require groups to carry multiple values.
This is common in enterprise AD and some OpenLDAP setups.
[H2] Spaces and permissions
The permission model was extended in two directions:
The space role set gained SpaceEditorWithoutVersionsWithoutTrashbin full edit rights without access to version history or the trashbin.
The previous step, SpaceEditorWithoutTrashbin (added in 7.2), removed trashbin access and this goes one step further; it’s designed for contexts where edit rights need to be granted without exposing file recovery capabilities: contractor access, compliance-constrained project spaces, environments where version history is a data governance concern.
The REPORT WebDAV method now returns spaceid in its responses, matching what PROPFIND already returned.
Clients that needed to correlate search results back to a specific space were carrying a workaround for this; now they don’t have to.
A more subtle but production-relevant fix:
the middleware responsible for reconciling space memberships was running on every authenticated request, including signed URL requests used for file downloads. Signed URL auth doesn’t carry OIDC claims. The middleware interpreted “no claims” as “remove this user from all project spaces”, and did so, only to re-add them on the next regular OIDC request. That oscillation produced transient “space not found” errors and intermittent download failures with nothing obvious in the logs to explain them.
The fix is to skip reconciliation entirely when no OIDC claims are present in the request context.
[H2] The user experience
The User Interface received a few great features and fixes:
A proper crash page in the Curie series: a bounded failure state with a clear message, rather than a blank screen when something goes wrong during load.
The search bar got a layout fix (search text was overlapping the search icon).
The share button was being obscured when a sharing role had a long display name, pushing it out of the visible area and making certain sharing flows completely inaccessible.
External members weren’t appearing in the “Shared with” section at all, which made federated and external share recipients invisible in the sharing panel.
[H2] The release pipeline
Something changed structurally in how Curie was delivered.
For years, oCIS used Drone CI: a self-hosted setup driven by a multi-thousand-line Starlark configuration file that orchestrated everything from unit tests to multi-architecture Docker builds, S3 artifact caching, e2e test suites against a live stack, Helm chart publishing, and the signed release tag flow.
Running it meant owning the infrastructure underneath it.
Moving a pipeline of that complexity to GitHub Actions isn’t a weekend project.
The caching strategy needed rebuilding from scratch across a Go monorepo of around 50 internal services.
Shared infrastructure dependencies had to be recreated.
The release signing flow had to be re-orchestrated.
Every step had to be verified to produce equivalent artifacts, because the quality gates don’t move just because the plumbing did.
The transition completed mid-series.
Earlier Curie patches were still published by the ownClouders automation account; the most recent two came out of github-actions.
The pipeline is stable.
The practical upside: no more runner infrastructure to maintain, native integration with GitHub’s security tooling, and a release process readable by any contributor who knows GitHub Actions rather than ownCloud-specific Drone Starlark.
For a project that launched an OSPO and retired its CLA specifically to lower the barrier to external contribution, that alignment matters.
[H2] What’s coming: Deledda and Ebadi
The quarterly cadence puts an early access in the first week of each quarter, with GA (General Availability) gated by QA (Quality Assurance).
If you’re wondering why there’s no Deledda RC (Release Candidate) yet given that Q2 is well underway, yes, we’re running late; the CVE-2026-33634 Trivy/Aqua supply chain incident in March consumed significant bandwidth across engineering, communications, and customer-facing work. The CI (Continuous Integration) migration also ran long.
The Deledda RC will land when it’s clean, not on a calendar date we can no longer hit.
Ebadi enters development in Q3.
Both releases are shaping up on the public roadmap.
The community forum is the right place to push for features or fixes you need while those cycles are still being scoped.
[H2] Upgrade now
Update to 8.0.3 from any 8.0.x version as it’s a binary swap no configuration changes, no migrations.
If you’re coming from 7.3.x, the only thing that needs attention is OCM: existing federated invitations and shares need to be recreated as documented in the 8.0.0 release notes. Everything else upgrades cleanly.
oCIS 8.0.3: github.com/owncloud/ocis/releases/tag/v8.0.3
Full Curie changelog: github.com/owncloud/ocis/releases

Go to news overview



[H4] ownCloud



[H4] May 13, 2026

[H3] Read now:

[IMG: Kiteworks Launches the ownCloud Open Source Program Office — Formalizing Governance, Retiring the CLA, and Committing to Sovereign, Open, Federated File Sharing for the Enterprise]

[H2]
Kiteworks Launches the ownCloud Open Source Program Office — Formalizing Governance, Retiring the CLA, and Committing to Sovereign, Open, Federated File Sharing for the Enterprise
May 6, 2026The relaunch of the original open-source, self-hosted File Sync and Share platform brings a published governance charter, relicensing to Apache 2.0, a DCO-based contribution model, and an AI-assisted contribution policy—together with new releases of ownCloud Infinite Scale, ownCloud Classic on PHP 8.3, and a new MCP Server.
read more

[IMG: Tomorrow, we put it all in writing. See you on the other side.]

[H2]
Tomorrow, we put it all in writing. See you on the other side.
May 4, 2026Founded 2010. Forked 2016. Acquired 2023. Forked 2025. Shipped throughout.
Now: governance, a manifesto, and a codebase that’s yours.
The Kiteworks OSPO for ownCloud launches May 5.
read more

[IMG: Tomorrow, we put it all in writing. See you on the other side.]

[H2]
Open source EFSS is not a stepping stone to a sales call
May 3, 2026You chose open source for a reason. We respect that reason.
Why oCIS isn’t a funnel, a trial, or a hobbled community edition.
read more

[H1] About us

[H4] Rooted in open-source culture, engineering for enterprise use

ownCloud develops and provides open-source software for content collaboration, allowing teams to easily share and work on files seamlessly regardless of device or location.
More than 200 million users worldwide already use ownCloud as an alternative to public clouds – and thereby opt for more digital sovereignty, security and data protection.

[H3] Installations

[H3] Users

[H3] Enterprise customers

[H2] History
ownCloud was founded by in 2010 as an open-source project to host and sync files, and 2011 as a company to support institutional customers. In 2012, ownCloud landed the first paying customer. As an open alternative to services like Dropbox, it quickly became one of the most popular open-source projects in the world with more than 1,000 contributors. In 2014, ownCloud received a funding round of 6,3 million dollars and passed the mark of 1 million users. In 2016, one of three co-founders, Frank Karlitschek, left the company, forked the project and started his own firm to pursue another vision.
The team committed itself to make open source work for the corporate realm and large scientific endeavours – not despite being open source, but because of it. ownCloud incrementally improved on its core, added features, integrations and fortified its Enterprise Edition.
In 2018, ownCloud was included in the Gartner Magic Quadrant for Content Collaboration Platforms (CCP) as the only open-source software in the world.
In 2019, ownCloud became available as a service at ownCloud.online, tailored to meet the needs of small and medium businesses.
Today, working mostly remote, roughly 75 staff at ownCloud develop and support the market-leading open-source content collaboration software. It allows groups of people in companies, schools, institutions and government to seamlessly share and work on files regardless of device or location. More than 500 enterprise customers and a grand total of 200 million users worldwide already use ownCloud as an alternative to public clouds – and thereby opt for more digital sovereignty, security and data protection.
The near future will see the introduction of ownCloud Infinite Scale, a new ownCloud rewritten from the ground up in Go, as well as a new, decoupled user interface based on Vue.js. Those innovations make ownCloud even more stable, secure and fast.

[H2] What Is the Kiteworks Open Source Program Office?
The Kiteworks OSPO is the organizational body responsible for open-source strategy, governance, licensing, community health, and ecosystem engagement. It is led by the Vice President, Open Source Program Office at Kiteworks, operates under the ownCloud brand, and sustains the platforms, security practices, and contributor community that make sovereign open-source data exchange work in production.

[IMG: Klaas Freitag]

[H4] Dr. Björn Momsen
Managing Director

[IMG: Klaas Freitag]

[H4] Dario Pefettibile
Managing Director

[H2] Career
Join us on our quest for digital sovereignty and become part of one of the 25 largest open-source projects worldwide.
See job openings

[H2] Press
We are happy to answer enquiries from media and press. In addition, we provide curated releases and media assets.
Go to newsroom