Introduction

Titanbase is an open-source, local-first visual schema designer for relational databases. Design your schema visually, save it as a portable .titan.json file, validate it locally, and export developer-ready PostgreSQL, Mermaid, Prisma, and Drizzle outputs.

Your schema shouldn't be locked to one tool or one workflow. Titanbase keeps the model (.titan.json) separate from the output (generated SQL and schema files), so the file you author stays portable and reviewable.

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│  Visual Editor   │ ──▶ │  .titan.json │ ──▶ │  Exporter         │
│                  │     │  (your file) │     │  (pure transform) │
└─────────────────┘     └──────────────┘     └──────────────────┘

• The editor runs locally in your browser — no account, nothing uploaded.
• .titan.json is your source of truth — a portable file you keep in version control.
• Exporters are pure functions: schema in, files out.

Available now#

• Local web editor — design tables, columns, relations, indexes, and enums on a canvas.
• .titan.json save / load — open and save your schema as a portable file.
• Validation & diagnostics — local schema checks before you export.
• Export Titan JSON — the canonical .titan.json.
• Export PostgreSQL SQL — CREATE TABLE, constraints, indexes, and foreign keys.
• Export Mermaid ERD — an erDiagram for Markdown and docs.
• Export Prisma schema — models, enums, and relations.
• Export Drizzle (PostgreSQL) schema — pgTable, pgEnum, and column builders.
• PostgreSQL .sql import — bring an existing schema in from a local file.
• Schema diff & PostgreSQL migration drafts — compare two schemas and generate review-ready SQL.
• Native desktop app — free, open-source Electron app for macOS, Windows, and Linux.
• 16 example templates — real-world starting points.

Planned#

These are on the roadmap and not available yet:

• CLI.
• DBML, MySQL, and SQLite exporters.
• Neon / Supabase presets.
• Cloud collaboration.

See the CLI and Titanbase Cloud pages for details.

Start here#

Why Titanbase#

• Local-first — your schemas live as files on your disk. No account, nothing uploaded.
• Open source — the editor, schema engine, and exporters are open under Apache-2.0.
• Git-friendly — .titan.json is plain JSON you can review in pull requests.
• No lock-in — the format is documented. Export to a supported target whenever you need to.