AgentDB / Lake

Your data, in your bucket. Forever.

AgentDB Lake keeps the entire history of your database on cloud object storage you own. It scales with your storage bill, not with your anxiety — and it outlives any machine it runs on.

Your bucket, your keys.

The whole database — every table, every version, every audit entry — lives on S3-compatible storage in your account. Nothing leaves your cloud, and no vendor holds your history hostage.

Nothing acknowledged is ever lost.

A write isn't confirmed until it's durable in the lake. If the machine dies mid-write, the record doesn't — that isn't a promise, it's a test that runs on every change.

Machines are replaceable.

When a server fails, a new one opens the same bucket and picks up exactly where the last one stopped — with a fence that guarantees only one writer ever holds the pen.

Studio's audit trail over a lake-backed engine: every commit with its LSN, action, target and outcome — the durable record itself.
The record itself, unretouched — every commit, every actor, every outcome, in order, on storage you own.
Under the hood

For the evaluating engineer.

The lake is not a backup target bolted onto a database — it is where the database lives. The commit log, the cold tier, and the proof chain are all objects in your bucket.

Shared commit log on object storage

The WAL itself lives on S3-compatible storage (hand-rolled SigV4, no SDK) with per-tenant lanes. Commit durability is one object write — RPO=0 by construction, not by replication.

Fencing & takeover

A writer lease with conditional-create fencing guarantees single-writer semantics; remote takeover is tested with kill -9 and real S3, not simulated.

Hot backup, in place

Online backups pin a cold epoch and export while writes continue — to a directory or straight to the bucket. Restore is: point at the files and boot; byte-faithful, LSN-preserving.

Tamper-evident history

Every WAL byte folds into a blake3 chain; checkpoints are ed25519-signed. An auditor can verify the whole history offline with only a public key — agentsql verify.

Tiered by temperature

Hot MVCC in memory, cold columnar segments (zstd, zone maps, bloom filters) in the lake. Old versions tier out automatically; nothing is deleted until an operator says so.

Encryption at rest

AES-256-GCM per frame with envelope-wrapped keys — age, Vault transit, or AWS KMS — and online key rotation. Feature-gated; your compliance posture decides.

The record outlives the machine. That’s the Lake.