Questions
The ones people actually ask.
If the answer you need is not here, ask us and it will be.
- Do I need a public IP or open ports?
- No. The agent in your cluster opens one outbound connection to Kaja and keeps it open. A cluster behind NAT with every inbound port closed can still serve public HTTPS on your own domain, routed through a gateway we run.
- What do I need before I start?
- A Kubernetes cluster and kubectl access to it. If you do not have a cluster, one command installs k3s, cert-manager and the agent on a fresh machine. One thing to check first: a cluster with no default StorageClass cannot run the managed databases, because their volumes will never be provisioned.
- What happens to my apps if Kaja goes down, or I stop paying?
- They keep running. Everything Kaja creates is a standard Kubernetes object in your cluster, so the workloads, services and ingress do not depend on our control plane to keep serving. What you lose while we are unreachable is the console, not your production.
- What can the agent do inside my cluster?
- It runs with full cluster privileges, which is how one-click databases and managed ingress work. It acts on the namespaces Kaja creates, and the terminal feature re-verifies that on the agent side before opening a session. This is worth reading the security page about before you install it.
- Does my source code or my data leave my infrastructure?
- Builds clone and run on your cluster. Logs and metrics are stored on your hardware and only stream to your browser while you are looking at them. Application traffic reaches us only if you use the gateway to publish a cluster with no public address, and that is opt-in per cluster.
- Is Kaja tied to a cloud provider?
- No. There is no cloud account to connect, no IAM role to create and no provider API we call. If it runs Kubernetes and can make an outbound connection, it works the same way — a hyperscaler, a rented box, or hardware in your own building.
- What does it cost?
- It is free while it is in beta, and there is no billing integration in the product at all yet. Your compute is never metered on any plan, because it runs on hardware you already pay for. The one limit today is 10 GiB a month of traffic carried by our gateway, which only applies to clusters with no public address of their own.
- Can I leave?
- Uninstall the agent. Your apps keep running as the ordinary Kubernetes objects they already were, and you can inspect or keep every one of them.
Still deciding?
The security page covers what the agent is allowed to do in your cluster, and the homepage lists what Kaja cannot do yet.