Hosted in Switzerland
Our security model
What we protect, how we do it – and what is technically not possible.
Encryption at rest
Each customer has their own encrypted volume (AES-256, LUKS2). The key is generated randomly, stored only wrapped in our separate key service and handed to the server in memory when the volume is opened. Stolen or decommissioned disks are unreadable.
Encrypted backups
Backups are encrypted before they leave the server, with a separate key per customer. The backup location only ever sees encrypted data.
Encryption in transit
All connections use TLS. Your services run in a stack of their own, isolated from other customers.
Access by our team
No routine access to customer data. Emergency access (e.g. a support case you request) requires two people, is logged in an append-only audit log and you are informed.
The honest limit
Search, face recognition and text recognition only work if the server can process your data while it runs. That is why we do not advertise “zero knowledge” encryption – we would rather be precise than make promises we can't keep.
Third parties
Payments: Stripe (card data never reaches us). Optional login with Google or GitHub: the provider learns that you log in. Optionally connected GitHub repositories: we only read the ones you share. The optional assistant sends your question and the relevant excerpts to an AI provider – only if you book it.
Ready for your own cloud?
Choose your services, see exactly what you pay – and your cloud is ready in minutes.