Cloud vs self-hosted
Managed control panel versus MIT-licensed self-host. Workloads stay on your servers either way.
Both products are a control panel. Neither is “run Postgres on Kubeara’s disks.” You connect Ubuntu servers and deploy there.
At a glance
| Self-hosted | Cloud | |
|---|---|---|
| Who runs the panel | You | Kubeara (app.kubeara.dev) |
| License | MIT, free forever | Managed service |
| Servers | Unlimited | Free: 1. Paid: 5 / 25 / unlimited by plan |
| Teams / members | Unlimited | Grows with plan |
| Workload data | Your hosts | Your hosts |
| SSO, LDAP, full audit logs | Not in the free core | Enterprise plan |
| Install | Self-hosting | Register |
Cloud plans (indicative)
Published list pricing (confirm on Pricing):
- Starter — $5/month, 5 servers
- Pro — $29/month, 25 servers
- Max — $99/month, unlimited servers
- Enterprise — custom: SSO, LDAP, dedicated support, audit logs, unlimited servers/teams/members
Billing can be monthly, quarterly, or yearly. No per-seat surprise on the core story: self-hosted stays free.
Which should you pick?
- Self-host if the panel must stay on your network, you want unlimited servers at $0, or you need to inspect every line of the control plane.
- Cloud if you want us to run the panel, you are fine with metadata (account, server hostnames, encrypted credentials) on Kubeara Cloud, and you like a free 1-server trial.
You can start on Cloud and later run a self-hosted panel (or the reverse). Workloads on your VPS do not have to move.