Launching today
RelateDB

RelateDB

Offline-first database schema designer in your browser

61 followers

Visit website
RelateDB is an offline-first, browser-based database schema designer. Model tables and relationships visually, import SQL or DBML, auto-arrange diagrams, and export SQL/DBML or images. No accounts, no cloud, no limits—everything runs locally in your browser for fast, frictionless schema design.
RelateDB gallery image
RelateDB gallery image
RelateDB gallery image
RelateDB gallery image
Free
Launch tags:Design Tools•Productivity•Developer Tools
Launch Team
AssemblyAI
AssemblyAI
Build voice AI apps with a single API
Promoted

What do you think? …

Karthik Ponnam
RelateDB
Maker
📌
I built RelateDB because most free database diagram tools I tried had friction — either the UI felt limiting, key features were locked behind paywalls, or simple workflows took too many clicks. I wanted something fast, offline-first, and frictionless: open the browser, design schemas visually, import/export SQL or DBML, and move on — no accounts, no uploads, no artificial limits. Everything runs locally in your browser, and your data never leaves your machine. I’d love feedback on usability, missing features
Zeiki Yu

Congrats on the launch — love how fast, offline-first, and no-account this is, perfect for devs who just want to sketch schemas and export SQL/DBML without any SaaS friction.

Ryan Thill

Offline-first + no-account + SQL/DBML import/export is the exact “just let me sketch a schema” experience devs want. The scale pain is keeping diagrams stable as schemas grow (auto-layout + diffing) and best practice is a deterministic layout engine + schema version snapshots so changes are reviewable/undoable 🔥 Are you storing state in IndexedDB (with shareable file export), and will you add migration diffs (v1→v2 SQL) + collaborative “share a read-only link” as next steps?

Karthik Ponnam
RelateDB
Maker

@ryan_thill  Yes, everything is stored locally in IndexedDB today, so it works fully offline and without an account.

I’m working toward proper schema snapshots + record-level diffs so things like migrations (v1 → v2 SQL) and undo/compare become possible. I’ll also add full workspace export/import for backup and portability.

Read-only sharing and cloud sync are on the roadmap as well.

Really appreciate the feedback, this is exactly the direction I want to take it.