Certyn plans and runs QA across your tools and environments. It investigates failures, verifies fixes, and explains what still puts your release at risk.
Pick your seat. Each one is a different assignment, shown as what appears in your tools, in order.
Prorate plan changes mid-cycle. Ready for review.
This touches four flows: upgrade, downgrade, invoice preview, renewal charge. Three have tests. Downgrade with an annual coupon has none, and a customer reported a problem there in ticket #5531. Running it on staging.
Failed. The invoice preview shows $0.00 credit. It should be $37.50. The billing API drops the credit when a coupon is set. The page is right, the API is wrong.
Opened ACM-318 with the steps, the video and the failing request. Assigned to Dan.
fix: keep the credit when a coupon is applied. Merged.
Ran the scenario again after the merge. Passed. ACM-318 closed.
Two roles manage: they decide what to check and what the results mean. Two roles execute: they run, reproduce, and investigate. What comes back changes the plan.
Decides what must be checked
Sets the coverage: which flows, issues, and risks actually matter for this release.
Runs across your stack
Uses your existing tests, tools, devices, and environments to check what matters.
Reproduces and explains issues
Reproduces reported bugs, finds the cause, and confirms the fix actually holds.
Applies your rules, reports risk
Weighs the findings against your ship criteria and calls out what stands in the way.
↑ results change the plan
The dashboard when you want the full picture. Slack when you want a quick answer. GitHub when you want the check on a pull request.
Certyn does not replace Playwright, TestRail, or Jira. It reads them, and sends the findings back.
Requirements explain expected behavior.
Changes identify what needs attention.
Existing tests provide coverage and evidence.
Customer reports reveal problems worth reproducing.
Environments say where to run.
Ticketing and chat receive findings and updates.
Two different things, both covered: your web app at desktop and mobile viewports in a real browser, and your native iOS and Android apps on real devices through Appium, on your device cloud or your own devices.
Web
1440×900Desktop and mobile viewports.
Order summary
Viewports are the browser resized. Native apps are the real app on a real device. Same flow, same evidence either way.
Start three ways: point Certyn at your app and let it explore, connect your test management tool so it runs the suites your team already maintains and writes results back, or push Playwright and JUnit results from any CI. No migration, no lock-in.
TestRail
Regression suite · 196 cases
Zephyr
Smoke suite · 24 cases
Xray
API contracts · 58 cases
Azure Test Plans
Release checks · 41 cases
After every run, pass/fail and evidence links are written back to the source.
Trigger a run on every deploy
- uses: certyn-one/action@v1 with: api_key: ${{ secrets.CERTYN_API_KEY }} project_slug: acme-store instruction: "Smoke test this deploy."
Or upload results from any CI
curl -X POST "$CERTYN_API/api/ci/results" \ -H "X-API-Key: $CERTYN_API_KEY" \ --data-binary @playwright-report.json
Playwright JSON or JUnit XML, auto-detected. Works from GitHub, GitLab, Jenkins, or anything that can curl.
No. Certyn can use them. Your existing tests, test-management systems, devices, customer reports, production signals, and engineering tools become capabilities available to the QA team. Certyn coordinates the work, investigates the results, fills the gaps, and determines what they mean for product quality.
No. You describe what should happen in plain English, like "a user can check out with a saved card", and Certyn runs it. Your team reviews findings; nobody babysits test scripts.
No. Certyn finds buttons and forms by looking at the page like a person, not by brittle CSS selectors, so most UI changes do not break anything. When real behavior changes, it flags it for review instead of failing silently.
Full user flows like checkout, sign-up, and password reset, plus mobile and responsive layouts, accessibility, security (with a pentest agent), and APIs. All in a real browser, on staging, preview, or production.
Evidence, not just a red mark. Every finding includes a screenshot, a full session video, a network log, and the exact steps to reproduce: enough to fix the bug without rerunning it yourself.
Certyn files a ticket for each bug in Jira, Linear, or GitHub, with severity, steps, and evidence, and closes it once the fix passes. Trigger runs from CI/CD with the GitHub Action or API, upload Playwright or JUnit results from any CI, connect Sentry so it reads your live errors, and ask for status anytime in Slack.
Give it a test account and it signs in like a person: it drives your real login form in the browser. Password logins work out of the box. For email codes, magic links, or SSO, the surest path today is a test account that skips the code (an allowlisted email, a static OTP, or a shared session), or a self-hosted runner inside your network. Onboarding asks how your app signs in and stores the credentials as encrypted environment variables.
By execution minutes: the actual compute time agents spend running, not the number of tests or test cases. You always know exactly what you are paying for.
Get real coverage on the free tier, no card. Then pick a bucket of QA hours when you need more, and cancel anytime.
What you give
What Certyn does first
What you get
Two minutes is the setup. The first findings arrive in minutes.
Start Free→1 concurrent test · 1 hour · one-time, no card
1 concurrent test · 6 hours/mo
3 concurrent tests · 40 hours/mo
Enter a URL. See real findings in minutes.
