When to use Yantra Studio

Each page below starts from a situation rather than a feature. If one of them describes where you are, it says what changes when the work is done in a model instead of in slides and spreadsheets — and what it will not do for you.

Architecture tools are usually sold on what they contain. That is not how the decision gets made. The decision gets made when something has become painful enough to justify changing how the work is done: an estate nobody can describe, a migration with no scope, an auditor asking for the reasoning behind a design nobody wrote down.

So these pages are organised by the pain, not by the menu. Where a page names a capability, that capability is real and the link goes to the page that documents it. Where it names a limit, the limit is real too.

You have inherited something

You are about to change something

Someone is going to ask you to justify it

You are designing for a particular industry

Put your architecture under version control

Model it, govern it, and keep it true to the system it describes.