Autonomous QA for web apps
Know if your release is ready to ship.
Pervaro tests every release of your web app in a real browser, verifies what fails, and gives you a readiness verdict backed by screenshots, video and logs. No QA team required.
New organizations start with 100 free credits. Already have an account? Sign in
Release 4.7.0
Readiness
- Sign-up and email verification
- Checkout · card decline handling
- Billing · proration on downgrade
- Invite acceptance
Verified issue · Billing
Downgrading mid-cycle shows the wrong amount. Screenshot, video and network log attached.
The gap
Building got fast. Checking didn’t.
AI coding tools can produce an app in a day. Someone independent still has to prove it behaves as intended before users see it.
“It works on my machine” is the whole test plan.
Pervaro tests the deployed site the way a person would, in a real browser, against what you meant to build.
A failing test might be a real bug, or just a flaky one.
Failures are verified before they become issues, each one carrying screenshots, video and logs.
You still have to decide whether to ship.
Every release ends in an explicit verdict: Ready, Ready with warnings, Not ready, or Not assessable yet.
What you get
An independent QA owner for every release
From understanding your product to closing the issues it finds.
Learns what your product should do
Upload requirements (PDF, DOCX, Markdown or text, up to 5 MB) and Pervaro turns them into a requirements list and proposed tests.
Tests follow your intent, not just whatever the UI happens to show.
Maps the real site first
Before writing tests, the agent explores your site and records the pages and controls it actually finds.
Requirements the site doesn't show are reported, not silently turned into broken tests.
Runs in a real browser
Tests compile into a structured plan that Playwright executes the same way every time. Runs don't call an LLM.
Repeatable results you can compare release to release.
Scopes each release smartly
Compare against an earlier release and Pervaro picks what to test: what changed, what must always run, and what didn't pass last time.
Less waiting than re-running everything, without skipping what matters.
Evidence on every result
Screenshots, video, traces, and console and network logs are captured, and you can watch a campaign live.
Developers can reproduce a failure without asking you for details.
Issues tracked to closure
Verified findings become issues with comments and a workflow. When a fix lands, the platform retests it.
Nothing is marked fixed until it has been checked again.
How it works
See Pervaro work, in either mode
Chat with an agent for quick exploratory testing, or run structured release suites. Step through each one below.
You can switch modes any time inside the app.
Step 1 of 8
Start in Agent mode
New session is where you begin, and it needs an environment. Open Environments in the left menu to create one.
Create an environment first
An environment is the website the agent tests, with its test users and reference documents.
Create environmentStep 1 of 8: Start in Agent mode
Safety and control
Built to be pointed at your staging site
A tool that clicks through your product needs firm limits. These are enforced by the platform.
Guarded browsing
Targets pointing at localhost or internal network addresses are blocked before the browser opens them.
Write-only credentials
Test account passwords are encrypted at rest and never returned or displayed again.
You set the boundaries
Per-environment switches decide whether the agent may delete, pay, or send content. Delete and pay are off by default.
Roles for your team
Invite colleagues as Owner, Admin, Developer or Viewer. Viewers get read-only access to products, runs and reports.
FAQ
Questions, answered
- Pervaro is an autonomous QA platform for web applications. You describe what your product should do, point it at a test environment, and it tests your releases in a real browser, verifies failures, and reports whether the build is ready to ship.
- Teams that ship web software without a dedicated QA function, such as founder-led startups and teams building with AI coding tools. It's designed to take ownership of checking a release so developers don't have to.
- Pervaro reads your requirements, explores your site, and compiles tests into a structured plan. Playwright then runs that plan in a real browser. Results, evidence and issues are collected, and a rule-based readiness assessment is produced for the release.
- Create a workspace, add a product with its testing URL and test accounts, upload requirements, and submit a release. Or use Agent mode to chat with the agent about what to test on an environment, no setup beyond the site and optional test users.
- Suite mode is organised around products, releases and repeatable test suites, and ends in a release readiness report. Agent mode is chat-driven: you describe an objective, the agent plans tasks, runs them in a browser, and reports findings. You can switch between them in the app.
- Each release is assessed as Ready, Ready with warnings, Not ready, or Not assessable yet when evidence is incomplete. The assessment is rule-based over verified results, and it comes with the reasons behind it.
- Test targets are checked so the browser can't be pointed at localhost or internal network addresses. Actions that delete data, spend money, or send and publish content are controlled by per-environment settings, and delete and pay actions are off by default. Even so, use a test environment and test accounts.
- Passwords you add for test personas are stored encrypted and are never returned by the API or shown again. Pervaro signs in on the agent's behalf, so the agent itself never sees them.
- New organizations start with 100 free credits, valid for 30 days. Credits pay for metered work such as test runs, compiles and test generation. Paid plan pricing isn't published on this page yet.
- Pervaro tests web applications through a browser. It can only test what it can reach, so staging access and working test accounts matter. Forms that require human verification, such as CAPTCHAs, aren't submitted, and password changes and account deletion are never automated. Teams can invite members with roles from Owner to read-only Viewer.
Ship every release with the evidence to back it.
Create a workspace, add your product, and submit your first release for QA.