SYSTEM Cited by 1 source
LakebaseOps¶
LakebaseOps is an open-source operational platform for Lakebase DBA automation, deployed as a Databricks App and governed by the same Unity Catalog grants and audit trail as the Lakebase databases it operates on. Repository: github.com/suryasai87/lakebase-ops-platform (authored by the Thoughtworks team behind the Backstage-with-Lakebase series).
Stub page. First wiki source surfaces LakebaseOps as what the platform does on its own in the Lakebase governance story — specifically, "Three agents — Provisioning, Performance, and Health — replace 51 of the tasks a DBA used to file tickets for. Seven of them run as scheduled Databricks Jobs and replace the pg_cron crontab a DBA would otherwise hand-maintain." (Source: sources/2026-05-15-databricks-backstage-with-lakebase-part-2)
Three-agent decomposition¶
From the 2026-05-15 source:
| Agent | Role |
|---|---|
| Provisioning | Replaces ticket-driven environment provisioning, schema reviews, data-refresh requests, access grants |
| Performance | Slow-query regression detection, pg_stat-driven monitoring, branch TTL enforcement |
| Health | Live pg_stat metrics surface, 9-KPI adoption dashboard |
The three agents collectively "replace 51 of the tasks a DBA used
to file tickets for." Seven of those run as scheduled
Databricks Jobs rather than as a hand-
maintained pg_cron crontab, removing one of the canonical
operational maintenance surfaces a DBA would otherwise own.
Surfaces shipped¶
Three named UI surfaces from the 2026-05-15 source:
- Monitoring UI: surfaces "live pg_stat metrics, slow-query regressions, branch TTL enforcement, and a 9-KPI adoption dashboard."
- 9-KPI adoption dashboard: tracks platform adoption rather than per-database performance.
- Migration wizard: scores ten source engines against Lakebase, with live pricing from the AWS and Azure APIs. Named source engines: Aurora, RDS, Cloud SQL, AlloyDB, Cosmos DB, "and more".
Governance posture¶
Verbatim from the 2026-05-15 source: "both [LakebaseOps and Lakebase MCP] deployed as Databricks Apps and both governed by the same Unity Catalog grants and audit trail described above." The structural property: LakebaseOps inherits its access control from the same UC GRANT model that governs the Lakebase databases it operates on — there is no separate permission system to maintain.
What it composes with¶
- The role-shift framing: LakebaseOps is the platform-side leg of the Part 2 thesis ("the DBA shifts from doing the work to designing how the work gets done"); LakebaseOps does the routine work the DBA used to file tickets for.
- Lakebase MCP: the DBA-on-top-of- the-platform leg. "LakebaseOps runs for the team. Lakebase MCP runs with the team. Both inherit the governance posture."
- Lakebase branching from Part 1: the branch TTL enforcement loop is mechanically interesting precisely because Part 1 made branches cheap enough that unmanaged proliferation becomes a problem; TTL enforcement is the platform-side governor.
What's not disclosed¶
- The agent loop architecture (LangGraph-style? durable workflow? plain scheduled job + state in Lakebase?).
- The
pg_statingestion path (direct query? exporter? UC- federated read?). - How the migration wizard's source-engine scoring algorithm works.
- What the 9 adoption KPIs are.
- How the seven scheduled-Job replacements for
pg_cronare expressed (Asset Bundles? UI-defined? code-defined?). - The mapping between "51 of the tasks a DBA used to file tickets for" and the three agents — which tasks live with which agent.
Seen in¶
- sources/2026-05-15-databricks-backstage-with-lakebase-part-2
— First canonical wiki disclosure of LakebaseOps.
Open-source Databricks-App-deployed three-agent platform
(Provisioning / Performance / Health) replacing 51 historical
DBA tickets, with seven scheduled Databricks Jobs replacing the
pg_croncrontab, plus a monitoring UI, a 9-KPI adoption dashboard, and a migration wizard scoring ten source engines (Aurora / RDS / Cloud SQL / AlloyDB / Cosmos DB / others) against Lakebase with live AWS + Azure API pricing. Inherits governance from Unity Catalog grants + audit trail. Authored by Thoughtworks (suryasai87).