Pricing & Billing

Checkly supports different kinds of checks and monitors which are billed slightly differently depending on their nature:

• Synthetic checks include: Browser, API, and Multistep. Those checks are billed per check run.
• Uptime Monitors include: URL, TCP, and Heartbeats and are billed per number of monitors.

Before diving into pricing details, here are key concepts that affect your costs:

• Check run: A single execution of a check or monitor
• Parallel scheduling: Running checks simultaneously from multiple locations
• Retries: Automatic re-execution of failed checks
• Flaky checks: Checks that fail intermittently due to network issues or timing problems
• Prepaid check bundles: Discounted packages of check runs purchased in advance
• Overages: Additional charges when you exceed your plan’s included check runs or monitors, typically at higher rates than prepaid bundles

This table shows the base cost for checks and monitors, and how Parallel Scheduling or retries affect your total cost:

When configuring your check frequency and scheduling strategy, the cost helper will estimate the monthly cost for the check. This widget appears in the check configuration interface and automatically calculates costs based on your settings.

API, as well as browser checks, have a base price per check run. Always refer to our pricing page for the latest prices. The base cost is typically listed as $X per 1k or 10k check runs.

If you use features that multiply the number of check runs, such as parallel scheduling and retries, your cost will increase.

When a check is running in parallel, it will run once on each selected location per execution. If you change a check from using the round-robin scheduling method to running in parallel, be aware that the cost will multiply by the number of locations you have selected.

Balance the number of locations the check is using to ensure you are quickly made aware of potential issues in critical locations without running an unnecessary amount of checks.

When a check is retried, this counts as a new check run. A flaky check can increase your check run costs above the expected. If you have problems with flaky checks, ask our community or our support for tips on how to improve check stability and reduce cost.

Multistep check pricing is slightly different from browser and API checks. A Multistep check is billed based on the number of requests done per check run. Each request in a Multistep check run is billed at the same rate as a regular API check run, as they are performing the same basic operation.

A Multistep check with 0 requests is billed as if it has 1 request.

When a Multistep check is run in parallel, the whole check (with any number of requests) is run from all included locations. That means that the cost is going to equal the number of locations the check is run from multiplied by the number of requests.

As a Multistep check is retried as a whole, the final cost of a retried Multistep check is based on the number of requests executed multiplied by the number of retries.

A given set of Uptime Checks are included in the Starter, Team, and Enterprise plans. Users can complete the existing plan allowance of Uptime Checks by adding to their plans packages of 25 monitors for $10 each.

Uptime monitors include:

• URL monitors
• TCP monitors
• Heartbeat monitors
• DNS monitors (Coming up soon)
• ICMP monitors (Coming up soon)

Parallel Scheduling on Uptime monitors is limited to Enterprise plans.

Retries on Uptime monitors are included in the price and limited to 1 retry per monitor per run.

Here are some common scenarios to help you estimate costs:

• Browser check running every hour (24 times/day, ~720 times/month)
• Base cost: $5 per 1000 runs
• Monthly cost: $3.60

• Same browser check running from 5 locations in parallel
• Monthly runs: 720 × 5 = 3,600 runs
• Monthly cost: $18.00

• Same single-location check with 15% retry rate
• Monthly runs: 720 + (720 × 0.15) = 828 runs
• Monthly cost: $4.14

• 4 separate API checks vs 1 Multistep check with 4 requests
• Both scenarios: 4 requests × 720 runs = 2,880 requests/month
• Monthly cost: $0.58 (both scenarios are equivalent)

1. Use round-robin scheduling instead of parallel when possible to reduce location multipliers
2. Optimize check frequency - not all checks need to run every minute
3. Fix flaky checks to reduce unnecessary retries
4. Consolidate related API checks into Multistep checks when it makes sense
5. Monitor your usage regularly through the Checkly dashboard
6. Consider prepaid bundles for predictable cost savings

When you exceed the check runs or monitors included in your plan, you’ll be charged for overages at a higher rate than the prepaid bundle pricing. Overage charges apply to:

• API check runs beyond your plan’s monthly allowance
• Browser check runs beyond your plan’s monthly allowance
• Multistep requests beyond your plan’s monthly allowance
• Additional uptime monitors beyond your plan’s included monitors

Overages are calculated based on your actual usage beyond your plan limits:

• Hobby Plan: Hard-capped at 10k API and 1.5k browser check runs - no overages possible, upgrade required
• Team Plan: Overages charged at standard rates for usage beyond plan limits
• Enterprise Plan: Custom overage rates negotiated as part of your contract

To avoid unexpected overage charges:

1. Monitor your usage regularly through the Checkly dashboard
2. Consider upgrading your plan if you consistently exceed limits
3. Optimize check frequency and locations to stay within limits

For Enterprise pricing or volume discounts, contact our sales team through the pricing page.

Responsible use

Last updated on July 10, 2025. You can contribute to this documentation by editing this page on Github