Enterprise as text.
Run by humans and machines together.

You leave with a decision you can keep true. Not a report of one — the model the decision was made in, in your own repository, and the method to keep it current after we are gone.

Architecture-as-Code for the enterprise — the git-native, text-first discipline software already has, carried up to the strategy, business and architecture layers that code-scoped tools never reach.

Two ways in

5 minutes · nothing to set up

Draw a diagram

Write a few lines of text, see a diagram. Install the Studio extension and open any file — the diagram renders in your editor as you type.

Install Studio →
team · methodology-first

Set up an architecture repository

Adopt Transitrix for your organisation. One prompt to a coding agent scaffolds a structured repository and CI validates every change.

Methodology quick start →

What this is

Architecture-as-Code for the enterprise — the git-native, text-first discipline software already has, carried up to the strategy, business and architecture layers that code-scoped tools never reach.

Against code-scoped tools. Architecture-as-Code exists today and stops at software. The layers where the money is committed — motivation, strategy, business — are the ones it never reaches, and they are the ones this covers.

Against context and memory layers. This is a formal model, not free-form notes and not opaque embeddings. It validates, it diffs, and a change to it is reviewed the way a change to code is reviewed. A machine can act on it because it is grounded, not because it was remembered.

The stack

Two units are open today. Two more extend the same thesis.

methodology · open

Transitrix

The foundation. A text-native way to model an organisation — goals, processes, capabilities, and structure — as code. Says how to describe an enterprise so it remains readable, versionable, and executable.

View on GitHub →
tool · open

Transitrix Studio

The unified editor extension and CLI to author and preview Transitrix formats — the reference implementation of the methodology. Previews the full Transitrix notation set, from BPMN process diagrams and goal trees to capability maps, FGCA, and process blueprints, with live preview as you type.

Install →
On the roadmap
strategy product · not yet public

Transitrix DSM

Dynamic strategy management that operates on the Transitrix model, updating as the enterprise model changes — not yet publicly available.

More on Transitrix DSM →
research · phase 2

Transitrix Swarm

A research platform for modelling what agents do inside a Transitrix-described enterprise. The behaviour layer of the stack. In narrative; not in active development in the next six months.

Neither is open. See what they do and how to see them working →

See it work

A few lines of text become a diagram you can read, review, and version. You author a Transitrix file in VS Code; the preview renders alongside it as you type.

Transitrix Studio in VS Code: a goals-tree source file on the left; on the right, the preview redraws live as a new goal is added, showing the branch appear.
Transitrix Studio — a Transitrix source file and its live preview, redrawing as you edit.

One model, every layer

You describe your enterprise once, as text. Two editor extensions render that single model across every layer — so the same source serves the boardroom and the codebase.

Built on open standards — ArchiMate 3.2 and BPMN 2.0 — with everything as plain, diffable text. Nothing is locked in: the technical views are standard PlantUML and Mermaid, and your files stay readable with or without our tooling.

What's open today

Both the methodology and Transitrix Studio are public. The methodology specification lives at github.com/transitrix/methodology. Transitrix Studio — an editor extension and CLI — installs into VS Code, Cursor, VSCodium, Windsurf and IntelliJ IDEA; see the install options. Source at github.com/transitrix/transitrix-studio. For the exact shape of every notation, see the DSL examples reference; recipes — prose with directives, named *.<kind>.ttrs — are described on the .ttrs recipe format page.

If you are evaluating Transitrix for a pilot or want to follow the work, reach out at hello@transitrix.com.

Follow releases — subscribe via Atom/RSS: Transitrix Studio · Methodology. Add either URL to any RSS/Atom reader, or use GitHub's Watch → Releases on each repository.

Free reference material

Cheat sheets, templates and worked examples — read on the page, take the PDF away. No sign-up, no email, no gate. Browse the library →

Explainers

One subject per page, in more depth than this front page goes. Read the explainers →

Learn

Eight steps from "What is this?" to your first diagram. About 20–30 minutes. Start the learning path →

Questions, answered