Checkly alternative for no-code journeys

Checkly or Pathly: journeys without writing code

Choose Checkly if your team already writes its Playwright tests and wants to version them in Git. Choose Pathly if you maintain client sites and want a monitored journey without writing or maintaining code.

What each tool checks
What each tool checks	Checkly	Pathly
Multi-step browser journey	Yes : Playwright	Yes : Flow, real browser
Journey built without code	No : Playwright test in code	Yes : click-by-click recorder
Screenshot of the failure	Yes : a screenshot on failure, and traces	Yes : screenshot of the broken step
Video of the failure	Yes : Playwright videos	Yes : on Pro and Business
Monthly report to send to the client	Not stated on its page : not stated	Yes : PDF on every plan, under your brand on Business
EU data hosting stated	Not stated on its page : not stated	Yes : GCP europe-west1, public DPA
Entry price	Free Hobby plan, capped run quota	Free Solo plan, no card

Multi-step browser journey

Pathly: Yes : Flow, real browser
Checkly: Yes : Playwright

Journey built without code

Pathly: Yes : click-by-click recorder
Checkly: No : Playwright test in code

Screenshot of the failure

Pathly: Yes : screenshot of the broken step
Checkly: Yes : a screenshot on failure, and traces

Video of the failure

Pathly: Yes : on Pro and Business
Checkly: Yes : Playwright videos

Monthly report to send to the client

Pathly: Yes : PDF on every plan, under your brand on Business
Checkly: Not stated on its page : not stated

EU data hosting stated

Pathly: Yes : GCP europe-west1, public DPA
Checkly: Not stated on its page : not stated

Entry price

Pathly: Free Solo plan, no card
Checkly: Free Hobby plan, capped run quota

Checkly or Pathly in an agency’s week: four scenes

Checkly is built for a developer team that tests in code. Pathly is built for the agency that maintains its clients’ sites without writing tests. Here is what changes, scene by scene.

Monday, 9 a.m.: the cart stops working

The home page returns 200: Ping stays green, and an uptime monitor sees nothing. The Flow fails at the “Add to cart” step. The alert goes out by email, and to Slack or Teams from Freelance up, with a screenshot of the broken step. On Pro and Business, the failure video also shows the seconds before. The agency fixes it before the client calls.

A new WooCommerce client signs up

In Checkly, a browser check is a Playwright test file, written in its editor or in your repository. Its documentation does not describe a recorder. With Pathly, Lumi recognises WooCommerce, Shopify, PrestaShop, Magento, WordPress, Joomla and Drupal and prepares the Flow for the cart, the login or the form. Each Flow is replayed before it is shown to you, and you validate each step.

The theme changes, the test breaks

A hand-written selector breaks when the client’s theme changes. In Checkly, a developer reopens the code and fixes the test. In Pathly, you re-record the step in a few clicks, or run Lumi on the site again. A Playwright export remains possible if a developer wants to take over.

On the 1st of the month, the report goes to the client

The monthly PDF report shows the client what was checked and what broke. It comes with every plan, under the Pathly brand, and switches to the agency’s brand on Business. Even in a month with no incident, the client sees the work done. Checkly’s public pages do not describe a report to send to a client.

Cost, limits and method

The same need, in figures

Example: an agency watches 20 client sites and 3 checkouts. On Pro, at €69 a month excl. VAT, it gets up to 50 Pings checked every 1 min, and unlimited Flows within 800 runs a month. 3 checkouts tested every 6 hours make 360 runs a month, inside the plan. Checkly bills its browser checks per run, with a free quota and then blocks of 1,000. For a team that already codes its tests, it can come out cheaper. Compare with its pricing page, linked under the table.

What Pathly does not do

Pathly does not keep your journeys in Git as code, and its checks run from Europe only. It does not provide a Playwright trace for every run. To drive it from CI, there is the API, the Terraform provider and the GitHub Action, but the journey stays recorded, not written.

How we compared

The table comes from Checkly’s public pages, read on 11/10/2026: browser check documentation and pricing. What they do not say is marked “not stated”, never “no”. Its prices are not copied, because they change. Spotted a mistake? Write to us from the Contact page and we will fix it.

Common questions

Do I have to write Playwright?

No. In Pathly, the journey is recorded by clicking. Checkly’s browser checks rely on Playwright tests, which suits a team that codes. A Playwright export remains available in Pathly.

Does Pathly fit into CI?

Yes. The API, the SDK, the Terraform provider and the GitHub Action run a Flow and block a deployment if it fails. The journey itself stays recorded in Pathly, not written in your repository.

Can I try before paying?

Yes. The Flow demo opens without an account, and the Solo plan is free, with no card and no time limit, with one Flow per day.

Does Pathly place a real order?

No. Flows prepared by Lumi stop before payment, send no form and only enter test values. A Flow you record yourself stops wherever you stop it.

Where are the data and screenshots stored?

On Google Cloud europe-west1, in Belgium, with a public DPA. The AI explanation of a failure is optional, runs in the EU, never reads the screenshots and is not used to train a model.

Is there a video of the failure?

Yes on Pro and Business: when a Flow fails, the video of that run is kept with the incident. On every plan, the incident keeps the screenshot of the broken step.