Updated November 2026

Bug0 or Smoketest?

Choose Bug0 when you want an engineer and AI agents to run a Playwright suite for you. Choose Smoketest when you want each ticket tested as it reaches QA, with the proof on that ticket, from $399 a month.

Book a callTalk to our founder. If Bug0 is the better fit, we will say so.
QA budget
C3fxFrom $399 a month
A
B
C
1
Option
Starts
Cost
2
Bug0, managed
Critical flows in one to two weeks
$2,500 a month, flat
3
Start with Smoketest
Today
From $399 a month
Next yearHeadcount

Bug0 figure is its listed price for up to 500 user flows, read in November 2026.

Bug0 runs a test suite for you.Smoketest takes each ticket as it reaches QA.

Here is one ticket,handled both ways.

Bug0 puts an engineer on your account and has a person review each failure, and that counts for a lot. The difference is where the work starts and where the result ends up.

Acme Billing / ACM-436

Show proration on the invoice PDF

When an Admin adds a seat mid-cycle, the invoice PDF should carry the proration line and match the invoice preview.

With Bug0Runs when a pull request triggers the suite
B0
Bug0APPBug report

Test failed. Invoice PDF, in your suite.

The PDF total does not match the preview. Reviewed by their engineer before it reached you.

What you get: a reviewed bug report from a test that lives in your repo.
With SmoketestPicks it up as soon as it reaches QA
SmoketestAPP

Failed · 1 of 4 requirements not met · 2m 38s · Attempt 1

The invoice PDF leaves out the proration line. The preview says $312.40 and the PDF says $294.00.

Next: moved to In Progress. Move the ticket back into QA to test again.

Watch the recording · View attempt

What you get: a test written from this ticket, with the proof left on the ticket.

The same eight questions, asked of both.

Bug0
Smoketest
Where work starts
When a pull request runs the suite
When the ticket reaches QA
Who decides what to test
Their engineer, from a coverage plan
It does, from the ticket, pull request, and playbook
Where proof lands
Bug reports, a dashboard, and weekly digests
Result, recording, and steps on the ticket
Surfaces
Web apps, plus voice and chat agents
Web, mobile, APIs, MCP servers, and AI agents
Who keeps checks current
Their engineer and self-healing tests
Smoketest, by following the goal as screens change
Time to first result
Critical flows in one to two weeks
The day you start
Cost model
$2,500 a month flat, up to 500 flows
From $399 a month, shaped to your team
Who owns the release decision
Their engineer gates the release
A named person on your team

Some teams should pick Bug0.

Here is how we would decide if we were in your seat. On a call we will tell you which side you are on.

Choose Bug0 when

  • You want an engineer to own a Playwright suite for you
  • You want one flat price with unlimited runs
  • You need a vendor with SOC 2 before you can start

Choose Smoketest when

  • You want every ticket tested the moment it reaches QA
  • Your team reads results on the ticket, in Jira or Linear
  • You want to start this week, from $399 a month

You can run both.

A managed suite watches the flows you already know about. Smoketest looks after the ticket in front of you, including the parts the suite has no test for yet.

Our founder sets it up with you on a real ticket.

  1. A call with our founder

    Tell us how your team ships and where tickets wait. We will tell you whether it fits.

  2. A real ticket, same day

    We set it up with you on your own board, so it can start the day of the call.

  3. A plan shaped to you

    It starts from $399 a month. Scale is designed with teams that need more runs.

  4. It changes as you do

    New flows, new tools, a new QA hire. We keep adjusting it with you as you grow.

Questions about Bug0

Laying out every option? See them side by side

Bug0 lists $2,500 a month, flat and month to month, for up to 500 user flows, with more priced pro rata. It also offers a discounted 60-day pilot.

It starts at $399 a month for 1,000 runs. Each run is up to 10 minutes, and a longer test counts as two runs or more, one for every 10 minutes. If your team needs more, we design a Scale plan with you, so you stop buying extra runs.

Not in the same way. No outside engineer works your tickets, because the agent does the testing. Our founder sets it up with you and keeps shaping it as your team changes.

Bug0 writes Playwright tests that live in your repos and run in your CI. Smoketest starts from the ticket, so there is no test code for your team to keep.

Yes. Bug0 sells testing for voice and chat agents. Smoketest runs scenarios through your agent's real interface, then checks its replies, tool calls, and what changed in your system.

Yes. Smoketest starts from your tickets, so it does not need your existing tests. You can run both for a sprint or two and compare the results.

Every result links to the recording, the steps, and the reasoning, and says what it did not test, so you can check its work the way you would check a teammate's.

A named person on your team. Smoketest gives them the evidence: what passed, what failed, the recording, and what it did not test. It never signs off a release.

Run one ticket before you sign a contract.

Book a call and we will test one ticket with you. If a managed suite is the better fit for your team, we will say so.

Ready for QA
Done
ACM-436
Show proration on the invoice PDF
Passed, recording