Pricing
Your compute is never metered.
Kaja runs on hardware you already pay for, so there is no per-container, per-build-minute or per-gigabyte-of-logs line item to model. Every feature is free to use today, on every cluster, for everyone on your team. One resource is counted: the traffic our gateway carries for clusters that have no public address of their own.
What applies today
The limits actually enforced on your account.
Not a trial with a card on file. This is the whole list.
- Everything, freeNo billing
- There is no payment integration in Kaja at all, so nothing can be charged for even by accident. No plans, no card, nothing to cancel.
- Servers, apps, projects, membersUnlimited
- No cap on connected clusters, on apps or projects inside them, or on the people in your organization.
- Compute, builds, storage, logsNever metered
- It runs on hardware you already pay for. It costs us nothing, so there is no line item for it and there will not be one.
- Gateway traffic10 GiB / month
- The one thing counted, and only for clusters with no public address of their own. Traffic through your own load balancer never counts.
Why traffic is the one thing counted
It depends on whether we are in the path at all.
Kaja publishes apps two different ways, and only one of them sends your users' traffic through us.
Your cluster has a public address
Not measuredYour domain points straight at your own ingress or load balancer. A visitor connects to your hardware directly. Those bytes never touch our infrastructure, so we cannot count them and do not try. There is no allowance on this path because there is nothing for an allowance to limit.
Your cluster has no public address
CountedBehind NAT, inside a rack, on a machine with every inbound port closed. Nothing can dial in, so the agent holds one outbound connection open and our gateway becomes the public front door for your app. Every request and response is carried over bandwidth we rent and are billed for by the gigabyte. That is the one cost your traffic imposes on us, so it is the one thing we count.
The allowance is 10 GiB a month. Go past it and gateway routing pauses until the month rolls over, which leaves your apps running and anything on your own load balancer untouched. Nothing is billed, because there is nothing to bill with. The gateway docs cover how the path works.
Managed control plane
We run the dashboard, the build coordination, and the gateway. You connect your servers with one command, and the agent only dials out, so nothing needs to be exposed. This is what everything above describes.
Self-hosted control plane
Run all of Kaja inside your own network with no dependency on us at runtime, for data residency, sovereignty, or air-gap requirements. Nothing leaves your network, so no traffic is counted at all. The charts exist and the docs cover it. Tell us what you need and we will help you stand it up.
Questions
What is free, and what is counted.
- What does it cost right now?
- Nothing, and not in the sense of a free trial. There is no payment integration in the product, so there is no mechanism to charge you. Everyone has the same access to every feature.
- Is my compute really free?
- Yes, and it is the one promise here that does not depend on our goodwill. Your apps, builds, logs, and metrics run on clusters you own and pay for already. They cost us nothing to run, so there is no per-container, per-build-minute, or per-gigabyte-of-logs line item, and there never will be.
- Why is gateway traffic the exception?
- Because it is the only part of your application's path that runs on infrastructure we pay for. When a cluster has no public address, our gateway is what makes it reachable from the internet, and it carries every byte in both directions over bandwidth we rent. Everything else you do on Kaja happens on your own hardware.
- How do I avoid using the allowance at all?
- Give the cluster a public address and publish through your own ingress or load balancer. Traffic then goes straight from your visitors to your servers without passing through us, and nothing is counted. Most clusters in a cloud or with a static IP work this way already.
- What happens if I go over the allowance?
- Gateway routing pauses until the month rolls over. Your apps keep running, and anything served through your own load balancer is unaffected. Nothing is billed, because there is nothing to bill with. If you are near the limit and it matters, tell us and we will raise it.
- Will Kaja stay free?
- Probably not forever, and we would rather say so than imply otherwise. There is no paid plan to sell you today. When that changes you will hear about it well before it takes effect, and it will price the control plane and the gateway. Your compute will still not be metered, because it is not ours to meter.
- What happens to my apps if I stop using Kaja?
- They keep running. Everything Kaja creates is a standard Kubernetes object in your own cluster, so losing the dashboard does not take your workloads down. That is what no lock-in has to mean to be worth saying.