// the find
kubero-dev/kubero
A free and self-hosted PaaS alternative to Heroku / Netlify / Coolify / Vercel / Dokku / Portainer running on Kubernetes
Kubero is a self-hosted PaaS that wraps Kubernetes complexity behind a Heroku-style UI — pipelines, review apps, add-ons, and GitOps without writing Helm charts yourself. It's aimed at small teams or solo developers who already have a Kubernetes cluster (or want one) but don't want to maintain raw manifests per app. The operator pattern means all config lives in etcd, so there's no separate database to manage.
The no-external-database architecture is a genuine design win — app state as Kubernetes CRDs means you get etcd's HA and backup story for free. Review apps triggered by PRs is properly implemented, not bolted on — it builds, deploys, and cleans up automatically. The add-on list is wide and honest about deprecations (Bitnami charts are marked deprecated with a reason, not quietly left to rot). The CLI installer handles cluster provisioning on GKE/DO/Linode, which removes the biggest setup hurdle for people who don't already have a cluster.
The add-ons labeled 'built in' are explicitly not HA-ready, which means any stateful workload that matters requires you to configure the external OLM operators anyway — the convenience layer stops exactly where it hurts most. Storing everything in etcd is great until you hit etcd's size limits or need to query deployment history at scale; there's no escape hatch to an external DB if that becomes a problem. NestJS + Vue is a reasonable stack but it's a fat TypeScript monolith in a world where the Kubernetes control plane is already complex — debugging a misbehaving operator through two layers of abstraction (NestJS service → Operator SDK → k8s API) adds real friction. The Bitnami deprecation is in progress but not done, which means new installs can still accidentally use deprecated add-ons if they don't read the table carefully.