How Hamlet uses Databricks Lakebase Postgres to test changes against production data

Databricks has published a customer story describing how Hamlet, an AI-powered platform that makes local government decision-making accessible, uses Lakebase Postgres to test changes against production data. The write-up frames the work as a testing practice: validating changes against real production data rather than only synthetic or staged datasets.
Lakebase is Databricks' managed Postgres offering, which places a Postgres-compatible database alongside the broader data platform so teams can run transactional workloads near their analytics and AI work. In practice, testing against production data usually means cloning or branching a database so engineers can exercise migrations, queries or application changes on realistic volumes and distributions before promoting them, a pattern familiar from tools like Neon and other Postgres branching services. That is my own reading of the setup; the announcement itself centers on Hamlet's use of the platform for this testing workflow.
The story does not detail Hamlet's architecture, the size of its datasets, latency or cost results, or specific internal tools used to run the tests.
Why it matters: Teams building AI products on government and other sensitive data face pressure to catch regressions before they reach users, and pairing a Postgres workload with the analytics platform they already use can simplify that loop. For developers, the takeaway is that production-like test data is becoming a standard part of the Postgres toolchain; for product teams, it signals that database branching and cloning are increasingly evaluated alongside performance and price. Whether this approach scales to very large or tightly regulated datasets remains an open question, in my inference.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
Hamlet, an AI-powered platform that makes local government decision-making accessible...