Docs
Mystra documentation
Mystra is a revenue-path monitor. After every deploy, a real Chrome browser signs up on your app, waits for the welcome email, reaches Stripe Checkout without paying, and checks the paid area. It alerts only with proof.
In two minutes
Add your app, prove the domain with one TXT record, describe the path, press Run now. Then paste the deploy hook into your pipeline so every deploy is checked:
curl -X POST https://mystra.run/api/hooks/deploy/<appId> \
-H "X-Mystra-Signature: $MYSTRA_HOOK_SECRET" \
-H "Content-Type: application/json" \
-d '{"commit":"'"$(git rev-parse --short HEAD)"'","env":"production"}'Prefer to hand this to an assistant? Every app's settings offer “Copy instructions for your AI”, and /llms.txt is the whole product in plain text.
Get started
How it works
- How a run worksThe four steps, the checks each records, and what a run costs your app.
- Outcomes and alertsPassed, broken, uncertain, flaky, and when Mystra pages you.
- Payment proofHow Mystra proves the pay step without charging a card: reach Stripe Checkout, read the plan and amount, stop, and confirm the paid area stays gated.
- Evidence and retentionScreenshots, video, HAR and console log, and how long they stay.
Configure
- Path settingsEvery field under Settings → Path and what the runner does with it.
- Deploy hookStart a run after every deploy: GitHub Action, Vercel webhook or curl.
- Cleanup webhookLet your app delete the throwaway account after each run.
- Marking the pathThree attributes that make the runner certain and fast.
- Brief for your AIHand the wiring to Claude Code, Cursor or ChatGPT.