Sentry Cron Monitoring Pricing: Cost Per Monitor and Plan Limits

Sentry includes one cron monitor free on every plan, including the $89 a month Business plan, and charges $0.78 per month for each additional monitor. The charge accrues to a pay-as-you-go budget when the monitor is activated, and Sentry states that some plans cannot configure such a budget, naming the free Developer plan specifically. So Developer is capped at exactly one cron monitor with no way to buy a second, and Team at $29 a month is the cheapest plan that can. Twenty scheduled jobs on Team cost $312 a year for the plan plus $177.84 for the nineteen extra monitors, which is $489.84 in total on an annual contract.

Every figure here was read on 9 September 2026 from Sentry's own pricing page and help centre, in USD. Sentry is not geo-localised: refetching the pricing page with a German browser locale returned a byte-identical document with the same dollar figures, which is not true of several vendors in this market.

How much does Sentry cron monitoring cost?

The rate is flat. There is no volume ladder, no reserved-quantity discount published anywhere, and no separate price for a job that runs every minute versus one that runs monthly. You pay $0.78 per monitor per month for everything past the first, whatever the schedule.

Plan prices are the annual contract figures, $312 for Team and $960 for Business. On monthly billing the plans cost $348 and $1,068 a year instead. Sentry does not say whether its annual discount reaches pay-as-you-go units, so the metered column above charges the flat rate in both cases, which is the conservative reading.

How many cron monitors does Sentry include?

One, on every plan. This is the part that catches people out, because the instinct when you run out of an allowance is to upgrade, and upgrading does nothing here. The free Developer plan includes one cron monitor. Team at $29 includes one. Business at $89 includes one. Enterprise is quoted individually and Sentry publishes no figure for it.

That pattern runs through most of Sentry's rate card rather than being specific to crons. Across the fourteen rows of Sentry's own plan comparison, Team and Business are identical on thirteen; the only included quota that changes between the two paid plans is metric monitors, which goes from 20 to 1,000. We worked through the whole table, including why the free plan and the $89 plan include the same amount of eight different things, in the Sentry uptime monitoring pricing breakdown.

One practical consequence: check whether your single free monitor is already spent before you plan around it. Sentry automatically creates an uptime monitor for the hostname that appears most often in your error data, and while that is the uptime allowance rather than the cron one, it is the same kind of surprise. Nobody enjoys discovering a quota was consumed by a default.

Why does a cron monitor cost less than an uptime monitor?

Sentry does not say. The two rates sit next to each other in the same table, on the same plans, in the same billing cycle: $0.78 for a cron monitor and $1.00 for an uptime monitor. That is 28.2 percent more for the uptime unit, and it is the only place in Sentry's rate card where two comparable units carry different prices without an explanation.

A reasonable guess is that it reflects the work involved. An uptime monitor is active: Sentry sends an HTTP request from one of its own locations on your chosen interval, waits up to 30 seconds for an answer and records the result. A cron monitor is passive: your job calls Sentry when it starts and finishes, and Sentry watches for the call that never arrives. The second costs Sentry almost nothing to run. That is a guess about motive though, not something the vendor states, and we would rather label it as one.

Worth noting that the same table writes the uptime overage as "$1.00/uptime alert additional" while the cron row says "$0.78/monitor additional". Monitor and alert are not the same unit, and Sentry's help centre uses "monitor" for both. We treat that as a wording slip on the pricing page rather than a different billing model, but it is the kind of detail worth confirming with sales before you budget for a flapping endpoint.

Do I need a pay-as-you-go budget for Sentry cron monitoring?

Yes, for anything past the first monitor. Sentry's help centre puts it plainly: additional monitors "are accrued to your on-demand/Pay-as-you-go spend when activated". A pay-as-you-go budget is a ceiling you set in advance, and until you set one the extra monitors will not activate.

The important restriction is that not every plan can set one. Sentry names the Developer plan specifically as unable to configure a pay-as-you-go budget. The free tier's limit of one cron monitor is therefore absolute rather than a soft cap you can spend past, which makes Team at $29 a month the real entry price for anyone running more than one scheduled job.

Budget carefully rather than generously, because pay-as-you-go on Sentry covers errors, logs, spans, replays, profiling and attachments as well as monitors, all drawing on the same pot. A month with a noisy release can drain a budget that you set with your cron jobs in mind, and monitors that do not activate are monitors that are not watching anything.

Sentry cron monitoring compared with Healthchecks.io and Cronitor

The three tools price the same job in completely different shapes, so the sticker tells you very little on its own.

Read the third column before the second. Healthchecks.io sells steps rather than slopes: $192 a year covers your first hundred jobs and job 101 effectively costs $60, because the only way to get it is the next tier. Cronitor has no base fee at all, so twenty monitors is $480 a year before anybody logs in, and then $60 a year for each person who does. Sentry's is the only one of the three where the monitors are a rounding error on a bill you were already paying for something else.

That last point is the honest case for Sentry, and it is a strong one. If Sentry is already in your stack, nineteen extra cron monitors cost $177.84 a year. Nobody moves vendors over that. We priced these in full in the Healthchecks.io pricing breakdown and the Cronitor pricing breakdown if you want the tier-by-tier arithmetic.

What Sentry cron monitoring does not tell you

Here is the limitation that decides this for most finance and data teams, and it is not about money.

A cron monitor is passive. Your job sends a check-in when it starts and another when it finishes, and Sentry raises an issue when a check-in fails to arrive or a run exceeds the time you allowed. That catches a job that crashed, a job that never fired because the scheduler died, and a job that hung. It is genuinely useful and it costs almost nothing.

What it cannot catch is a job that runs, exits zero, checks in cleanly and produces the wrong answer. Sentry's own documentation offers an invoice generation job as its example use case, which is exactly the scenario where this matters. An invoice run that completes in the normal eleven minutes and writes zero invoices because an upstream feed returned an empty file will report a perfect green run. So will the nightly job that turns your ledger export into board-ready financial statements from a table that stopped updating on the fourth. The check-in says the process ran. It says nothing about what came out.

The same gap exists on the uptime side and is easier to see there: by default a Sentry uptime check passes on any 2xx status code, so a checkout page returning 200 while rendering a stack trace counts as up. Asserting anything about the response body sits behind a feature called Verification, which is restricted to Sentry's Early Adopter programme and described by Sentry as still in progress.

Closing that gap means checking the output rather than the exit code: a heartbeat that only fires when the job wrote the rows it was supposed to write, plus an endpoint check that asserts on content rather than status. That is the distinction we drew in cron job monitoring, and it is what cron and heartbeat monitoring here is built around.

Is Sentry cron monitoring worth paying for?

For a handful of jobs alongside error monitoring you already buy, yes, easily. The rate is fair, the billing is transparent, there is no volume ladder to misread and no country-specific price list to trip over. Set the pay-as-you-go budget, add the monitors, move on.

It stops being the right answer at two points. The first is scale: at a hundred jobs Sentry's flat $0.78 costs $926.64 a year in metered monitors alone, where Healthchecks.io Business Plus covers a thousand jobs for $768 total. Flat rates lose to volume tiers eventually, and $0.78 loses sooner than most because it never moves. The second is when a silent success would hurt you more than a crash, which for anything touching money, invoices or reporting is usually the case.

If you are pricing the whole Sentry monitoring line rather than just the crons, the plan ladder, the $1.00 uptime rate, the fifteen-minute default detection time and the quota table that barely changes between plans are all in the Sentry uptime monitoring pricing breakdown.