Run Zeus on your hardware, or ours. Same product, same price.
Some teams need every credential to stay on their own servers. Others want to hand the operations to us. Zeus supports both — self-hosted on your own hardware, or fully managed with KMS encryption. Pick based on what your security requirements demand.
The control plane, on your terms.
Most SaaS tools have one deployment model: their cloud, their rules, and access to your configuration that you can't control. That works for a lot of teams. For others — especially those with compliance requirements around data residency — it's a blocker.
Zeus runs wherever makes sense. Deploy it on hardware you own and it operates entirely within your network. Secrets, IAM credentials, and cluster configuration never leave your infrastructure — our cloud only ever sees a license check and a token validation. Prefer not to operate it yourself? We run it for you, with all data encrypted using KMS from AWS or GCP with keys in your account.
One thing that doesn't change between modes: your clusters always run on your own infrastructure. EKS clusters live in your AWS account. GKE clusters live in your GCP project. Proxmox and bare-metal clusters run on your own hardware. Zeus is the control plane that provisions and manages them — not the infrastructure itself. Whichever deployment mode you choose, the clusters are yours.
From zero to running.
Choose your mode
Self-hosted if you need data residency or want full control over your instance. Cloud-hosted if you'd rather not operate the control plane. You can switch later.
Install or sign up
Self-hosted: one install command on your server, then link it to your account. Cloud-hosted: sign up and we provision the instance — you're managing clusters in minutes.
Connect your infrastructure
Link your AWS or GCP accounts, Proxmox nodes, or bare metal servers. In self-hosted mode, those credentials go into your instance and stay there.
Add your team and go
Invite team members and set roles. Auth runs through your identity provider or Zeus's built-in auth. Both modes look identical from your team's point of view.
Built by people who run this in production.
No hand-waving. Here’s what’s actually under the hood: the kind of detail you’d expect from a platform you’re going to trust with production.
Questions you’d actually ask.
What exactly reaches the Zeus cloud in self-hosted mode?
A periodic license check and an auth token validation. No cluster configuration, no secrets, no IAM credentials, no kubeconfigs. Your private data never leaves the instance.
Can I switch modes later?
Yes. Zeus configuration is exportable. You can start cloud-hosted, decide you want your own hardware, and migrate — or go the other direction. We'll help.
Who can access my cloud-hosted instance?
Only you and team members you invite. ZeusK8s staff cannot read your data. We have access to infrastructure-level metrics (CPU, memory usage) for SLA monitoring, but not to your configuration or secrets.
Does self-hosted get the same updates?
Yes. Zeus checks for new versions and notifies you in the UI. You apply them when you're ready. We don't push updates to self-hosted instances without your action.
What about compliance requirements like HIPAA or SOC 2?
Self-hosted gives you the data residency controls most compliance frameworks require. Cloud-hosted with KMS encryption also satisfies many requirements. If you have specific compliance needs, talk to us — we'll tell you which mode fits.
Is there a performance difference between modes?
None. Both modes connect directly from Zeus to your clusters. The control plane location adds no meaningful latency to cluster operations.
Keep exploring.
All features →Identity, policy, compliance.
Explore →One encrypted credential store.
Explore →Plans for every stage.
Explore →Start running it today.
Spin up your first cluster free, or get a guided tour from our team.