Enterprise

Runtime context that stays in your environment.

Airgapped and on-prem by design. There is no AppMap cloud for traces.

Bring your model. Keep your evidence.

AppMap sequence diagram showing the full request path from HTTP to database, generated inside the developer environment.
Runtime evidence, generated and reviewed inside your environment.
Independent runtime evidence

Architecture governance cannot rely on the AI grading its own homework. AppMap adds an independent evidence layer inside your environment: runtime behavior captured from the application itself, outside the AI's reasoning loop. The agent can consume it, the reviewer can see the same evidence, and the organization can govern against it. The AI explains the evidence. It does not create the evidence.

Architecture and trust

Your environment

Developer environment

AppMap records and compares traces

tmp/appmap · working traces

CI

The same review runs in the pipeline

No outbound dependency on AppMap services

Repository

gold_traces/ · sanitized before commit

Self-hosted AI endpoint
Hosted coding agent (optional) · provider's terms apply

AppMap runs inside your environment with no outbound dependency on AppMap services. Offline activation and internal distribution are supported. There is no AppMap cloud for traces.

Trust, but verify: open-source clients and a published data spec. Developers and security reviewers can audit what AppMap records and what it sends to the agent.

How AppMap deploys

AppMap records and compares traces in your environment. AppMap telemetry is configurable to route to your internal observability stack, such as Splunk, so that data stays inside too. If the team chooses a hosted coding agent, some context goes to that provider. The provider's configuration and terms apply.Your environment. No AppMap cloud data plane.ZONE 1 · DEVELOPER WORKSTATIONIDELanguage agentLocal tracesQuery DBMCP serverCoding agentZONE 2 · CIAppMap Gold TracesAppMap review workflow (GitHub Action or CI job)PR commentHOW IT DEPLOYS
Extensions
packaged for internal distribution or installed from the VS Code and JetBrains enterprise marketplaces
Agents and CLI
pulled from your language package registries (RubyGems, PyPI, npm, Maven Central)
Deployment telemetry
configurable to route to your internal observability stack (Splunk or similar)
AppMap records and compares traces in your environment. AppMap telemetry is configurable to route to your internal observability stack, such as Splunk, so that data stays inside too. If the team chooses a hosted coding agent, some context goes to that provider. The provider's configuration and terms apply.

What the reviewer sees

The same runtime evidence the agent queried, generated locally and attached to the change.

The call tree the agent queried
The call tree the agent queried
Every SQL query from the real run
Every SQL query from the real run
The full request path, HTTP to database
The full request path, HTTP to database

From one workstation to CI

  1. Step 1

    Start on the workstation

    Teams do not need to instrument CI to begin. AppMap records from a running process, so teams start in the editor or in environments that already run: a local run, a focused test, a smoke script, an API call, or a QA environment. No full enterprise-stack build required to record the first traces.

  2. Step 2

    Centralized ground truth of application behavior, in git

    The AppMap Gold Traces skill identifies important application paths and uses existing tests to build the set. When coverage is missing, AppMap suggests a new test case. The organization can run the same review in CI when ready. The set lives in the team's repository, where changes follow the same pull-request workflow as the code. Teams begin lightweight in the editor and graduate the flows that matter into the pipeline.

    AppMap demo traces of the public open-source FINOS Waltz project, comparing the same endpoint before and after an unrelated change.
    Public open-source demo: FINOS Waltz