Product
From a sentence to a verified release
How it works
- 1
Add your app
Create a project with your app's address (staging or production) and, optionally, its Git repository and default branch.
- 2
Describe a journey
Write what a user does and what should happen, in plain English: "Sign in, add a jacket to the cart, check out with a promo code."
- 3
Review the generated test
Qavtrix writes a real Playwright test with named steps. You can read and edit it; every change is saved as a new version.
- 4
Run it anywhere
Run on demand, on a schedule in your time zone, or from GitHub Actions on every push. Each run gets a fresh browser in an isolated runner.
- 5
Act on the result
Every run has a permanent ID, a step timeline, screenshots, logs and a replayable trace. Failures come with an explanation and a next action.
Everything in the platform
Plain-English test authoring
Browser journeys and HTTP API checks, written by AI as readable Playwright code you own.
Isolated cloud runners
Tests run in a separate runner with no access to your account data, under strict time limits.
Long journeys, in parts
Tests with many steps run in parts and carry the session, page and variables from one part to the next.
Evidence on every run
Step timeline, failure screenshot, stdout and stderr, and a Playwright trace you can replay.
AI failure analysis
Expected versus actual, a likely cause (app bug, changed selector, timeout, test data, environment) and what to do next.
UI change detection
When a button is renamed or replaced, Qavtrix names the element that took its place and updates the test with one click.
Sign in once
For apps behind CAPTCHA, 2FA or SSO: sign in yourself in Chrome once, and every run starts signed in. Sessions are stored encrypted.
Automation
Schedule a project or a single test every 15 minutes, hourly, daily or weekly, in your own time zone.
CI and repositories
A ready GitHub Actions job runs your tests on every push and fails the build when one fails. Runs link to the branch and commit.
Transparent usage
One credit per test step, known before a run. Sandbox mode runs on free credits; Live mode adds bought credits.
Security and governance
Credential-free runners
Test scripts run in a separate runner that holds no secrets. Results return through short-lived, presigned upload links.
Signed execution
Every request to a runner is signed with an Ed25519 key and verified before anything executes.
Script screening
Scripts are checked before they run: no access to the runner's file system, processes or environment.
Scoped API keys
One key per project for CI, stored hashed, shown once and rotatable at any time.
Administration
Admin roles, account suspension and a cross-account view of failing runs with suggested fixes.
Usage you can audit
Credits are charged per test step, with every charge, grant and refund kept in a ledger.
Put your critical journeys under test this week.
Create a project, describe one workflow, and see it run with full evidence in minutes.