Architecture that stays true to the code
Compass exists to close the gap between the system you designed and the system you're actually running.
Every team starts with a clean architecture diagram. Then the code gets written, services get added, events get renamed, and within a few sprints the diagram is fiction. Nobody trusts the map any more, so nobody updates it.
Compass starts from one idea: the design and the code should be the same thing. You describe your services once, Compass creates each one's project from your team's own template, in whatever language you write, and it keeps checking: when the code and the config disagree, the drift check (compass check drift, by hand or in CI) tells you. The diagram can't go out of date, because it's drawn from the code itself.
What we believe
One source of truth
The topology, the services, the event wiring and the drift checks all come from a single model. There's nothing to keep in sync by hand.
Code humans write comes first
A new service starts as an ordinary project in its language, or from your own template, and from then on the code is yours. Saving records it; Compass never rewrites it.
Any language, one workspace
Services sit side by side whatever they are written in: each started from a template or brought in as it is, filed in its domain and drawn on the same diagrams. Each builds from the app the way its own folder says.
How Compass is built
Compass ships as a single Rust binary. One engine draws the diagrams, makes the services' projects and checks for drift, so the three can never disagree about what your system is. Configuration lives as code-friendly JSON you can review in a pull request; operational state, sessions and secrets live in a local store — the secrets encrypted — that stays out of your repository.
See the idea in motion
Walk the product tour, then start free and watch design, code and drift stay in lockstep on your own workspace.