Pick your lane.

One ticket, tested once. We write the scenarios for the ticket and run all of them; that is one run. A retry after a fix is a new run. A retry caused by our infrastructure is on us and is never counted.

Nothing stops. Each run after the thousandth is $0.40 and lands on your next invoice. The queue keeps moving and the tickets keep coming back tested.

One Smoketest project, connected to one board in Jira or Linear, with its own environments, saved sign-ins, and notification channels. Pro includes five. Most teams use one per product or per repository.

Yes. Fourteen days of Pro, every feature included, no card. Connect your board, move a real ticket to QA, and see what comes back. If it is not for you, nothing to cancel.

Any time, from billing. Yearly is $4,000, two months free, with the same 1,000 runs a month. Moving from monthly to yearly credits what you have already paid for the current month.

Yes. Cancel from billing and Pro runs until the end of the period you paid for. Your projects, runs, and recordings stay readable for the 30-day retention window.

Yes. Jira and Linear, GitHub, CI, the API, CLI and MCP server, recordings, saved sign-ins, digests, the sprint overview: all of it is on Pro. Enterprise lifts the limits and adds what larger teams need to sign off: SAML SSO, SCIM, audit logs, BYOK, zero data retention, an uptime SLA, and onboarding with the founder.

On Enterprise, runs can use your own model keys so ticket content and screenshots go through accounts you control, and we can turn off retention so recordings, transcripts, and frozen ticket context are dropped as soon as the result is on the ticket. Both are set up with you during onboarding.

Enterprise is invoiced, comes with our DPA, and we answer security questionnaires as part of onboarding. Pro is paid by card, with invoices available from billing, and the same DPA applies.

No. It makes them faster. Every ticket that reaches QA gets its first pass automatically: scenarios written from the acceptance criteria, run on desktop and mobile, result and recording on the ticket. Your QA engineers stop re-clicking the same flows and writing up the same results, and spend that time on exploratory testing, edge cases, and sign-off. Teams use that room to ship more, not just to spend less.

Nothing. Pick the status that means ready for QA and we watch it. Your columns, assignees, priorities, and workflow stay exactly as they are. We post one comment per ticket and move it to Done or back to In Progress based on the result. If a person moves a ticket while we are testing, we stop and never move it back.

We write scenarios from whatever is there: the description, the comments, the attachments, and, with GitHub connected, the pull request behind the ticket. Most tickets have enough. When one does not, it waits in QA with a note saying exactly what was missing, so the author can add a line and we run it again. Over time that nudges the whole team toward tickets that can actually be tested.

You save a login session once per environment and we reuse it. Preview URLs per branch, basic auth, and staging behind a VPN on Enterprise all work. For flows that need an email to finish, each run gets its own inbox, so OTP codes and magic links are handled without anyone touching a phone.

The ticket goes back to In Progress with the failing step, what we expected, what we saw, and the recording, assigned to the author of the change. The developer fixes it while the branch is still fresh, moves the ticket back to QA, and we test it again. No repro to write, no back-and-forth in the comments.

On the ticket first, always. On top of that, connect Slack or Discord and get a message when a ticket fails and when it recovers, per project and per channel. Email gets the same alerts plus a digest, so a lead can see the sprint's testing at a glance without opening anything.

An overview of the sprint: how many tickets were tested, the first-pass rate, how many came back to development, and how late in the sprint QA actually starts. It is the same data the team works from, rolled up, so the question is never whether something was tested but what the numbers say about how the team is shipping.

They happen, rarely. Mark the result wrong on the ticket and it moves on; we use every one of those to get better. A human status change always wins, so nothing is ever stuck behind us.

The ticket, its comments, attachments, and linked pull request, only for tickets in the QA status you choose. Recordings, transcripts, and screenshots stay in your Smoketest project, behind your own access control. They never go into Jira or Linear; the comment carries the result and a link.

Not yet. Today every test starts from a ticket, so what we check is what your team asked for. Exploratory testing is on the roadmap: the agent walks your application and your code, works out the scenarios that deserve a test, and proposes them for your team to accept. If that is the part you are waiting for, say so on the call and we will keep you posted.

Pro: connect Jira or Linear, point us at your QA status, and test your first ticket today. Enterprise: book a call, bring one real ticket, and we set everything up with you around how you release, including private hosting and SSO where you need them.