About Sqemo
Sqemo is an ERD tool that enforces your team's database naming conventions.
Why it exists
Every team that has run a database for a while ends up with three names for the same
thing: user_id in one table, userId in another,
usr_no in a third. The naming convention is written down somewhere. It
doesn't enforce itself, and code review catches only some of the drift. The rest
ships to production, and then it is expensive to change.
Sqemo was built to put the convention where it can act: in the modeling tool. You
define a word list ("customer" → cust) and naming rules once, model in
business terms, and the physical table and column names are generated. Names that
leave the standard are flagged in the editor and in CI, not discovered in a
migration six months later. The same rules apply when an AI agent edits the model
through the MCP server, so humans and agents produce the same names.
Who builds it
Sqemo is an independent, one-person project. It is not backed by a larger company, and the person who writes the code is the same person who answers hello@sqemo.com. The product has been live since July 2026 and is used mostly by teams in Korea so far; the marketing site is published in English and Korean.
The parts of Sqemo that other tools can build on are open: the MCP server and CLI source, the sqemo-mcp package on npm, and the entry in the official MCP Registry. Walkthrough videos are on the YouTube channel.
How it is run
- The editor runs in the browser at app.sqemo.com. Local projects need no account and are stored only in your browser.
- The free plan includes the full modeling toolkit. Pro and Team pay for cloud projects, workspace members, and live-database features — see pricing. There is no ad revenue and no sale of user data.
- Comparison posts on the blog state the date on which the other product was checked, and we correct them when told they are out of date.
Contact
Questions, bug reports, and requests for a naming-standard review: hello@sqemo.com. Documentation starts at Getting started.