Cryptomator

“secure cloud vault that fits”

Pros

One thing that worked really well for me is how Cryptomator slips into an existing cloud storage setup without trying to replace the provider or its sync app. I can keep the same Dropbox or Google Drive folder layout and just add a vault inside it which makes the setup lightweight and simple to explain to other people. The vault model also lines up nicely with the way I already organize project folders. Once a vault is created and unlocked, it shows up like a normal drive, so I can open, edit and save files with the same apps I already use. Meanwhile, the cloud-synced folder only stores encrypted data which means the provider never has access to readable content. I also appreciate that filename protection is built in by design, not treated like an extra option. It is not just the contents of files that are encrypted but also filenames and folder structure details which really matters when names include client names, project codes or other sensitive information. That cuts down on metadata leakage that would otherwise happen just from syncing a folder. Day to day, the experience stays very focused. The core actions are just creating a vault, choosing where it lives, unlocking it and locking it again and the interface does not clutter things up with unrelated file management features. That makes it much easier to introduce to people who only need a safe folder in the cloud and do not want to learn a whole new storage system. Cross-platform support was also important for my use case and Cryptomator covered what I needed. I used it on desktop and Android and the same vault worked across both as long as the encrypted folder underneath stayed synced. That consistency removes a lot of friction compared with tools that rely on platform-specific formats. I also like how well this approach supports compliance-focused storage practices. Since the encryption happens locally before anything is synced, it is much easier to justify using a cloud provider for availability and transport while still keeping control over confidentiality. Pair that with a provider that has the right contractual and administrative safeguards and the whole setup becomes much easier to defend internally. On top of that the desktop pricing and distribution make it easy to evaluate and adopt gradually. I was able to test the workflow, document best practices and decide how to support it going forward without getting stuck in licensing discussions right away.

Cons

There are a few areas where it takes some extra attention. Virtual drive behavior can depend a lot on the operating system and the surrounding setup and I had to factor that in. If the sync client is still downloading the encrypted vault, the mounted view may look incomplete and it is not always clear whether the problem comes from the mount layer, the cloud client or just sync delay. A more obvious vault not fully synced message in�the app�would clear up a lot of that confusion. Performance also depends on the kind of files involved. Big files usually behave well but a large number of small files or deeply nested folders can feel slower than working in a normal unencrypted directory especially when the cloud sync client is scanning changes at the same time. I noticed that most during the first population of a vault or when reorganizing large folder trees. Another point of friction is that encrypted filenames and directory IDs in the synced folder are intentionally not human readable. That is obviously the goal but it also means I cannot count on doing emergency maintenance directly inside the encrypted directory, so I have to stay disciplined about always using the unlocked view. When someone forgets and manually changes encrypted files, troubleshooting gets painful fast.�The product�keeps things intentionally minimal which is nice in general but that also means diagnostics are limited. If something breaks, like a sync conflict, interrupted upload or mount issue, I usually end up piecing things together from operating system messages and whatever the cloud client happens to report. More useful in-app troubleshooting guidance would make support much easier.

“good open source tool”

Pros

After switching from Boxcryptor for my business, Cryptomator has been a much better fit. The interface is cleaner and more user-friendly and the fact that it's open source and free makes it even more appealing. The biggest plus is that it works flawlessly with both Google Drive and Microsoft OneDrive which are the two services we rely on with clients. I have also seen it work well with Icedrive and pCloud which is a nice bonus if you want to avoid paying extra for pCloud's encryption add-on.

Cons

At this point, there really isn't anything about this software that I dislike. My only concern is whether development will continue long term since it's an open-source project. If the team ever stopped maintaining it, we'd have to start looking for another option, although I honestly doubt we'd find one that works this well.

“complex interface and limited use”

Pros

It falls short when it comes to offering a free desktop version which would have been a major benefit. It also does not really make file storage convenient, since unlocking and locking the vault requires manual action each time. On top of that the interface is complicated and not very user-friendly.

Cons

There are also a few things about both files and filenames that feel restrictive and disappointing. It does not work well for business use which seriously limits its usefulness for a lot of users. The free version also seems to be missing features that some people would consider necessary.