Kubero — Self-Hosted PaaS for Kubernetes with Git Push Deployments

Introduction

Kubero turns any Kubernetes cluster into a Heroku-like PaaS where developers deploy apps with a simple git push. It handles build pipelines, automatic HTTPS, environment management, and add-on provisioning through an intuitive web dashboard, abstracting away Kubernetes complexity for development teams.

What Kubero Does

• Provides git-push-to-deploy workflows with automatic container builds via Buildpacks
• Manages multi-stage pipelines (review, staging, production) for each application
• Provisions add-ons like PostgreSQL, Redis, MongoDB, and RabbitMQ from a built-in marketplace
• Handles automatic TLS certificate provisioning via cert-manager integration
• Offers a web dashboard for managing apps, viewing logs, and scaling replicas

Architecture Overview

Kubero consists of a Kubernetes operator that manages custom resources (KuberoApp, KuberoPipeline) and a web UI that communicates via the Kubernetes API. When a developer pushes code, a webhook triggers the build pipeline which uses Cloud Native Buildpacks to produce a container image, pushes it to the configured registry, and rolls out the new version. The operator watches for resource changes and reconciles the desired state with running pods, services, and ingresses.

Self-Hosting & Configuration

• Requires an existing Kubernetes cluster (K3s, EKS, GKE, or any conformant distribution)
• Install via Helm chart or kubectl apply for the operator and UI components
• Configure a container registry (Docker Hub, GitHub Container Registry, or private) for image storage
• Set up a git webhook (GitHub, GitLab, Gitea, or Bitbucket) for push-to-deploy triggers
• Add-ons are managed as Helm charts; extend the marketplace with custom charts

Key Features

• Heroku-style developer experience on any Kubernetes cluster you own
• Buildpack-based builds require no Dockerfile for common language stacks
• Pipeline stages let you promote code from review to staging to production
• Add-on marketplace provisions databases and caches as managed Kubernetes services
• Multi-tenant with namespace isolation and RBAC-based access control

Comparison with Similar Tools

• Heroku — managed PaaS with per-dyno pricing; Kubero runs on your own cluster for free
• Dokku — single-server PaaS; Kubero is Kubernetes-native and horizontally scalable
• Coolify — Docker-based self-hosted PaaS; Kubero leverages Kubernetes for orchestration
• CapRover — Docker Swarm PaaS; Kubero runs on Kubernetes with richer ecosystem integration
• Portainer — container management UI; Kubero adds full PaaS workflows with pipelines

FAQ

Q: Do I need to know Kubernetes to use Kubero as a developer? A: No. The web UI abstracts away Kubernetes concepts. Developers interact with git push, environment variables, and scaling sliders.

Q: Which languages and frameworks are supported? A: Any language supported by Cloud Native Buildpacks: Node.js, Python, Ruby, Go, Java, PHP, .NET, and Rust. Custom Dockerfiles also work.

Q: Can I use Kubero for production workloads? A: Yes. It creates standard Kubernetes deployments with health checks, resource limits, and rolling updates. Production-grade features like autoscaling and persistent volumes are supported.

Q: How does the add-on marketplace work? A: Add-ons are Helm charts that Kubero provisions into the app namespace. They provide connection strings as environment variables automatically injected into your app.

Sources

• https://github.com/kubero-dev/kubero
• https://docs.kubero.dev