QueueHawk's Team plan covers up to 10 applications. Agency covers up to 500. For an agency running Hangfire across client projects, the natural question is: which one do we actually need, and when do we outgrow Team?
One Hangfire-connected instance — a client project, a service, an environment. If you run separate staging and production Hangfire instances for the same client and monitor both, that's two applications, not one. Count real instances, not client contracts, before comparing plans.
If you're a small shop with a handful of active client projects on Hangfire — ten or fewer at a time — Team covers it: 180-day history, Slack/Teams/webhook/email alerts, multiple team members. Retiring an old client project frees up a slot without needing to change plans, since the limit is "applications currently monitored," not "applications ever monitored."
The signal to switch isn't a specific headcount — it's when adding an eleventh (or twentieth, or fiftieth) client project means checking whether you're still under the limit before you install the agent. Once application count becomes something you have to track instead of something you never think about, Agency removes that friction entirely: up to 500 applications, 1-year history, priority support.
Team is $129/mo ($109/mo billed annually) for up to 10 applications — as low as ~$13/app/mo at full capacity. Agency is $299/mo ($249/mo annually) for up to 500 — at 25 applications that's about $12/app, and the per-app cost keeps dropping as you add more client projects. There is no cost crossover to calculate: below the limit Team is simply cheaper, so the question is only whether you need more than 10 applications at once. See the full pricing breakdown, or the separate question of per-application vs. per-job pricing if you're also comparing against a per-monitor tool.
See also: why a single cross-app dashboard beats one Hangfire dashboard per client project in the first place.