Pricing
Kubrain has one transparent price, and your agent can compute the bill in one
multiplication before creating anything. The pricing and estimate tools are
public (no token) — they are pure math over published rates, and estimate
runs the same code as create_cluster, so a quote, a dry-run plan, and a quota
admission check can never disagree.
The billed dimensions
| Dimension | Rate | Notes |
|---|---|---|
| RAM | €0.006 / GiB-hour (≈ €4.38 / GiB-month) | The binding resource. Control plane, bundled vCPU (~1 per 2 GiB), and egress are included. |
| Standard volumes | €0.05 / GiB-month | First 20 GiB free per tenant. |
| LoadBalancer public IPs | €3.50 / month each | One is used by ingress-nginx; raw type: LoadBalancer Services allocate their own. |
RAM is the one dimension that scales with your cluster shape — ram is GiB per
node. Everything else about compute (CPU, the control plane, network egress) is
bundled into that number.
Tiers
tier sets the control-plane shape; it does not change the RAM rate.
| Tier | Control plane | Workers | Use for |
|---|---|---|---|
dev | 1, schedulable | 0+ | prototypes, sandboxes |
normal | 1, dedicated | 1+ | small non-critical apps |
ha | 3, etcd quorum across ≥3 zones | 1+ | production |
Quote before you create
kubrain pricing # the rate card + tier shapes
kubrain estimate --tier ha --ram 8 --nodes 2 # exact €/hour and €/month
kubrain estimate --tier ha --ram 8 --nodes 2 --volume-gib 100 --lb-ips 1estimate returns the €/hour and €/month with a per-dimension breakdown and
creates nothing. The same numbers come back as monthly_eur in a
create_cluster dry-run and in install_addon’s monthly_delta_eur.
Worked example
An ha cluster, 3 control-plane nodes + 2 workers, all 8 GiB, with ingress-nginx
and a 100 GiB volume:
- RAM: 5 nodes × 8 GiB × €4.38 = €175.20 / month
- Volume: (100 − 20 free) × €0.05 = €4.00 / month
- LB IP (ingress-nginx): €3.50 / month
- Total ≈ €182.70 / month