Sovereignty
Your software. Your servers. Your rules.
Sovereignty means three things here: you choose where your software runs, nobody can reach in without you, and you can leave at any time.
Your side
- Your servers
- Your data
- Your admin keys
- Your secrets
Akua
- Each install’s settings and history
- Change requests waiting for approval
- The record of who did what
Convenience has a price.
A strategic dependency.
70%
of Europe's cloud infrastructure market belongs to three US companies.
Synergy Research Group, 2025
The problem
Software doesn't run by itself.
What you see is the surface. Underneath: servers, updates, security, access, backups. That is what binds people and time, and why companies hand it to a cloud provider.
Software needs infrastructure.
The product
Any software. On your server.
Choose software, provision it on your server, keep operations in view. Or just ask.
What are we building today?
- Deploy PostgreSQL
- Run a security audit
- Scale my cluster
-
Deploy
Push code or prompt an agent.Versions roll out across every cluster.
-
Ask
Your cluster, your logs, your metrics.Answered in plain language.
-
Manage
Scale, update, audit, recover.From terminal, chat, or agent.
-
Ambient agents
Always on.
Agents watch, diagnose and draft the fix. No incident goes unseen.
-
OPEN-STACK
Your model. Your IDE. Your agent. One audit log, one policy gate.
-
Human-in-the-loop by configuration.
You set the policy.Every action is logged.
-
Per-tenant isolation
Dedicated namespace, RBAC, and network policy. No shared tenancy, no incident crosses the line.
-
Unified audit trail
Agents and humans write to the same audit trail. Each action attributed to its source, each change traceable.
-
Operational SLA
99.9% uptime. Real engineers on call when something breaks.
Your data, your cloud, your region.
The big question
Can someone abroad switch off your IT?
No. Here is why, in three steps.
-
Your software runs on your servers
In your own cloud account, on a cluster you already have, or on servers in your building. The applications live there, not with Akua.
-
The connection only goes out
Your servers open a secure connection to Akua. Akua cannot open one to you. There is no door from the outside, so there is nothing to lock.
-
Cut the connection, and the software keeps running
Without Akua you lose the dashboard and updates. The applications keep running. Your keys, settings and images use standard formats you can take anywhere.
Not from outside. Not by us.
Records
Who did what, and when.
Every install keeps its own record: every change, who made it, who approved it and why. It is written as things happen, not switched on later.
The record is plain git. Clone it and keep your own copy.
Regulation
What the rules ask, and what Akua answers.
Three rules most of our customers meet. Each one in plain words.
DORA
Banks and insurers
Asks
A list of every company behind a critical service, and proof that you could leave it.
Answer
Every install records which provider, which country and which account it runs on. Leaving is standard Kubernetes: take your keys, settings and images with you.
EU AI Act
Companies using AI in regulated work
Asks
A record of what an AI system did, and who was responsible for it.
Answer
AI agents go through the same change requests as people. Who asked, who approved and what changed is written to the record.
GDPR
Every company with personal data
Asks
To know where personal data is stored, and who can see it.
Answer
Your data stays on your servers. Akua stores settings, not your records. The few optional features that send content to Akua are listed in the docs.
By design
Sovereignty the architecture can prove.
Not a setting, not a promise on a roadmap. What Akua is built on.
-
The cluster is yours
Akua runs on Kubernetes in your account or on your hardware. The machines, the cluster and the data stay under your control.
-
Standard formats only
Deployments are standard Kubernetes resources and Helm charts, not a proprietary format you would have to leave behind.
-
The export path exists
Take your kubeconfig, your charts and your images to any other Kubernetes cluster. Leaving is a decision, not a project.
-
No markup on compute
You pay Hetzner, AWS or your data center directly at their prices. Akua charges only for the control plane.
Questions
Questions your lawyer will ask.
Who holds the admin keys?
You do. Akua keeps a reference to each key, not the key itself; the value sits in a secrets store, every read is recorded, and you can take access away at any time.
Where is our data?
On your servers: in your cloud account, on a cluster you run, or in your building. Akua stores the settings of each install, not your data. A few optional features, such as AI code execution, send content to Akua; the docs list each one.
Is Akua GDPR compliant?
Your data stays where you put it, on a provider you chose, and the record of who changed what is yours to read. That is what your data-protection officer needs to check, and all of it is visible in your workspace.
What can an AI agent do in our environment?
Only what you allow. An agent has its own identity and its own permissions, it goes through the same change requests as people, a person approves the critical ones, and every action is written to the record.
Which providers work today?
Servers managed by Akua on Hetzner Cloud, your own Hetzner account, any Kubernetes cluster you already have, and servers you connect yourself.
What if Akua disappears?
Your clusters, settings and images use standard formats. They stay yours, and everything keeps running. That is the exit plan the regulator asks for.
Yours to keep.
Yours to leave.
Free to start on a managed server, or on your own cloud account from day one.