Solutions: Agencies and studios
For agencies and studios: test suites clients can own
A test suite in code is hard to hand over to a client without test engineers. Plain-English specs in YAML files live in the client's repository and can be read without the agency.
Trigger: Handover of test suites. What helps: Specs the client can read and own.
How the platform fits
Specs live in the repository
Tests are YAML files in tests/, versioned and reviewed with the code.
An exit path in code
Specs can be exported to Playwright tests in TypeScript.
Per-client projects
Each plan has a set number of projects: 1 on Free, 3 on Team, 10 on Scale.
Capabilities
Tests in plain English
A test is a list of steps in plain English in a YAML file; the platform resolves each step against the live page at run time.
Read moreHeals locator and layout changes
When a step no longer resolves because an element moved, was renamed or restyled, the platform re-resolves it, marks the test as healed and records the change for review.
Read moreRuns in CI
One CLI command runs a suite in CI and reports a pass, fail or healed status per test as a check on the pull request.
Read moreQuestions
Can the client keep the tests if they stop using the platform?
Yes. The specs are files in their repository and can be exported to Playwright tests in TypeScript.
How many client projects fit in a plan?
1 project on Free, 3 on Team, 10 on Scale, by contract on Enterprise.
Request early access
Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged. We reply within 24 hours on business days.