Testing that
proves itself.
Describe a GUI test. Get a recorded run and an independent verdict you can inspect.
It starts with a sentence
Write the steps and what should happen. Ryvetz finds each control on the live screen.
Explore FlowsInvite a teammate and confirm the seat
-
Open Settings › Members
-
Invite dana@example.com as an editor
-
Send the invite
Judge criterionThe members list shows dana@example.com as Pending within 10 seconds
-
Revoke the invite
Judge criteriondana@example.com is no longer listed within 10 seconds
View YAML
name: Invite a teammate and confirm the seat
app: acme-crm
account: staging
steps:
- do: Open Settings › Members
- do: Invite dana@example.com as an editor
- do: Send the invite
verify: The members list shows dana@example.com as Pending within 10 seconds
- do: Revoke the invite
verify: dana@example.com is no longer listed within 10 secondsA verdict that cites pixels
A separate judge sees only your criterion and the screenshot, then cites what supports its verdict.
Explore the Judge
1The status the criterion asks about: Pending.
2Also on this screen: an avatar that failed to load.
Judge criterionThe members list shows dana@example.com as Pending within 10 seconds
“dana@example.com is listed in Settings › Members with the status Pending.citation1”
What each side was given
A pass the judge is not confident in is recorded as a fail. Cheaper checks, such as an exact text match or a known-good replay, can settle a step before the judge is asked.
Executor received
- The live screen
- Step 03: Send the invite
Judge received
- The criterion
- One screenshot
Never shown to the judge
The executor's reasoningIts logsIts own claim of success
Evidence you can inspect
Replay the video, inspect the trace, and read the verdict. Team adds pull-request checks.
Explore Evidence
Run overview: an illustrative capture of the example product, Acme CRM.
Open full-size imageGuardrails for real accounts
Shared runners accept test, sandbox, and demo accounts only, with session guards enforced by the runner. Accounts with real money behind them, such as funded or live trading accounts, require dedicated Enterprise runners.
Explore runner safeguards- Nothing to install
- You author flows in the browser or from the CLI. The runner, the browser, and the platform profile are ours to keep working.
- Test accounts only
- Credentials are encrypted at rest, injected only for the length of a run, and never shown back in the UI.
- Dedicated when it matters
- Accounts with real money behind them, such as eval, funded, and live trading accounts, belong on a single-tenant runner under Enterprise. Never on a shared slot.
Ship with evidence.
Invite-only for now. We onboard teams in order, a few at a time.