Billing
CronRadar bills by the number of jobs it protects. Runs, retries, and API requests are never billed, and there is no charge per team member. Current prices are on the pricing page.
| Plan | Price | Monitors | Run history | Alert history |
|---|---|---|---|---|
| Free | $0 | Up to 10 active monitors | 30 days | 90 days |
| Pay as you grow (Grow) | First 10 active monitors free, then $1 per monitor a month | No limit | 90 days | 180 days |
| Business | By inquiry | Custom requirements |
What counts as a monitor
A monitor counts while it is active. The count covers every application in every team the billing account's owner owns, including development and staging jobs. Paused jobs, and jobs paused because they vanished from your scheduler, do not count.
Jobs created by any team member count toward the team Owner's billing account.
How the peak works
On Grow, CronRadar records your number of paid monitors (active monitors beyond the free allowance) every hour and keeps the highest count of the billing period. Stripe bills that peak in arrears at the end of the period. Pausing or deleting monitors lowers future counts but not a peak already recorded, so it does not reduce the current period's bill. The billing period follows your Stripe subscription, which starts when you subscribe.
The Billing page in the console shows the period's peak paid monitors and the estimated price.
Monthly budget
On Grow you can set an optional monthly budget in US dollars under Billing. There is no budget by default, and you can change or remove it at any time.
A new monitor that would raise the period's bill above the budget is created but held paused, whatever its source: discovered by a framework integration, created in the console, through the API or by a coding agent, or created by its first report with ?schedule=. A first report is still recorded; it is not refused. Held monitors show "Held by budget" in the console, the sync response reports them, and the Billing page shows how many are held.
The budget only gates new monitors. Monitors that are already running are never paused by it, and monitors within the period's recorded peak still fit, so lowering the budget does not stop jobs you are already paying for this period. Resuming a paused job yourself is checked the same way.
Held monitors resume on their own, oldest hold first, as soon as the budget allows: when you raise or remove the budget, or pause or delete other monitors. CronRadar checks every five minutes and right after those changes in the console. A held job that leaves its framework's registry stops waiting and resumes only if it comes back. The Billing page shows when the budget is reached; no email is sent.
At the Free limit
On Free, the same rule applies at the free allowance: discovered jobs beyond it are held paused and labeled "Plan limit · unprotected", console creation is refused, and a first report for a new job key returns 402. Pause or delete jobs you no longer need, or upgrade to Grow.
Upgrade, invoices, and cancellation
Choose Add a card on the Billing page to move to Grow through Stripe Checkout. Manage billing opens the Stripe customer portal, where you update your card, download invoices, and cancel.
When you cancel at the end of the period, Grow continues until then. When the account returns to Free, the oldest active monitors up to the free allowance keep running and the rest are paused. Run and alert history shorten to the Free windows at the next daily cleanup.
For custom requirements, ask about Business on the contact page.