Who the pilot is for
The pilot is for teams that build and ship their own software product and need to know a release is ready before it goes out. That includes:
- Product and engineering teams shipping a web product on a regular release cycle.
- QA and engineering leads who own the release decision.
- Founders of product startups who ship without a dedicated QA person.
How the code was written does not matter. Hand-written, AI-assisted or both get the same checks. Your release is checked against what your team says it should do, not against what the code happens to do.
What a pilot team does
A pilot team connects a real build, adds context and reads a report. In four steps:
- Connect a staging or preview URL for your product. It must be a product your team owns or has written permission to test, and the checks stay inside the hosts you allow.
- Add context: your requirements, design rules and business rules, so the release is checked against what it is supposed to do.
- Get a report. Every result is in one of four states, shown below.
- Approve only what was covered. Your sign-off covers what was checked and nothing else.
The four states in the report:
- Verified: checked, and reproduced by an independent run.
- Issue found: a real failure, with the steps to reproduce it.
- Needs input: the requirements were unclear or contradictory, so it asks instead of guessing.
- Not covered: outside what was checked, and shown plainly.
Coverage, stated plainly. Checks run in Chromium only: real Chromium browser sessions, including phone and tablet sizes with touch emulation. Firefox and Safari rendering and real devices are not covered, and the report lists them under Not covered.
Want your team's next release checked in the pilot? Start with a free 45-day trial, no card.
Work email only. We'll only email you about the ShipperAG pilot. Unsubscribe anytime. How we handle data.
What we ask of pilot teams
We ask for three things:
- A real release to test. The pilot works on your own product, not a demo.
- Plain feedback. Tell us what was useful, what was wrong and what confused you.
- A named person who signs off releases. One person reads the report and decides what to approve.
In return, pilot teams get a free 45-day trial on a real product, a direct line to the founders and a say in what we build next.
How teams are chosen
We invite pilot teams from the waitlist first. Joining the waitlist does not guarantee a place, and we read every entry.
The form asks for your work email and, if you want to give it, your team size. We keep your email, team size, plan choice and the page you joined from, only to contact you about the ShipperAG pilot. See how we handle data on the About page.
What it costs
The pilot starts with a free trial: 45 days from your first release check, up to 20 checks on your own product, and no card. When it ends, nothing is charged automatically. You choose a plan or stop, and you keep every report either way.
Plans start at $149 a month for 20 release checks, with unlimited seats. See pricing for every plan and what each includes.
While you wait
You can use these today, without waiting for an invite:
- The website readiness check: paste a URL and see what a machine verified, what failed, what needs a person to judge and what nothing checked.
- The release readiness checklist: an interactive scorecard that shows whether your next release is ready to ship.
- The website QA checklist: 100 checks across journeys, forms, accessibility, Core Web Vitals, SEO and security, free to download.
- The UAT sign-off template: free to copy, so your release decision is written down the same way every time.
- The sample report: a real ShipperAG run on Northwind Books, our own test shop, so you can see how results and a sign-off look before you join.