How Molar fits together
Molar is autonomous QA for web apps. One account gives you four tools that cover the full loop: discover flows, test safely, gate releases, and debug failures.
Note:
Documentation index for agents: docs.molar.it/llms.txt
The four products
| Product | What you get | Who it's for |
|---|---|---|
| Cartographer | Map your app from a seed URL and export production-grade Playwright tests | QA engineers, platform teams |
| Guard | PR gating, production monitoring, shadow-prod diff, and Mender auto-fix PRs | DevOps, release engineers |
| Clones | Local stand-ins for Stripe, Twilio, email, auth, and S3 — no real charges or inboxes | Fintech, any team with vendor dependencies |
| Trace | Step-by-step replay of failed runs — video, network, DOM, clone state | Anyone debugging a failure |
app.molar.it is where you sign in, connect apps, approve scenarios, and review runs. Product-specific views roll out inside the same dashboard as each surface matures.
What your account includes
- Scenarios — write tests in
.molar.md; Molar compiles them to Playwright - CLI —
molar(ornpx molar-agent) for init, run, scenarios, clones, traces, and MCP - Dashboard — runs, scenarios, billing, team invites, and GitHub App setup
- MCP — connect from Cursor or Claude Code with one install; same tools locally via
molar mcp serve - Sign-in — one login for the dashboard, API, CLI, and MCP (email, GitHub, Google; SSO on Business)
- Billing — usage meters and plan limits in the dashboard
How teams typically work
- Cartographer crawls your app and proposes scenarios from real user flows (or you author
.molar.mdin the CLI). - Guard runs those scenarios on every PR and on a production schedule.
- Clones replace Stripe, Twilio, and other vendors so tests never touch real customers.
- When a run fails, Trace opens a timeline you can replay step by step.
- Mender (part of Guard) can draft a fix PR when a regression is confirmed.
Humans vs agents
| Humans | Agents | |
|---|---|---|
| Start | app.molar.it signup | Agent self-serve signup or molar agent signup |
| Connect | Dashboard, GitHub App, optional CLI | MCP install or molar mcp serve |
| Operate | Approve flows, billing, team settings | Run scenarios and read traces via MCP tools |
Both paths share the same org, scenarios, and run history.
Deployment options
| Option | Who it's for | What you get |
|---|---|---|
| Molar cloud | Most teams | app.molar.it + api.molar.it — no infrastructure to run |
| Single product | Teams starting with one surface | That product's dashboard and docs; expand when ready |
| Self-hosted | Enterprise / air-gapped | Run Molar in your environment; local MCP and clones — operator docs |
Where to go next
- For humans · For agents
- Install & initialize
- Your first scenario
- Cross-product workflows
- MCP server setup
- Dashboard
Product deep dives: Cartographer · Guard · Clones · Trace.