We started building Stackdome in 2024 as a hobby project. The idea was to package the tooling in the CNCF/cloud-native ecosystem into an opinionated platform, so that developers can get a well engineered platform without learning Kubernetes YAMLology or a dozen other projects from the CNCF landscape.
Railway and Render did this well for their hosted products. I wanted to bring that level of polish and DX to something you can self-host. Stackdome uses Kubernetes underneath, but it's completely transparent to users. (I have some ideas for an expert mode that exposes more of the bells and whistles.)
My day job involves working with cloud native technologies, and it made me appreciate how much is already solved by Kubernetes and the tooling around it. If you are already running Kubernetes, Stackdome is something you can adopt incrementally. (I have some ideas around adopting already-running workloads.)
Features:
- First class support for multi-service applications, shown on a canvas in the UI (inspired by Railway). You can edit, wire up, and create resources from the canvas.
- First class support for multiple clusters. Stackdome acts as the hub and places workloads across clusters (hub and spoke).
- Self hostable, from a small VPS to a large cluster.
- Managed Postgres with WAL archiving, HA, backups, and PITR (CNPG underneath).
- A release system for the whole stack. A release targets everything, and you can roll it back if something breaks.
- Source to image, with an in cluster registry (Zot).
- Disposable preview environments, which can also be multi-service.
- Declarative apps via a Stackfile, deployed with the CLI.
Website: https://stackdome.com
Docs: https://docs.stackdome.com
Repo: https://github.com/Stackdome/Stackdome
Try it on our cloud, no credit card and no compute to bring: https://cloud.stackdome.com
Happy to hear your feedback and questions.