About
A deploy platform that owns none of the hardware.
Kaja is a deploy platform for infrastructure you already own. You connect a Kubernetes cluster, and you get push-to-deploy, rollbacks, domains, HTTPS, managed databases, logs and metrics across every cluster in your organization — without handing anyone a kubeconfig, and without opening a port.
What we believe
- The hardware should not be the product
- Most platforms with a good deploy experience sell you the machines it runs on, and the experience ends where their fleet does. Kaja sells none, which is why it works the same on a hyperscaler, a rented box and a rack in your building.
- Unreachable is normal
- A great deal of real infrastructure has no public address and never will — inside a customer's network, behind CGNAT, on a segment with every inbound port closed. We treat that as the ordinary case rather than the unsupported one.
- Kubernetes should be underneath, not in front
- You should not need to write a manifest to ship a web service. But everything Kaja creates is still a standard Kubernetes object, so the day you want to look underneath, there is something there to look at.
- Say what isn't finished
- The homepage carries a section listing what Kaja cannot do, and the security page states what the agent is allowed to do in your cluster. Both cost us signups and both stay.
Where it is
Kaja is free to use today, on any number of clusters. It carries no SLA and no compliance certification, which is worth knowing before you plan around it. What it can and cannot do is listed on the homepage, and what it does inside your cluster is on the security page.
Get in touch
Questions, a bug, something that did not work on your cluster, or a security report — it all comes to the same place and we read it.