Cron and background-job monitoring tools generally price one of two ways: per monitored job, or per application. Neither is "wrong" — but which one is cheaper for you depends entirely on how many job types you run in each application, and that's worth doing the actual math on before picking a plan.
Several monitoring tools in this space charge a flat rate per monitored job — commonly around a dollar per job per month, sometimes cheaper at volume. Every recurring job you track is a line item. It's simple to reason about at small scale: three jobs, three dollars. The trade-off shows up as your job count grows — add a fourth recurring job to an existing project, and the bill moves with it, every time, indefinitely.
QueueHawk plans scale by how many applications you're monitoring — not job count or event volume (see the full breakdown on the pricing page). Every application on a plan includes an unlimited number of job types. A project with 3 recurring jobs and a project with 40 cost the same, because both are still just "one application."
Here's what that looks like across a few realistic setups, using a common $1-per-job reference rate for the per-job side:
| Setup | Per-job pricing | QueueHawk |
|---|---|---|
| 1 app, 3 job types (just getting started) | $3/mo | Free — $0/mo |
| 1 app, 40 job types (one busy project) | $40/mo | Starter — $35/mo |
| 5 apps, 15 job types each (75 total) | $75/mo | Team — $129/mo |
| 12 apps, 30 job types each (360 total) | $360/mo | Agency — $299/mo |
No consistent winner — it genuinely depends on your job count per application. A handful of jobs across a couple of small projects: per-job pricing is likely cheaper. Enough job types piling up on the applications you already pay for: the per-app ceiling starts winning, and it's a ceiling you can see in advance rather than one that creeps up with every job you add.
Enter how many applications you run and roughly how many job types each one has:
Estimate only — $1/job is a common reference rate, not a specific vendor's current price, and it will drift out of date. QueueHawk plan boundaries: Starter (1 app), Team (up to 5 apps), Agency (unlimited apps) — see the pricing section for what's included in each.
Either way, the point isn't that one model is universally cheaper — it's that per-app pricing means you never have to think about it again once you've picked a plan. Adding a recurring job to an existing project is a code change, not a billing event.
See also: monitoring Hangfire across multiple client apps, and the full pricing breakdown.