Checkly or Smoketest?
Choose Checkly when your engineers want to write and commit their monitors as code. Choose Smoketest when a ticket you already tested should keep running in production, with no test code to write, from $399 a month.
- Ticket testACM-436 passed on staging
- RegressionRuns after every deploy
- Production monitorRuns every hour
With Checkly, your engineers write the monitors.With Smoketest, a tested ticket becomes one.
Here is one flow,watched both ways.
Checkly is built for engineers, and its monitors live in your repo with the rest of your code. The difference is who writes the monitor and what you get when it fails.
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.
Check failed. invoice-pdf.spec.ts
Expected $312.40, received $294.00. The trace is in the check result.
trace.zip
Failed · Hourly run · 2m 38s
The invoice PDF leaves out the proration line. The preview says $312.40 and the PDF says $294.00.
You will hear again when it recovers.
Watch the recording · View attempt
The same eight questions, asked of both.
Some teams should pick Checkly.
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 Checkly when
- Your engineers want monitors as code in the repo
- You need frequent API checks from many regions
- You want status pages and on-call alerts in one place
Choose Smoketest when
- A ticket you tested should keep running in production
- Nobody has time to write and look after monitors
- You want one teammate from QA through to production
You can run both.
Checkly is strong at fast API and uptime checks. Smoketest follows a full user flow, signed in, and shows you a recording when it breaks.
Our founder sets it up with you on a real ticket.
A call with our founder
Tell us how your team ships and where tickets wait. We will tell you whether it fits.
A real ticket, same day
We set it up with you on your own board, so it can start the day of the call.
A plan shaped to you
It starts from $399 a month. Scale is designed with teams that need more runs.
It changes as you do
New flows, new tools, a new QA hire. We keep adjusting it with you as you grow.
Questions about Checkly
Laying out every option? See them side by side
Checkly has a free plan, then Starter at $24 a month and Team at $64 a month, both billed annually, with usage on top of what each plan includes. Enterprise is a custom quote.
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.
For full user flows, often yes, because it needs no code to keep them going. For frequent API and uptime checks, keep Checkly.
Hourly, daily, or weekly, set for each test, in your timezone.
By email, Slack, or Discord. You can limit it to failures and recoveries, so you hear about what changed and nothing else.
No. It writes the test from your ticket, or from a sentence you give it, and it keeps working as screens change.
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.
Put one real flow on a schedule.
Book a call and we will set one up with you. You see the first run and the recording the same day.