Guard gates pull requests with affected-scenario selection, monitors production with safe synthetics, and — when something breaks — lets Mender draft the fix. All without touching a real customer.
Guard isn't a test runner — it's a release-safety system. It understands your code graph, picks the right scenarios, runs them safely against cloned vendors, and fixes what it breaks.
Affected-scenario selection picks only the tests touched by your diff. Ancestor-green cache skips what's proven safe. Full-suite fallback when the graph isn't confident.
median check: 2m 14sScheduled synthetics across 5+ regions, running real user flows against your live app — with cloned vendors so no real customer is ever touched.
40 checks / minTriages the failure, classifies it (product bug? vendor drift? flake?), and — for real bugs — drafts a fix PR with a regression test. A human always approves.
68% acceptance · 14m MTTRGuard's dependency graph knows which files map to which scenarios. When a PR touches discount.ts, it runs checkout.coupon and checkout.flow — not your entire suite.
Guard reads your repo's import graph, route map, and scenario definitions to build a dependency matrix. When a commit lands, it traces which scenarios are affected by the changed files.
If a scenario already passed on a parent commit and none of its dependencies changed, Guard skips it. Cache policy is per-scenario — content-hash for static tests, ancestor-green for flow tests.
When the graph confidence drops — a lockfile touches 50 transitive deps, or a new file has no edges yet — Guard falls back to the full suite automatically. No config. No missed regressions.
When Guard catches a regression, Mender reads the failing trace, the commit diff, and the git history — then drafts a fix PR with a regression test. A human always approves. Governance controls what files Mender may touch.
Guard runs your critical paths on a cadence against live production — with synthetic identities and cloned vendors, so checks never generate a real charge, a real email, or a real analytics event.
| Scenario | us-east | us-west | eu-west | eu-central | ap-south |
|---|---|---|---|---|---|
Checkout — card → receipt checkout.flow · p95 1.9s |
✓ | ✓ | ✓ | ✓ | ✓ |
Auth — login + 2FA auth.login · p95 0.7s |
✓ | ✓ | ✓ | ✓ | ✓ |
Billing — stripe webhook → DB billing.webhook · p95 1.1s |
✓ | ✓ | ✓ | ✗ | ✓ |
Email — receipt delivery email.transactional · p95 3.6s |
! | ✓ | ◐ | ✓ | ✓ |
Dashboard — first paint dashboard.load · p95 1.0s |
✓ | ✓ | ✓ | · | · |
Guard is surface 3 of Molar's vision: a complete quality fabric for the AI-native engineering team. Each surface works alone — and they compound together.
Map your codebase. Understand how modules connect, which paths carry risk, and where agent-written code lands.
Behavioral replicas of your third-party dependencies. Same API, same error modes, zero real effects. The foundation Guard runs on.
Gate every merge. Watch every deploy. Fix what breaks. The release-safety system for AI-native teams.
Follow a request from browser to database and back. Distributed tracing built on the Molar graph. Coming soon.
Guard targets teams comparing Checkly, Datadog Synthetics, and deployment gates — but adds affected-scenario selection, cloned-vendor safe synthetics, and Mender fix PRs.
Checkly and Datadog run synthetics against live vendors and real users. Guard runs flows with Clones so production checks never charge a card or email a customer — and adds affected-scenario PR gating plus Trace replay on failure.
Guard maps changed files to scenarios via a dependency graph. A PR touching discount.ts runs checkout scenarios — not your full 47-test suite. Median check time: 2m 14s. See GitHub Actions integration.
No. Production synthetics use cloned Stripe, Twilio, and email vendors. Zero real-user side effects — ever.
When Guard confirms a regression, Mender triages the failure, classifies it (product bug vs flake vs vendor drift), and drafts a fix PR with a regression test. A human always approves the merge.
Every plan includes PR gating, production monitoring, the full dashboard, and the same Mender. The only knobs are runs and seats. Free until you ship — then the math is on this page.
Every merge safe. Every deploy watched. Every fix drafted.
Guard is the release-safety system for AI-native teams.