Skip to content
SchemanticBeta

Private beta · early access open

Turn database schemas into documentation people actually understand.

An interactive ER diagram and the meaning behind every table — living documentation, rendered from your DBML.

Free during betaPrivate by defaultNo lock-in
northwind · documentation.htmlReady to share
Try it yourself

The problem

ER diagrams show structure. They don't explain meaning.

The shapes are right there. The understanding isn't — so everyone who opens the file is left guessing what it actually means.

northwind · documentation.htmlReady to share no context attached
shop
customer
PKid
email
shop
order
PKid
FKcustomer_id
total_centsint
billing
invoice
PKid
FKorder_id
billing
payment
PKid
FKinvoice_id
What is this for?
Who owns this?
Safe to drop?
PII in here?

New engineers

ask what every table is for.

Onboarding stalls on tribal knowledge that lives in one person's head — not in the repo.

Clients

can't read raw schema docs.

A wall of column types isn't a deliverable. It's homework you've handed to someone else.

PMs & auditors

need context, not types.

They're asking what a table means and why it exists — not whether a column is nullable.

How it works

From raw DBML to a handoff people understand.

No new tooling and no export dance — just the schema you already have, turned into something anyone can read.

  1. 01Add

    Start with the DBML you already have.

    Paste it, type it, upload a .dbml file, or drop one in — or load a sample. No new format to learn.

    schema.dbml
    // shop + billing
    Table shop.order {
    id bigint [pk]
    customer_id [ref: > customer.id]
    total_cents int
    }
    Table billing.invoice {
    order_id [ref: > order.id]
    }
  2. 02Generate

    Get an interactive ER map.

    Tables grouped into colour-coded modules, with every relationship traced and drawn.

    er-map
    Shop Billing2 relationships
    shop
    customer
    PKidbigint
    emailvarchar
    shop
    order
    PKidbigint
    FKcustomer_id
    total_centsint
    billing
    invoice
    PKidbigint
    FKorder_id
  3. 03Understand

    See the context behind each table.

    Click any table for what it references and what depends on it — the meaning, not just the columns.

    detail
    shop
    order
    PKidbigint
    FKcustomer_id
    total_centsint
    shop.orderricher guides · coming next
    • References shop.customer
    • Referenced by billing.invoice
    • 4 columns · 1 enum (status)
  4. 04Share

    Save it once. Share a living link.

    Save the docs as a private project, then share a public, revocable link — it always shows your latest save.

    workspace / northwind Saved
    v3 · rendered just now
    private · versioned · re-render anytime
    /s/x7Kq… link live

What you get

Structure you can see. Context you can read.

From the system-wide map to a single table's meaning — what every generated doc gives the reader who opens it.

Interactive ER map

See how the whole system connects.

Tables, types, enums, and every relationship — grouped into colour-coded modules and laid out so you can follow each foreign key across the model.

InteractiveCrow's-foot relationships
Shop Billinghover to trace
shop
customer
PKidbigint
emailvarchar
shop
order
PKidbigint
FKcustomer_id
total_centsint
billing
invoice
PKidbigint
FKorder_id

Context for every table

Click a table, understand what it is.

A click opens a detail panel: what the table represents, an at-a-glance of its keys and connections, and what depends on it. Rich plain-English guides are the next layer.

AI guide layer · coming next
2 · shop
order
Shop module

What this table is

Operational record

A live business process — one purchase, placed by a customer and settled by an invoice.

At a glance

6
columns
2
keys
1
depends on
2
used by
AI guide layer · coming next

Trace a path across the model

Follow one record end to end.

Hover any table to light up its relationships today. A guided, narrated journey across the model is on the way.

Hover to trace · liveGuided journey · coming next
customerorderinvoicepayment

order → references customer · referenced by invoice

Your workspace

One living doc. Always current.

The whole model renders into a single interactive document that carries your brand, not ours. Save it privately to your workspace — every save keeps a version — then share a public, revocable link that always shows your latest save.

White-label outputPrivate projectsShare by link
workspace / northwindSaved
v3 · rendered just now
private · versioned · re-render anytime
Share link · live

Sample output

This is the doc your reader opens.

Not a screenshot — the actual generated documentation, running live in your browser.

northwind-handoff.htmlReady to share

Use cases

Built for the moment you hand a database to someone else.

One living document works for every audience — clients, new hires, product, auditors, and your own team.

  • Agencies & consultancies

    Hand clients a database they can actually read — a deliverable, not a schema dump they email back with questions.

  • New-engineer onboarding

    New hires meet the system as a map — what each table is for and how it connects, not a schema to decode on day one.

  • Product & PMs

    Give product the context behind the data model — no meeting, no translation layer required.

  • Audit & compliance

    Reviewers see meaning and relationships, with your inline notes carried through — context, not column types.

  • Internal architecture docs

    Living documentation generated from the schema, so it stays honest instead of rotting in a wiki.

The difference

Stop handing over silent schemas.

A raw ERD tells people what exists. Schemantic tells them why it matters.

Before · raw ERDerd.png
o_hdr
id
usr
ttl
ldgr_x
id
o_ref
amt
What is ldgr_x?Who owns o_hdr?
After · explained handoffReady to share
shop
order
PKidbigint
FKcustomer_id
total_centsint
shop.order
  • References shop.customer
  • Referenced by billing.invoice
customerorderinvoice

Why trust it

Product proof, not logos.

No customer wall yet — so here's what the product actually does today, and what's coming next.

<5s
from DBML to interactive docs
0
installs — it runs in your browser
100%
private — your schema is never shared
1
living doc for your whole data model
Shipped today
  • Works from standard DBML

    dbdiagram-compatible — no rewrites.

  • Interactive ER map

    Modules, keys, and crow's-foot relationships.

  • Click any table for detail

    What it is, its keys, and how it connects.

  • Accounts & private projects

    Sign in, save your schemas, organize by project.

  • Versioned saves

    Every save keeps a snapshot you can reopen anytime.

  • Share by link

    A public, revocable link that always shows the latest version.

  • No lock-in

    Standard DBML in — your schema stays portable, forever.

On the roadmap
  • Private share links

    Password-protected and workspace-only links.

  • Comments & notes

    Collaborative review notes on any table.

  • AI guide layer

    Plain-English what & why per table — human-reviewed before it ships.

  • Guided sample journey

    One record narrated across the whole model.

  • SQL & live-DB import

    Beyond DBML — CREATE TABLE dumps and live introspection.

Pricing

Free while we're in beta.

Rendering is free today, and a free account lets you save your work. Here's the shape of the paid plans we're planning — provisional, and not live yet.

Free

Available now
$0

Try it, and document public or open-source schemas.

  • Render interactive docs in your browser
  • Public share links, revocable anytime
  • Up to ~15–25 tables
  • Built-in sample schemas
  • Limited AI credits (when AI lands)

Pro

Planned
~$19/mo

For solo devs and freelancers.

  • Everything in Free
  • Private projects
  • Unlimited tables
  • Full AI authoring (metered)
  • White-label output + private links
Coming soon

Team

Planned
~$59/mo

For small teams and agencies.

  • Everything in Pro
  • Collaboration & shared workspace
  • Comments & notes
  • Private share links
  • More AI credits
Coming soon

Business

Planned

~$179/mo for ≤25 users — CI/CD API + GitHub Action, drift-aware sync, higher AI quotas.

Enterprise

Planned

Custom — self-host / open-core, SSO/SAML, audit trail, and the decision/rationale layer.

Prices are provisional and not yet live · everything is free during beta

FAQ

Questions, answered.

The honest version — what the product does today, and what's coming next.

Is my schema data private?

Your work stays yours. Your schema is never shared or used for anything else, and saved projects are private to your account. Share links are strictly opt-in — and you can revoke one at any moment.

What input do you support?

Standard dbdiagram-style DBML: schema-qualified tables (e.g. Table public.user { … }), columns with pk / not null / unique / notes, enums, and Ref relationships. Importing SQL / CREATE TABLE dumps and connecting a live database are on the roadmap.

Do I need an account?

Not to render — paste your DBML and explore the full interactive docs free, with no sign-up. Create a free account when you want to save your schemas as private projects and share them by link.

What exactly do I get?

An interactive ER diagram with colour-coded modules and crow's-foot relationships, plus a detail panel for every table — its keys, what it references, and what depends on it. Explore it live in the studio, save it to your workspace, and share it with a revocable link that always shows your latest save.

Is there any lock-in?

None. Your DBML is a standard, portable format — nothing gets trapped in a proprietary store, and you can take your schema anywhere, anytime.

Is it free?

Everything is free during beta — including accounts and saved projects. Paid plans — higher limits, AI-authored guides, and team collaboration — are on the roadmap.

Private beta · limited early access

Be one of the first teams whose schema explains itself.

Everything is free while we're in beta, and the teams already inside are shaping the roadmap. Render your first doc, claim your workspace, and keep it.

Free during beta · No credit card · Your schema stays private