I'm Son Tran, a software engineer, and I build Schemity - the offline desktop ERD tool this site is about. Schemity is not a product I designed for an imagined user: it is the tool I reach for every working day. I design and maintain production schemas of dozens of entities with it, running the full loop it was built for - design the model on the canvas, hand the SQL to implementation, connect the live database, and let re-sync keep the diagram honest as the schema evolves.
That daily use is where the product decisions come from. Features like context views, the reviewed migration SQL diff, and plain JSON storage you can version control with Git all exist because I hit the problem myself first - usually on a schema I was responsible for in production. When something on this site claims a workflow works, it is because it is the workflow I use.
The same goes for the writing. Every post on the blog starts from a real problem database designers face - researched, sourced, and matched against what Schemity actually does - because an ERD tool for software engineers should be documented the way engineers think: problem first, tool second.
Schemity's principles are simple: your schema is yours, so it stays on your machine - no cloud, no subscription, one-time purchase. If you want to talk databases, tooling, or anything on this site, reach me at [email protected] or on the Discord community.