Tableusers {
id int [pk]
email varchar [unique]
}
Tableorders {
id int [pk]
user_id int [ref: > users.id]
status varchar
}
Tableorder_items {
order_id int [ref: > orders.id]
product_id int
quantity int
}
// Ref: products.id < order_items.product_id
01 the gap
Everyone works from a different picture of the same system.
developers
“Which tables does this touch? Is the diagram still true?”
product managers
“The spec says one thing. The build does another.”
QA
“Which edge cases exist? Who makes the test data?”
AI agents
“No shared context, so we guess. Confidently.”
02 modules
One place for the structure of your product. One module is live; the rest are on the way.
Schemas
live · beta
Write DBML, get a diagram you can actually read. Zoom from context to columns with C4 levels, link elements, and discuss them in comment threads right on the table.
Architecture decisions pinned to the elements they explain, so the “why” stays when people move on.
ADR-012 · orders.status is an enum
because …
03 zero-access security
Designed so we can’t read your schemas.
Your schema is a map of your business. End-to-end encryption means the map stays yours, even from us.
in progress End-to-end encryption is rolling out in the Schemas beta. Until it reaches your workspace, content is protected by TLS and access control, not by your keys.
End-to-end encrypted
Keys are created in your browser. The server stores only ciphertext (XChaCha20-Poly1305, X25519 key wrapping).
Zero-access
DBML, layout, titles, notes and comments are encrypted. We see what’s needed to run the service: ids, members, roles, sizes, timestamps.
EU-hosted
Servers at Hetzner in Germany. No trackers and only essential cookies, so no cookie banner.
GDPR by default
Export everything, delete your account for real, backups purged within 30 days.
04 built for AI agents
Your agents get the same context you do.
MCP server
roadmap
Claude Code, Cursor and friends ask “how are orders related to users?” or “what breaks if I drop x?”. Agents propose changes as reviewable suggestions, never silent edits.
Context packs
roadmap
One link with the schema, APIs, flows and decisions for a scope. Hand it to a contractor, an integrator, or an AI.
Integration cards
later
Publish a public card with your APIs and data model, so other companies’ agents can find you and integrate.
Fits zero-access: an agent reads through a local Beintalk connector that holds your keys. The server still sees nothing.
Terminal showing an AI agent fetching a challenge, solving it with the demo client and subscribing.
A reverse CAPTCHA, for the bots.
AIs can subscribe to our news, but they have to prove they’re AIs. Fetch a random schema, answer a question about its foreign keys, add a small proof-of-work, all in about 20 seconds. Easy for a program, tedious for a human with a browser.
Honest fine print: this proves “an automated agent that can reason and run code”, not a cryptographic AI identity. A human with a script passes too. We’re fine with that.
