Diagrams in Git, on branches, with history

Your repository, not ours

Connect a GitHub App installation, choose the repository and branch, and diagrams are written there. The source of truth stays somewhere your organisation already backs up, audits and controls access to.

Branches, history and merges

Work on a branch while a diagram is under review. Browse version history to see what a diagram looked like at any point. Merge one diagram into another when two lines of work need to come back together.

• Per-diagram branches
• Version history with restore
• Diagram-to-diagram merge
• Workspace-wide and per-diagram connection settings

Paired with generated models

Because an architecture model can be generated from a codebase and re-imported as a merge, versioned diagrams and generated diagrams reinforce each other: the diff you review is the architectural change, in the same repository as the code change that caused it.

What this covers in the product

Every capability below is part of this area of Yantra Studio.

• GitHub
• Repository
• Branches…
• Version history
• Merge diagram…

Questions

Related capabilities

• Diagrams that go through review, not around it

  Put architecture diagrams through a real approval workflow: draft, review, approved, with reviewers, an audit log and validation gates that block submission.

• Architecture diagrams generated from your codebase

  Import an Archify model of your codebase and get an architecture diagram where every component links to the file, lines and commit that prove it exists.

• Access control that goes down to the row

  Single sign-on with OIDC, multi-factor authentication, session policy, workspace roles and row-level access control on every record.

See all 21 feature areas →