Because Schemity stores diagrams as JSON, you can version control your database diagram in git exactly like source code. This is the defining workflow of a Git-native ERD tool.

How do I put a Schemity workspace in my Git repo?

The key step is Import workspace (not New workspace). New workspaces always live under ~/schemity/, but importing lets you point Schemity at any folder - including one inside your Git repository, such as docs/erd/:

  1. In the sidebar, choose Import workspace.
  2. Pick the folder in your repo where the diagram should live.
  3. Give the workspace a name.

Schemity initializes the workspace structure in that folder (so importing an empty repo folder just works) and from then on writes its JSON there. Now the diagram is tracked with the rest of your code.

How do I commit schema changes?

After editing the model, commit it like any change:

git add docs/erd/
git commit -m "Add payments entity and its relationships"

The commit history becomes a timeline of how your schema evolved.

How do I review ERD changes in pull requests?

This is where it shines. Open a pull request and reviewers see the schema change as a readable JSON diff. Pair it with the migration that implements the change so design and SQL are reviewed together:

git diff docs/erd/billing.json

A new foreign key, a dropped column, a tightened constraint - all visible in review before they reach production.

What happens if I remove an imported workspace?

If you remove an imported workspace from Schemity’s list, it only forgets the path - the folder and its files are left untouched, so your repo keeps the diagram.

Why keep your ERD in Git?

Your ERD stops being a stale picture in a wiki and becomes living documentation that moves with the code - reviewed, versioned, and trusted.

Next

Set up private AI assistance in BYOK Setup.