One Control Plane, Three Databases: Evaluating Open Everest as a Private DBaaS for MySQL, PostgreSQL

Public database-as-a-service is convenient until the bill, the lock-in, and the data-residency questions catch up with you. In our company, we asked a direct question: could a single open-source control plane give our developers push-button databases, on infrastructure we own, across all three engines we actually use?

This talk is an honest field report on standing up Open Everest as a private DBaaS running MySQL, PostgreSQL, and MongoDB side by side on Kubernetes. We’ll walk through the architecture, how Everest’s operators and control plane fit together, and what “self-service” really looks like when a developer asks for a database. We’ll spend real time on the parts that don’t make the marketing slides: the sharp edges, the backup and sizing decisions, the security and multi-tenancy questions, and the criteria we’re using to decide whether this goes to production.