Ryvetz
Join waitlist
How it works

From a sentence to a verdict you can forward.

Ryvetz turns a written flow into an executed test on a machine we operate, and hands back video, a trace of every action, and a judged verdict for every step you gave a criterion.

Join waitlist See pricing
  1. 01 Describe

    One flow, in plain English, with a criterion on the steps that matter.

  2. 02 Run

    A hosted runner opens your terminal on a practice account and drives it.

  3. 03 Judge

    A separate model grades each criterion from the screenshot alone.

  4. 04 Read

    Video, trace, and a cited verdict, in the dashboard or as a CI check.

Flows

It starts with a sentence

Write the test the way you would say it to a colleague. Every step is grounded on the live screen at run time, so nothing depends on selectors or coordinates.

flows/bracket-order.yaml
name: Place a bracket order and flatten
app: topstepx
account: practice

steps:
  - do: Open the order ticket for MNQ
  - do: Set quantity 2, bracket with a 10-tick stop
  - do: Submit and wait for the fill
    verify: The positions table shows 2 MNQ within 15 seconds
  - do: Flatten the position
    verify: No open position within 15 seconds
The Ryvetz Atlas map for TopstepX: 35 screens discovered across 9 paths, drawn as a tree of thumbnails from the start screen.
Every run feeds the Atlas: a map of the screens and controls Ryvetz has already seen, so the next flow grounds faster.

Plain-English steps

A step is what to do and, when it matters, what must be true afterwards. No page objects, no locators.

See it on a plan

Grounded on pixels

The executor looks at the real screen and finds the control the way a human would, so a moved button is not a broken test.

See it on a plan

Recovers from drift

When the interface changes, the agent sees the new screen and continues instead of failing on a missing selector.

See it on a plan
Judge

A verdict that cites pixels

The agent that clicks never grades itself. A separate strict judge sees only your criterion and the screenshot, and quotes what it used before anything passes.

Executor sees
  • The live screen
  • The step to perform
  • The Atlas of known controls
Clicks, types, waits. Never grades.
Judge sees
  • Your verification criterion
  • The screenshot. Nothing else.
Issue found

“A failed image load in Support › Mini Tutorials: the URL reads ‘…topstep.comundefined/’, missing the path separator.”

A pass it is not confident in is recorded as a fail.

Split roles

Executor and judge are different models with different instructions. One acts, one decides.

See it on a plan

Criterion and screen only

The judge never sees the executor’s reasoning, so it cannot be talked into a pass.

See it on a plan

Strict by default

A pass the judge is not confident in is recorded as a fail, with the evidence attached.

See it on a plan

“Yes, one broken element was found: a failed image load in Support > Topstep's Mini Tutorials with malformed URL 'https://strapi-cms.topstep.comundefined/' missing a path separator between domain and path component.”

1 issue found Recon health check · TopstepX, 25 Aug 2026 Answered from the screen, with 2 citations
Runners

Hosted machines we operate

Your laptop is not the test machine. Every supported platform ships as a curated image on a runner we run, with a session guard that refuses the wrong screens.

web-runner-01 Ready
Image
chrome-stable · topstepx-profile
Slot
1 run at a time, yours next
Accounts
Practice and demo only
Session guard
Refuses log-out and real-money screens
dedicated-runner Enterprise
Tenancy
Single-tenant, never shared
Image
Your golden image
Accounts
Eval, funded, live

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.

See it on a plan

Practice accounts only

Credentials are encrypted at rest, injected only for the length of a run, and never shown back in the UI.

See it on a plan

Dedicated when it matters

Eval, funded, and live accounts belong on a single-tenant runner under Enterprise. Never on a shared slot.

See it on a plan
Evidence

Evidence your pipeline can gate on

Video, screenshots, and a typed trace for every run, plus JSON and exit codes. On Team, every pull request gets a check run.

A TopstepX recon in the Ryvetz dashboard: the recorded terminal video with step, action, pass and fail markers on its timeline, and the recon panel reporting 1 issue found, a broken image with a malformed URL, boxed on the frame.
A real finding: the recon answers the health check from the screen, cites the frame, and boxes the broken element on it. Video, timeline, and transcript stay attached.

Video and trace

Every action is recorded and typed. Scrub to the step, read what the agent did, see what the judge cited.

See it on a plan

CI check runs

Install the GitHub App or call the webhook from your pipeline. Fail the release when the judge does.

See it on a plan

Share links

Time-limited capability URLs for a run, so a release manager can read the verdict without an account.

See it on a plan

Ship the terminal with evidence.

Every workspace starts at $0 with $30 of free credits. Describe one flow, watch it run on a hosted machine, and read the verdict.

Join waitlist Get a demo