Checkly vs statusas.lt
A Checkly alternative when what you need is uptime monitoring and a status page rather than Playwright scripts: 13 locations, a status page included, priced in euros.
TL;DR: Checkly is strong at browser checks with Playwright. statusas.lt is strong at uptime monitoring and status pages. If you need to know your API is down and tell your users — pick us.
Checkly and statusas.lt solve different problems. Checkly runs browser tests against complex user journeys: sign-in, checkout, search. statusas.lt checks whether your endpoints are reachable and fast enough, and tells your users about it on a status page.
If your team already writes Playwright tests and wants them run from the cloud, that is what Checkly is for. If you want to know your API answered 500 from Frankfurt, and your users to see it without you doing anything, our path is shorter.
Pricing differs too: Checkly grows with the number of runs, ours is a flat monthly amount per plan.
Feature comparison
| statusas.lt | Checkly | |
|---|---|---|
| Uptime monitoring | The core of the product | Yes |
| Browser checks (Playwright) | No | The core of the product |
| Status page | Included | No |
| Check locations | 13 | 20+ |
| Monitoring as code | YAML + CLI, Terraform | JavaScript |
| OpenTelemetry export | From the Pro plan | Yes |
| Where data sits | Lithuania | EU / US |
| VAT invoice in euros | Yes | No |
Pricing comparison
| statusas.lt | Checkly | |
|---|---|---|
| Free plan | 1 monitor, 6 locations | A limited number of runs |
| Entry paid plan | €30/mo | Usage-based |
| Pricing model | Flat per plan | Grows with runs |
| Status page | Included | Not available |
Checkly's price depends on how many checks you run and how often; ours does not. Prices come from public pricing pages.
Choose statusas.lt when
- You want uptime monitoring and a status page in one place
- You want a flat monthly price with no run budget to watch
- You need HTTP, TCP, DNS, ICMP, gRPC or UDP checks with assertions
- Your data has to stay in Lithuania
Choose Checkly when
- You need browser-based checks with Playwright
- You test complex user journeys, not just endpoint availability
- Your team already keeps tests in JavaScript
Moving from Checkly
If your usage is mostly API checks, the move is simple:
- 1Create a free account
- 2Recreate your HTTP checks by hand or through YAML and the CLI
- 3Turn on the status page — something Checkly does not have
- 4Set up your alert channels
Keep the Playwright tests on Checkly — we do not have them and will not pretend otherwise.
Frequently asked questions
Does statusas.lt replace Checkly?
It replaces the part that checks whether endpoints are reachable and fast, and adds a status page. It does not replace browser tests with Playwright.
Can I keep monitors in code?
Yes. Monitors are described in a YAML file and pushed with the CLI, or managed with the Terraform provider.
Is there an OpenTelemetry export?
Yes, from the Pro plan — check results can go to your own OTLP collector.