Skip to content
Pathwatch Docs

Core concepts

Organisations

Every account belongs to one or more organisations. A personal org is created automatically on signup. Team orgs are invite-only and have their own billing, members, monitors and alert channels.

All PathWatch resources are scoped to an organisation — there is no cross-org visibility.

Monitors

A monitor is a recurring check against a target. Each monitor has a type — one of uptime_http, ssl, dns, port, uptime_ping, uptime_keyword, domain_expiration, heartbeat, browser_lite, or flow — a schedule, a set of regions, and zero or more attached alert rules.

PathWatch ships two browser monitor types:

  • Browser Lite — single-page browser check. Navigate to a URL, run a handful of assertions, capture a screenshot on failure.
  • Browser Flow — multi-step browser check. Sign-in, checkout, form-submission flows with up to 50+ step actions.

Both run on real Chromium, Firefox, or WebKit. See Browser Lite and Browser Flow for the full configuration reference.

Checks and check runs

Each scheduled execution produces a check run — one row per region. A monitor configured for three regions produces three result rows per interval. The monitor’s overall status is computed across all regions using either the default aggregation (“any region down = degraded, majority down = down”) or your custom success criteria.

Variants and execution targets

Each uptime, browser-lite, and browser-flow monitor maps to a variant — standard / fast / real-time — which carries its own minimum check interval. Variants are billed as slots: a Pro plan includes 100 standard uptime slots, 50 fast, 10 real-time, plus browser variants. See slot quotas.

A monitor’s execution targets are the regions and runners it checks from. A single HTTP monitor checked from five regions = five execution targets. Plans include a fixed execution-target pool; extra +25 packs are available as add-ons.

Regions

PathWatch runs cloud checks from 46 locations across seven continents. You see them in the picker as cities, never as cloud provider names. See the Regions reference for the full live list.

Region access is tier-gated:

  • Free — 6 locations (Tier 1 Essential — major hubs)
  • Starter — 16 locations
  • Pro — 40 locations
  • Business — all 46 locations

A hardened location is one served by two or more independent cloud providers — the dispatcher fails over between providers automatically. See Regions & locations.

Confirmation regions

To avoid pages from one flaky region, configure your monitor with multiple regions and your alert rule with a confirmation threshold. A failure alerts only when the threshold count of regions agree. See Confirmation regions.

Runners

A runner executes checks. PathWatch’s cloud runners are the default — you don’t need to deploy anything. Self-hosted runners (a Docker container you run on your own infrastructure) become available on the Starter tier and up — 1 runner on Starter, 3 on Pro, 10 on Business. They let you monitor internal services, private IPs, and VPN-protected applications from inside your own network. Self-hosted runners are also the only runners that currently support IPv6 outbound — see IPv6 monitoring.

See techdocs.pathwatch.app (paid plan) for deployment instructions.

Entitlements

Plan tiers (Free, Starter, Pro, Business) grant entitlements — per-variant monitor slot quotas, region tier access, retention window, runner permissions, alert channels, and a long list of feature flags. Add-ons grant extra entitlements stacked on top.

The current entitlement bundle is visible at Settings → Billing and broken down at Usage.