Sovereign cloud · Switzerland

A sovereign cloud, actually in Switzerland.

A Swiss region of a US hyperscaler is still a US company under the CLOUD Act. klickops is owned and run by a Swiss company on hardware we own, so your data answers to Swiss law alone.

Live in 60 seconds Plain Kubernetes underneath Swiss · ISO 27001 / 9001

Data residency is not the same as data sovereignty. Knowing where your bytes sit is not the same as knowing whose laws govern them, and for regulated industries and the public sector, that gap is the whole point.

Data residency is not data sovereignty

A US cloud's Swiss region keeps your bytes in Switzerland, but the company operating it remains subject to the US CLOUD Act, which can compel access to your data regardless of where it physically sits.

For regulated industries, the public sector, and any team that takes its compliance obligations seriously, residency on paper is not enough. What matters is which jurisdiction actually governs access.

How klickops is genuinely sovereign

klickops runs on hardware Natron Tech AG owns and operates in Swiss data centres, certified to ISO 27001 and ISO 9001. There is no hyperscaler underneath.

  • Swiss-owned and Swiss-operated, with no US parent company in the chain.
  • Your data is governed by Swiss law alone, outside the US CLOUD Act.
  • Nothing proprietary: export every workload as clean Kubernetes YAML and leave whenever you choose.

Sovereign does not mean fewer features

klickops is a complete Container-as-a-Service, not a stripped-down compliance product. You get the full platform on real Kubernetes that Natron builds, operates and monitors for you.

  • Deploy apps from a container image or a Git repository, with automatic builds and rollouts.
  • Managed high-availability PostgreSQL, S3-compatible object storage and persistent volumes.
  • Domains with automatic TLS, a zero-trust firewall, scheduled backups, and live metrics and logs.

vs. the alternatives

See how far each one gets.

Deploy, add a database, scale, stay in Switzerland, leave clean. The others hit a wall. klickops runs the whole track.

Deploy
Database
Scale
Stay in CH
Exit clean
klickops Runs the whole track
Deploy
Database
Scale
Stay in CH
Exit clean
Railway / Vercel Your data leaves Switzerland
Deploy
Database
Scale
Stay in CH
Exit clean ·
AWS / Azure (managed K8s) A Swiss region is still a US company
Deploy
Database
Scale
Stay in CH
Exit clean ·
Self-managed K8s / VM You become the platform team
Deploy
Database
Scale ·
Stay in CH ·
Exit clean ·
built in extra work hits a wall

Frequently asked questions

What is the difference between data residency and data sovereignty?

Residency is where your data physically lives. Sovereignty is which country's laws govern access to it. Data can reside in Switzerland yet still be reachable under foreign law if the operator is a foreign company.

Is a US hyperscaler's Swiss region a sovereign cloud?

No. The data may sit in Switzerland, but the operator is still a US company subject to the US CLOUD Act, which can compel access regardless of location. That is residency, not sovereignty.

Is klickops subject to the US CLOUD Act?

No. klickops is owned and operated by a Swiss company on Swiss-owned hardware, with no US parent in the chain, so your data is governed by Swiss law alone.

What can I run on a sovereign Swiss cloud like klickops?

The full platform: containerised apps, managed PostgreSQL, object storage, volumes, domains with TLS, a firewall, backups, and metrics and logs, all on real Kubernetes you can export and leave at any time.

Sovereign by default. Swiss to the core.

Join the private beta