Blogs
Insights on secure data exchange, digital sovereignty, and open source — from the team that built the platform.
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.
Kiteworks Open Source Program Office (ownCloud)
Kiteworks empowers organizations to manage risk in every send, share, receive, and save of sensitive content, protecting over 200 million end users across thosuands of global enterprises and government agencies. The Kiteworks Open Source Program Office is the steward of ownCloud, the open-source platform for sovereign secure data exchange, file synchronization, and collaboration. Built from the ground up in Go with zero database dependency, ownCloud Infinite Scale scales from a single binary to million-user deployments. Guided by a published governance charter and Apache 2.0 licensing, the OSPO ensures ownCloud remains a transparent, community-driven digital commons.
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.
Kiteworks Launches the ownCloud Open Source Program Office — Formalizing Governance, Retiring the CLA, and Committing to Sovereign, Open, Federated File Sharing for the Enterprise
The 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.
Tomorrow, we put it all in writing. See you on the other side.
Founded 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.
Open source EFSS is not a stepping stone to a sales call
You chose open source for a reason. We respect that reason.
Why oCIS isn’t a funnel, a trial, or a hobbled community edition.
How a school cloud with millions of users runs on software you can fork tomorrow
One of Europe’s largest EFSS deployments (1.8 million users) runs on the same oCIS you can fork tomorrow.
No enterprise edition. No paywall. Same code.
Digital sovereignty is not a label you buy from a hyperscaler
Digital sovereignty is not a data center location. It’s control.
Why the hyperscalers’ “sovereign cloud” branding fails the test, and how oCIS doesn’t.
What two forks and a Lessons Learned document can teach you about trust
Most open source projects bury their history. Ours is published.
What two forks can teach you about how trust actually works.
Twelve documents, zero marketing slop: anatomy of an open source manifesto
Editing matters more than writing.
Anatomy of an open source manifesto in twelve documents, with the corporate slop cut and the operational policies added.
Stewardship is not the same as control: A governance charter for people who’ve been burned before.
Kiteworks controls ownCloud’s roadmap. Why we are being highly visible about this and what it means.
Your PR was written by an AI. We don’t care. (But we do have rules.)
We don’t care if an AI wrote your pull request. Last year a community member shipped two oCIS extensions that way. Here are the four rules that make it work.
I’m a script kid running an OSPO. That’s the point.
What volunteering with Germany’s disaster-relief agency taught me about running an OSPO: the most valuable person in a crisis isn’t the most technical one.
What 108 repositories taught us about open source hygiene
Sixteen years. 108 repos. One map. What an archaeological dig through the ownCloud GitHub org taught us about contributor experience and open source hygiene
PHP 8.3. Yes, for Classic. Yes, we heard you.
PHP 7.4 went end-of-life. Your auditors noticed. You asked, so ownCloud Classic will now run on PHP 8.3, so you can stay compliant while you plan the migration to oCIS.
We killed our own CLA. Here’s why that’s a good thing.
We’re retiring the ownCloud CLA and adopting the Developer Certificate of Origin. Here’s the reasoning and why contributors should take notice.
What happens when you fork twice, get acquired, and keep shipping anyway
Some context into ownCloud history, the 2 forks and what happened.