The ERD tool that enforces your team's naming standards
Sqemo is an ERD tool that enforces your team's database naming conventions. Design databases with a shared word list, not guesswork: model in business terms, and consistent physical names for tables and columns are generated by your team's naming rules. Off-standard names are caught in the editor and in CI, not in production.
Free · runs in your browser · no sign-up required · handles 5,000+ tables
Sound familiar?
Every team ends up with three names for the same thing. Code review catches some of it. The rest ships to production.
user_id userId usr_id user_no
Naming conventions in a wiki don't enforce themselves. Sqemo turns them into rules that run on every column you add.
Words in, consistent schema out
-
1. Define your word list and domains once
Map business terms to physical words and abbreviations — "customer" →
cust, "identifier" →id. Domains carry type and length — "status" →varchar(20). -
2. Model in business language
Name entities and attributes the way your domain experts talk. Logical and physical models stay linked.
-
3. Physical names, generated
Table and column names follow your naming rules automatically. Words missing from your list get flagged, not shipped.
Add "Customer Status" — CUST_STS varchar(20) is generated
from your word list, domains and naming rules. Change the list, and every
off-standard column is flagged and updated in one click.
In a team, the standard grows through review
-
1. The workspace owns the standard
Put the word list and naming rules in a workspace and every linked ERD generates names from the same standard. Members read it; they don't edit it.
-
2. Members propose words
Hit a word that isn't in the list? Propose it right there — with a note — instead of patching the standard yourself.
-
3. The owner approves or rejects
Approved words reach every team ERD immediately. Rejected ones never enter the standard. Nobody changes it quietly.
See the propose → approve → reject flow in a 2-minute video.
Everything else an ERD tool should do
-
Word list, domains & naming rules
A word list and domains shared through a workspace, plus a rule engine, keep every diagram on the same standard — even while editing together in real time. A compliance report proves it.
-
Logical / physical modeling
Two connected tiers, like the big modeling suites — without the license fees or the installer.
-
7 SQL dialects + DBML
Import and export MySQL, PostgreSQL, Oracle, CUBRID and more. DBML both ways.
-
Linting & a CI gate
15 rules check the model as you edit.
npx sqemo-mcp lintfails CI on any violation, and Pro checks drift against the live database too. -
MCP server for AI workflows
Let Claude or any MCP client read and edit your ERDs — modeling assistance with your naming standard still enforced.
-
Free to start, nothing to install
Runs entirely in the browser — and still opens a 5,000-table schema in seconds. Local projects need no account at all.