erdiagram.dev

ER Diagram - Design database schemas online β€” free, no signup needed

byβ€’
Simple, fast ER diagram editor β€” design databases visually without the bloat. Free guest mode, DBML import/export, version history. No signup required.

Add a comment

Replies

Best
erdiagram.dev
Maker
πŸ“Œ
Hey Product Hunt πŸ‘‹ I'm the maker of ER Diagram. This started from a small annoyance: I just wanted to sketch a database schema β€” five tables, a couple of foreign keys β€” and every tool I tried made me create an account and confirm my email before I could draw a single box. For a thirty-second sketch. So I built the thing I wanted: you land on the page and start drawing immediately. No signup, no modal, nothing in the way. Guest diagrams are saved locally in your browser, so a reload won't wipe your work. You only need an account if you want cloud sync or sharing. A few things it does: β€’ Import & export SQL DDL and DBML β€” it round-trips, so you're never locked in β€’ Drag-to-connect foreign keys, auto-layout, PNG/SVG export β€’ Prebuilt schema templates (e-commerce, blog, SaaS, hospital, and more) β€’ Works in 10 languages On the tech side: it's SvelteKit (Svelte 5) with a Canvas renderer (LeaferJS) instead of DOM nodes, so it stays smooth even with a lot of tables. It's free to use. I'd genuinely love your feedback β€” especially if you throw a messy real-world schema at it and the layout does something silly. I'll be around all day answering questions πŸ™ β†’ https://erdiagram.dev/?utm_sourc...
Saul Fleischman

@erdiagramΒ The no-signup friction removal is a refreshing takeβ€”you're right that most tools front-load auth for something that should be instant. The local browser persistence for guests is a smart move since people often sketch before committing to anything. How are you thinking about the monetization beyond cloud sync, or is that the primary lever you're exploring right now.

erdiagram.dev

@saulfleischmanΒ Cloud sync isn't really the monetization hook β€” it's more of a baseline convenience so people can pick up their work across devices without thinking about it. The stuff I find more interesting to build around is grouping, annotations, and version history. Those are the features that start mattering once a schema gets real β€” when you're collaborating, iterating on designs, or need to track how things evolved. Different design contexts need different levels of structure, and that's where I see the value landing.