Design your services.
Build them your way. Stay in sync.
Every service in its domain, how the code fits together drawn from the code itself, and a full issue tracker with an AI agent beside every issue — one workspace for the whole team, in any language.
Architecture, code and delivery in one workspace
Open a service and its code, its architecture and its issues are one press apart — and an agent can take an issue on from there.
Architecture generated from your code
Every service and domain gets a Topology built from its source: a Tree of each file's functions, and a Map of the services, the calls between their functions and the events that connect them. It is generated from the code, so there is no second diagram to keep current.
- Tree and Map views of any service or domain
- Function cards: callers and callees, parameter tracing, models and complexity
- Several diagrams side by side in the Viewer
Architectural viewpoints, defined in the code
A slot is a one-line comment that marks a point worth drawing: where a request enters a service, an event it publishes or listens for, a step, a call or a branch. Switch the Topology to Slots only and it draws exactly those points — the architecture of a specific flow, at the level of detail your team chose, versioned with the code and redrawn as it changes.
entrywhere a request comes into the servicepublishan event it sends outsubscribean event it listens forstepa point inside it worth showingcalla call it makesbranchwhere its path divides
A complete issue tracker, with an agent beside every issue
Every service and domain keeps its issues on its Workspace tab: issues and sub-issues, a list or a board of swim lanes, projects broken into goals, labels, priorities, assignees and due dates, filters that group and order them however the team needs, and saved views. And when one is better handed off, its Work is right beside it: check out the issue's branch, and an agent works it there, in as many chats as it takes.
- List or Board, grouped by lane, project, label, priority or service
- Projects and goals, sub-issues and saved views
- Work beside each issue: Claude Code, Codex, Gemini CLI and more
Built for engineering teams
Language-aware editing
Files open read-only and the keys are modal, so reading never edits by accident. Hover a name for its type and docs, jump to its definition or find its references — Compass finds a language server for each file by itself — and a terminal for each service sits under its code.
Inherited governance
Which AIs run a scope's work, how its services build, what a new service is made from, what Commit does, and the lanes, labels and projects its issues are planned in. Set it once at the top; a domain or a service overrides only the field it differs on.
Integrated version control
Stage, discard and commit with each file's diff beside the list; branches, history, pulls, pushes and merges — conflicts included — in the same panel. While an issue's branch is checked out, the status bar is that issue and its chats.
Access control and audit
Everybody in a company works in one workspace, and your account decides what each of them may do there — read, write or administer, scoped to the domains a team owns, and security events go to an append-only, hash-chained audit log.Enterprise
Start your free trial
Make an account and Compass opens on a workspace of your own. Seven days free; cancel in that time and you pay nothing.