Every question, before you ping support

Pathly watches your critical web journeys. An HTTP scenario checks that a URL responds (status, latency, SSL, domain expiry). A browser scenario replays a real Chrome journey (clicks, typing, assertions) 24/7 from St. Ghislain (GCP europe-west1), and alerts you when it breaks — not only when the server returns 200.

HTTP = one request to a URL: status, latency, SSL cert, domain expiry. Best for “the site responds”. Browser = a real Chrome that opens the page, clicks, types, checks text. Best for login, cart, checkout. Free and Starter = HTTP only. Pro (5 journeys, 200 min/month) and Business (20 journeys, 800 min/month) unlock the browser.

See my scenarios

HTTP 200 means the server answered. Not that “Sign in” is dead, JS broke checkout, or a step now takes 12s instead of 2. Pathly replays the user journey. If ping is green and the scenario is red, customers are blocked even when infra “looks fine”.

Open the dashboard

On Sign in, click “No account yet?”. Enter name, email, password (min. 8 characters). A workspace (org) is created and you are the owner. Default Free plan: 5 HTTP scenarios, no browser, 1 seat, 7-day history.

Create a workspace

Settings → invite by email. They get an /invite/… link (or you copy it). Seat limits: Free/Starter = 1, Pro = 3, Business = 10. Extra seat add-on (€8/month) on Pro and Business. Only an owner manages invites, API keys and webhooks.

Open settings

In Settings you create a key (the secret is shown once). It authenticates automated calls to the Pathly API. The prefix stays visible; store the secret in a vault, never in your source code.

Email + password works on every plan. Enterprise SSO (SAML / OIDC) is not included in Free, Starter, Pro or Business: it’s a custom pack on request, listed on the Pricing page.

1) Pro or Business plan. 2) Recorder → URL (https://…) → Open. A real Chrome starts. 3) Click and type like a user: each action becomes a step on the right. 4) Assertion mode to check that text is visible. 5) Name it and save. Pathly then replays it on your schedule.

Open the recorder

Scenarios → open the browser journey → “Edit scenario”. The recorder reloads steps. Restart from the beginning or continue at the end. Text checks no longer block editing. Save again to publish the new version.

See my scenarios

Scenarios → New HTTP scenario. URL, name, latency threshold (ms), GCP regions (St. Ghislain / Frankfurt / Hamina), interval by plan (Free min. 5 min, Starter 3 min, Pro/Business down to 1 min). Pathly also stores SSL (issuer, expiry) and domain expiry.

Those are the official Google Cloud cities Pathly launches checks from: St. Ghislain (europe-west1, Belgium — current worker), Frankfurt (europe-west3) and Hamina (europe-north1). GCP has no region in Lyon or Lille. Paris exists (europe-west9) but Pathly does not run a worker there.

On a browser scenario page, each step is compared to the previous run and the average (7 / 14 / 30 days). Green = faster, red = slower. Useful to catch a login or checkout creeping up before it times out.

Yes, from Pro: failure screenshot + browser scenario video, on the run history. Free and Starter have no browser captures (no browser scenarios). Artifacts follow plan retention (7 / 30 / 90 days).

See run history

HTTP: Free every 5 min, Starter 3 min, Pro and Business down to 1 min. Browser: Pro every 5 min, Business down to 1 min. Faster intervals use more browser minutes (each run rounds up to the next minute).

Yes. On the scenario page, turn off “Enabled”. Pathly stops running it. That saves run quota, but it still counts toward your HTTP / browser scenario cap until you delete it.

Settings → alert email. Included from Starter (not Free). Option to also notify on recovery to OK. An incident opens under Incidents; you can add a postmortem.

See incidents

Settings → paste your Slack webhook URL. Pathly encrypts it. You can remove it in one click. Generic event webhooks (not Slack) are on Business, or the “webhooks / status” add-on on Pro (€14/month).

Configure Slack

/status = Pathly’s own health (site, API, monitoring). Your customer page = Settings → public address (e.g. acme) + “make public”. Customers see your scenarios at /status/acme, optional logo. The address must be unique. Useful during incidents without opening Pathly.

View Pathly status

In Settings, enable the digest and set an email. You get a periodic summary (uptime, incidents) instead of living in the app. Independent from real-time alerts.

Free €0: 5 HTTP, every 5 min, 7 days, 1 seat, no email/browser. Starter €23: 25 HTTP, 3 min, email, 30 days, 1 seat. Pro €59: 50 HTTP (1 min), 5 browser journeys, 200 Chrome min/month, screenshots, 3 seats, 90 days. Business €179: 200 HTTP, 20 journeys, 800 min, 1 min browser interval, Slack/webhooks, 10 seats. SSO and large volume = quote.

See pricing

Each Chrome run rounds up to the next minute: 1 second → 1 billed minute, 61s → 2 min. Pro 200 min/month, Business 800. +100 min pack = €22/month (Pro/Business, up to 20 packs). If you exceed quota, browser runs are rejected until the next cycle or a pack.

Around 80% usage (HTTP, journeys, or minutes) a banner appears. Plan & options shows usage versus your limits. Upgrade or add a pack: +25 HTTP €17, +1 browser journey €12, faster HTTP €26, retention €36, seat €8.

Open Plan & options

Free 7 days, Starter 30, Pro and Business 90. After that, runs (and captures) are purged. Extra retention add-on (€36/month, Pro/Business) if you need more archive volume on a 90-day basis — per-run product cap remains 90 days.

Plan & options → “Upgrade to …” to pay by card, or “Billing portal” for cards and invoices. Monthly subscription, no annual commit shown.

Data and checks run on Google Cloud, region europe-west1 (St. Ghislain, Belgium, EU). Secrets (Slack webhook, scenario passwords if you enter any) are encrypted. Session lasts 14 days. No plaintext passwords in the app.

Only members of your org see scenarios, runs and captures. The public status page exposes only what you publish. To delete an account and associated data, contact Pathly. We don’t store card numbers: payments are handled by the payment provider.

Expected: HTTP and browser don’t measure the same thing. Open the run: screenshot, failing step (missing selector, assertion text gone, timeout). Often a cookie overlay, A/B test, or a login that changed. Re-record or relax the assertion.

Check: Pro or Business plan (Free has no browser), URL starts with https://, browser minutes available. Opening can take 10–20s. A red banner shows the cause (timeout, unreachable site, plan). Pathly watches public sites, not sites only reachable on your internal network.

Minutes or journey count is full. Plan & options: upgrade, minutes pack (+100 min / €22) or journey pack (+1 / €12). A disabled scenario stops consuming minutes but still counts toward the cap until deleted. Minutes reset on the monthly cycle.

See my usage

HTTP checks store the certificate issuer, its expiry and the domain expiry. Watch the scenario page: a soon-to-expire cert or domain will flip the check. Set an alert email so you don’t miss it.