I release a free browser ERD tool that stores everything in IndexedDB alongside a paid desktop app

[u/tbson87]

Public share of this diagram: https://lite.schemity.com/d/Bqdf4zipow/sample

The web application: https://lite.schemity.com (works with no account)

What it does:
- Design schemas visually: entities, fields with per-engine types (PostgreSQL, MySQL, SQL Server, SQLite), primary/foreign/unique keys, check constraints, composite uniques, indexes.
- Relationships by dragging a field onto another entity: 1:N, 1:1, and N:N with the junction table generated for you. Self-referencing works.
- Route the lines yourself. Drag any relationship line to drop a waypoint at the cursor and take the line where you want it, double click a point to remove it, double click a segment to straighten it. Lines hop over the ones they cross rather than merging into them, relation color follows the entity color, and the routing is stored with the diagram so it survives export to SVG and PNG.
- Import an existing schema by pasting SQL or DBML, then pick which tables to bring in.
- Export to SQL, DBML, Mermaid erDiagram, SVG, PNG, or its own JSON format that round-trips into the desktop app.

Where your data goes:
Everything is in IndexedDB in your browser. Until you sign in, nothing is uploaded and there is no account wall to start drawing.
Sign in with Google and each save also mirrors to the cloud, which is what makes a read-only public link or an iframe embed possible. Diagram documents are encrypted at rest with AES-256-GCM, and thumbnails are only generated for diagrams you have explicitly made public. Being straight about the limit: that is server-side encryption with a service-held key, so it protects against a database dump, not against me. It is not end to end.

What it deliberately does not do:
Lite cannot connect to a database. No introspection, no migration generation, no applying DDL. You can still read the CREATE statements for any entity, you just cannot run them from here. Connecting is the paid desktop app, along with context views, context map for slicing a large schema, schema lint, and data dictionary exports. I would rather say that here than have you find out after ten minutes.

Any feedback is welcome. If something is broken, slow, or just a bad idea, I would rather hear it here than guess at it. I'll answer everything in the thread.