Status

System Status

Manually updated · Last checked 2026-07-19

All Systems Operational

Components

mergen.app (website & docs)

Marketing site, documentation, and blog.

Operational

Account & billing (Clerk + LemonSqueezy)

Sign-in, account dashboard, subscription management.

Operational

Cloud API (MERGEN_CLOUD_MODE)

Opt-in multi-tenant SaaS data plane for teams — telemetry ingest, OTLP, CI gate, credentials.

Operational

HITL delivery (Slack / email / PagerDuty)

Outbound notification channels for human-in-the-loop approvals and incident alerts.

Operational

npm registry (mergen-server)

Package installs and updates. Hosted by npm, not Mergen — see npmjs.com if this looks wrong.

Operational

What this page does — and doesn't — cover

Mergen's core enforcement — the local policy gate that blocks, holds, or passes tool calls — runs entirely on your own machine against a local server on 127.0.0.1. It does not call out to Mergen's infrastructure to make a decision, so nothing on this page affects whether your local gate is up. This page tracks only the pieces Mergen hosts centrally: the website and docs, account and billing, the opt-in cloud API for teams, and outbound HITL delivery.

You don't have to take that on faith — every install runs a live self-check of exactly this claim. Run mergen-server status, open My Machine, or check the IDE sidebar, and you'll see a Reliability panel confirming — in real time, on your machine — that Slack and Sync Plane outages never affect local enforcement. See the fail-open design doc for the full breakdown.

Report an issue

This page is updated by hand, not by an automated monitor — if something above looks wrong, or you're seeing an outage that isn't reflected here, email omer@mergen.app or open an issue on GitHub.