OpenRun is rewriting declarative web app deployment, but the DB question sits at the boundary. OpenRun can run with an embedded SQLite on a single machine or an external Postgres on multiple machines, and there’s no plan to deploy databases with OpenRun yet. The config language is Starlark, keeping deployments readable and scriptable. [1]
The OpenRun boundary OpenRun focuses on web apps and GitOps-driven deployment, not database services. Kubernetes is on the roadmap to run OpenRun as a service with auto-scaling, but databases stay outside the declarative model for now. [1]
• SQLite — embedded on a single machine. [1] • Postgres — external database on multiple machines; OpenRun supports this setup today, with Kubernetes planned for future scaling. [1]
Operational reality without a unified DB model Without a unified deployment for databases, migrations, backups and data consistency live outside OpenRun’s declarative web-app flow. That tradeoff keeps things simpler today but adds friction for stateful workflows as teams grow. [1]
Closing thought: OpenRun’s path—lean web-app declarativity plus future Kubernetes support—keeps the debate alive about whether databases belong in the same declarative deployment boundary. Watch how the Kubernetes plan evolves and whether a unified DB model appears. [1]
References
Show HN: OpenRun - Deploy web apps declaratively
OpenRun declarative deployment uses SQLite embedded or Postgres externally; plans Kubernetes; excludes database deployment
View source