Surfaces.
The right guidance, at the moment it matters. From the coding agent to the pull request to Slack, every surface works from the same understanding of your system.
One understanding of your system. Surfaces are where it shows up.
Every surface draws from the same understanding of your system, so whether you're in your coding agent, on Slack, reviewing a PR, or looking at a dashboard, you're working from the same picture.
Coding agents
Where managed workflows run. A Topogy plugin in Claude Code and Codex recognizes what the agent is about to do, like changing a migration or committing to a protected branch, and loads your team's guidance before it acts.
- Trigger conditions for the moments that matter
- Guidance scoped to the repository and the task
- Gates that stop a required step from being skipped
- A visible marker each time guidance loads
MCP Server
Ask Claude about your team's AI usage. Admins connect Claude Code, Claude Desktop, or claude.ai to Topogy and get answers on usage, cost, teams, tools, and models, each with its definition.
- Usage and cost measures, with definitions
- Compare teams and drill into sub-teams
- AI tools, models, and session purposes
- Works in Claude Code, Claude Desktop, and claude.ai
Web App
The command center for engineering leadership. Explore how your system fits together, track AI usage and cost, configure workflows, and monitor adoption, all in one place. Where VP Engs and architects go to understand what's happening across the org.
- Knowledge and codebase rules views
- Engineering and AI metrics dashboards
- Risk map views
- Workflow configuration and run history
- Cost attribution and ROI reporting
GitHub App
Topogy in the pull request. Automated checks for convention adherence and blast radius, surfaced as PR comments and status checks. Engineers and reviewers get context without leaving GitHub.
- Convention compliance checks on every PR
- Blast radius annotations
- AI-generated vs. human-written code labeling
- Links to the tickets and agent sessions behind each change
Slack
Alerts, insights, and workflow triggers where your team already communicates. Topogy posts risk alerts, workflow summaries, and metric highlights to the channels that matter. Engineers can ask about their system directly from Slack.
- Risk alerts to team channels
- Workflow result summaries
- Natural language questions about your system and AI usage
- Workflow triggers and approvals
Ticketing
Topogy enriches your issues and project tracking with system context. Link tickets to affected services, surface architecture dependencies during planning, and close the loop between what was planned and what agents actually built. Works with Linear, Jira, and other planning tools.
- Auto-link tickets to affected services and components
- Architecture context surfaced during sprint planning
- Ticket-to-PR-to-agent-session traceability
- Convention references attached to issues
One system, many surfaces.
Every surface reads from and writes to the same understanding of your system. When an agent loads guidance in Claude Code, that session feeds back in. When a PR check runs, the results do too. When Slack posts a risk alert, it's drawn from the same data the web app shows. No sync issues. No stale views.