How it works
How a run works
The four steps, the checks each records, and what a run costs your app.
Updated
A run walks four steps in order on one app, a host you own and have verified. Each step records timestamped checks, a screenshot, and, if it fails, the request and response and the console error that decided it.
1. Signup
Opens your signup page, dismisses cookie banners, fills the email (and a password when the form asks for one; passwordless and magic-link flows are handled), submits, and accepts a “check your email” confirmation as success. Client-rendered forms are waited for.
2. Email
Waits for the welcome or verification mail at the run's own address, run-<id>@inbox.mystra.run, then follows the first verify, confirm or login link that points at your host. The wait is the window you set; two minutes is a good default.
3. Pay
Starts from the upgrade page you configured, or looks for an Upgrade, Pricing or Billing link and the usual paths such as /pricing. Presses the plan button, follows plan dialogs, and reaches Stripe Checkout. It never pays: see Payment proof.
4. Access
Proves the paid area: a CSS selector on a page, or a boolean field in a JSON endpoint called with the run's session. In the default payment mode the check is inverted: the paid area must still be closed to the fresh, unpaid account.
What a run costs your app
One signup, one welcome email, one Checkout session that is never completed, and about a minute of traffic from a single browser. Signup, email and access are retried once if they fail; pay never is.