Solution blueprint

Operational AI apps on Lakebase

Lakebase is an optional managed Postgres add-on for operational data and AI apps. It serves low-latency reads and writes, syncs Gold data from the lakehouse, and gives Voir agents live operational state, so apps and analytics share one governed foundation.

Updated

How it is built

  1. Provision
  2. Sync
  3. Build
  4. Flow back
LakebaseManaged Postgres with HA and backups
Lakehouse syncServe Gold data to apps
App APIsBuild data and AI apps
VoirLive state for agents
  1. ProvisionAdd Lakebase to a workspace.
  2. SyncServe Gold tables to Postgres.
  3. BuildPoint apps and agents at Lakebase.
  4. Flow backChanges return to the lakehouse through StreamHouse.
Lakebase
Managed Postgres with HA and backups
Lakehouse sync
Serve Gold data to apps
App APIs
Build data and AI apps
Voir
Live state for agents
On this page

What is Lakebase for?

Application state, agent memory, lookups and low-latency serving.

Is it real Postgres?

Yes. Standard drivers and ORMs work.

Do we need it?

It is optional. Add it when you build operational apps or agents that need live state.

Common questions

Do we need a separate database for AI apps?

Lakebase gives managed Postgres next to the lakehouse, so apps and analytics share governed data.

Is it suitable for a startup?

Yes. See DataNature for startups and fintechs.

Implementation details

  1. Enable Lakebase, the managed PostgreSQL add-on, in your workspace.
  2. Sync Gold data that apps need for low-latency reads.
  3. Connect apps with any PostgreSQL driver over the standard wire protocol.
  4. Hold live state for Voir agents and applications, such as case status or approvals.
  5. Govern with Atlas RBAC, and keep the system of record in the lakehouse.

See it on your own data.

Book a demo

Demos and quotes are handled by Dlytica, the company behind DataNature.