G2

Luca P.

Chief Operations Officer DEQUA Studio | Formerly CTO in MarTech

Marketing and Advertising

Mid-Market (51-1000 emp.)

6/18/2026

"A self-hosted file platform I trust with regulated data, operational rough edges and all"

4.5/5

What do you like best about ownCloud?

Spaces is the feature that reshaped how my team works, and it is the first thing I put in front of anyone evaluating the platform. In the older ownCloud 10 model every file ultimately lived inside some user's personal namespace, so a project's documents were quietly tied to whoever happened to create them. Infinite Scale flips that. A Space is a drive that belongs to a project or a team rather than a person, with its own quota, its own managers, and roles assigned per user or per group. When a contractor rolls off or someone moves departments, the project files stay exactly where they are and the people who still need them keep their access. We spin up a Space per client engagement, hand the manager role to the lead, and stop worrying about documents stranded in an account we later have to untangle. It also makes the boundary between "my personal files" and "files meant to be shared" explicit, which is a security win on its own.

Self-hosting on infrastructure we control is the reason this is in our stack at all, and it has held up under real scrutiny. Everything sits on servers we run, in a location we choose, which means I can answer where a given file physically lives and who can reach it without hedging. For work that falls under GDPR and the data protection rules we operate beside, that is not a nice-to-have, it is the whole point. The platform leans into this with multi-factor authentication, encryption options, and an admin model built around the assumption that the data never leaves your custody. I have sat in compliance conversations where the honest answer to "where is this data" was the thing that closed the discussion, and that answer is only possible because nothing is parked in someone else's cloud.

The Infinite Scale architecture is the upgrade I did not fully appreciate until I had lived with the old stack for years. oCIS is written in Go and ships as a single binary, with no PHP layer and no separate database or identity provider required to stand up a working instance. I run it in a container, and it asks remarkably little of the hardware compared with the web-server-plus-PHP-plus-cache arrangement it replaced. The practical effect is that deployment stopped being a tuning exercise. Where I used to babysit a PHP runtime and a database to keep a busy instance responsive, the new server comes up with one command and behaves. Migrating an existing setup to it is a project in its own right, which I will get to, but the destination is a much lighter thing to operate.

The desktop sync clients are mature in the way that only matters once you depend on them daily. There are native clients for Windows, macOS, and Linux, plus mobile apps for Android and iOS, and selective sync means I am not forced to pull an entire Space onto a laptop with a small disk. Sync conflicts, when they happen, are surfaced clearly in the client rather than silently picking a winner, so I can see which file diverged and decide what to keep. That visibility sounds minor until you remember the horror stories of sync tools that quietly resolved conflicts the wrong way. Across a distributed team on three different operating systems, the clients have been the dependable layer, and dependable is exactly what I want from the piece that touches everyone's working files.

Sharing controls are granular enough to cover the awkward external cases without resorting to email attachments. I create public links with a password and an expiration date, so a file I send a client today stops being reachable next month whether or not anyone remembers to revoke it. Password-protected folders let an outside partner drop files into a defined spot without seeing anything else, and the per-Space role model means I can grant exactly the level of access a situation calls for rather than an all-or-nothing share. When the export side of the business needs to exchange documents with a customer, the link with its own controls is the mechanism, and the constant low-grade anxiety of "did that shared file ever get locked down" mostly went away.

Identity and the open protocols underneath are what let it slot into infrastructure we already run. Authentication goes through OpenID Connect against our own identity provider, so people sign in with the accounts they already have and deprovisioning happens through the directory rather than as a separate chore. There is an LDAP interface via the bundled identity component for the systems that still expect one, and the file protocols are standards rather than something proprietary: WebDAV for sync, OCS for shares, and resumable uploads so a large transfer that drops partway through does not start over from zero. I have wired it into our existing single sign-on without fighting the product, which is more than I can say for a few tools that insist on owning identity themselves.

Two smaller things round it out. In-browser document editing through the Web Office integration of your choice, whether that is OnlyOffice, Collabora, or a Microsoft path, means a quick edit does not require pulling a file down and pushing it back. And full-text search with tags makes a large Space navigable, so finding the right document is a query rather than a scroll. Neither is the reason I chose the platform, but both remove friction from the daily grind. Review collected by and hosted on G2.com.

What do you dislike about ownCloud?

The operational burden is the honest cost of self-hosting, and you should go in knowing you are signing up to run a service, not consume one. Updates, backups, monitoring, and security patching are all yours. There is no button inside the product that backs up the entire system, so my approach is to snapshot the VM and separately back up the data and configuration directories to somewhere off the box, then actually test a restore now and then rather than assuming the backup works. It is manageable and it is what I expect from anything self-hosted, but it is real work, and a team without someone comfortable owning that should weigh it carefully before committing.

The split between the legacy ownCloud 10 line and Infinite Scale is the thing I found most confusing to navigate, and the migration between them is a genuine project rather than an upgrade you click through. oCIS is deliberately leaner and focused on file sync and share, which means some pieces that lived in the old PHP world are not present in the same form. The groupware bits, calendar and contacts, were never reliable for us on the old stack anyway, breaking after updates often enough that we moved those functions elsewhere, but anyone expecting oCIS to be a drop-in continuation of everything ownCloud 10 did will need to recalibrate. The old web interface was also sluggish and needed a caching layer tuned to feel responsive, which oCIS has largely fixed, but the transition cost to get to the better place is not zero.

A few capabilities sit behind the paid Enterprise license, and it is worth knowing which ones before you assume the community edition covers your whole list. The open source build is generous and is what we run for a lot of what we do, but certain governance and admin features, the File Firewall being the example I bump into, along with official support, are part of the commercial tier. None of this is hidden or unreasonable for a company that has to fund development, and the community edition is a real product rather than a crippled trial. Just map your must-have controls against the edition you are planning to deploy so there are no surprises during rollout.

The configuration surface is deep, which is power and friction in the same breath. oCIS is a set of services driven by a long list of environment variables, and standing up a production-grade instance with the identity provider, the Web Office service, search, and the rest wired together correctly takes real reading of the documentation. I have onboarded junior admins to it and watched them get lost in the number of moving parts before the architecture clicked. The third-party app ecosystem is also smaller than the most obvious alternative in this space, so if your goal is a kitchen-sink suite with an app for every conceivable task, this is not trying to be that. It is a focused file platform, and once you accept that framing it is the right tool, but it is a framing worth setting expectations around. Review collected by and hosted on G2.com.

What problems is ownCloud solving and how is that benefiting you?

The core problem it solves is keeping regulated and sensitive files out of a public cloud we do not control. Before, the default for file sync and sharing was one of the mainstream consumer-grade services, and every one of them put our data somewhere we could not fully account for, which turned every compliance question into an exercise in caveats. Now the files live on our own infrastructure, we decide where that infrastructure sits, and access runs through our own controls. The benefit is not abstract. It is being able to give a straight answer about data residency and custody, which is the difference between a quick sign-off and a long argument when sensitive material is involved.

It fixed the orphaned-files problem that used to surface every time someone left. The old reality was that a departing employee's project documents were tangled up in their personal account, and recovering ownership meant a scramble through admin tools at exactly the moment everyone was already stressed about the departure. With Spaces, the project owns its files, not the individual, so a person leaving is an access change rather than a recovery operation. Handovers got noticeably calmer because there is nothing to dig out of a deactivated account.

Secure exchange with clients and partners moved from an improvised mess to a defined mechanism. The before-state was either emailing attachments, which is a non-starter for anything sensitive or large, or spinning up some one-off transfer tool for the occasion. Now I share a link with a password and an expiry, or hand a partner a password-protected folder to drop files into, and the access cleans itself up on schedule. The whole class of "we shared that months ago and never locked it down" worries got smaller because the controls are part of how the share is created, not an afterthought.

Running a distributed team across mixed operating systems used to mean a patchwork of tools and the occasional USB drive. People are on Windows, macOS, and Linux, and getting everyone reliable access to the same files previously involved different mechanisms for different machines, plus shares that only worked over the VPN. Consolidating onto one platform with native clients for every OS and mobile apps on top means there is a single answer to "how do I get to my files," and selective sync keeps that workable even on machines with limited disk. The fragmentation that used to fragment the team's workflow alongside it is gone.

Identity management got simpler because the platform plugs into what we already run. Previously a new tool meant another set of accounts to create, manage, and remember to disable when someone left, which is both an admin tax and a security gap. By authenticating against our existing identity provider and exposing a directory interface for the systems that need it, account lifecycle lives in one place. Onboarding adds a person to the directory and they have access, offboarding removes them and the access goes with it, and I am not maintaining a separate island of logins.

Cost and scaling stopped being a function of headcount. A per-seat subscription to a SaaS file service grows linearly with the team whether or not the usage justifies it, and that bill only goes one direction. The community edition carries no per-user fee, and the single-binary architecture scales from one modest box up to a more distributed deployment as needs grow, so the economics are tied to the infrastructure we actually use rather than to a seat count. Set against the older self-hosted stack it replaced, the lighter footprint also means less server to pay for and less to operate, which compounds the saving over time. Review collected by and hosted on G2.com.