About us
Eight years of database diagrams.
We started DrawSQL in Sydney in 2018. Founder-owned, profitable, and focused on building a product that lasts.
The idea came from a simple frustration. Before DrawSQL, Dennis worked at a digital agency where a 132-table schema lived in Confluence as a single MySQL Workbench file. It was the team’s source of truth, but every update meant downloading it, editing it locally, and uploading it again for everyone else.
That was not collaboration. A shared desktop binary file was never going to be a good team workflow.
That’s where DrawSQL started: database diagrams in the browser, made for teams.
The small team behind DrawSQL
Dennis
Founder and builder.
Writes most of the code.
Uses DrawSQL to build DrawSQL.
Has strong opinions about every canvas interaction.
Avy
Runs everything that isn’t code.
Quietly decides half the roadmap.
Loves talking to customers.
If you’ve ever asked for a feature, she’s probably the one who flagged it.
Where it’s going
The canvas is still the point.
AI is changing how development teams build. It writes code, generates migrations, and updates schemas faster than anyone can keep in their head. By the time you check, the database you remember may already be out of date.
That makes shared context more important, not less. We’re leaning in.
The next version of DrawSQL is built around one idea: the shared database diagram becomes the central context for your schema. Humans, AI, and CI all write to it, review it, and plan from it. It becomes the place where schema changes are understood before, during, and after they ship.
Code will keep moving faster. Schemas will keep changing. The canvas is still where everyone meets.