Hangfire

Hangfire is a background-job processor for .NET and .NET Core applications, aimed at developers who want queued and scheduled work to run within their application stack. Its strongest case is persistent, retrying job processing with a built-in dashboard; teams needing batches or throttling should expect to pay for extensions.

Overview

Hangfire handles fire-and-forget, delayed and recurring jobs, along with continuations. Jobs persist in storage rather than depending on one running process: SQL Server and Redis are officially supported, and community-driven storage implementations are also available. That is useful when work must survive application interruptions, but choosing and operating the storage backend remains part of the deployment.

Hangfire describes its processing as at-least-once and retries jobs after unhandled exceptions or application termination. Those safeguards reduce the chance that interrupted work is simply lost, but repeated execution is possible, so job logic should tolerate retries. Processing can span multiple machines, with synchronization handled automatically.

The built-in web dashboard shows processing activity and job states. By default, it accepts only local requests; remote access requires authorization configuration. This gives teams a safer default, while making dashboard access control their responsibility if they need remote visibility.

Key features

• Multiple job patterns: Fire-and-forget, delayed, recurring jobs and continuations cover immediate work and scheduled workflows without limiting Hangfire to a single queueing pattern.
• Persistent storage: Official SQL Server and Redis support gives teams established backend choices; community storage implementations broaden the options, but are not the officially supported choices.
• Retries and distributed processing: At-least-once handling and automatic retries support resilience, while multi-machine processing can suit workloads that need to run across machines. Applications still need to account for jobs being executed again.
• Integrations: Documentation covers ASP.NET, ASP.NET Core, console applications, Windows Services, WCF, Nancy and ServiceStack, making Hangfire relevant beyond a single .NET hosting style.
• Paid extensions: Pro adds batches and batch continuations; Ace adds concurrency and rate-limit throttling. Hangfire.Throttling is officially supported only with Hangfire.SqlServer, Hangfire.Pro.Redis and Hangfire.InMemory storage, so teams should check that compatibility before buying for throttling.
• Dashboard access: The dashboard gives a view of background processing and job state, but remote access is not ready by default: authorization must be configured.

Pricing

Hangfire uses a freemium model. Core is open source under LGPLv3 and free for commercial use, so teams can begin without a license fee. There is no free trial for Pro, but purchases have a 30-day refund period.

The lower-cost paid tier adds Pro but stops short of dedicated support and Ace. Business adds Ace and support; Enterprise costs more for priority support and custom terms. Paid plans are priced per organization per year, not per seat, and carry perpetual licenses. The free plan's stated storage choices are narrower than Startup's. No trial means Pro must be purchased to evaluate under its license, though the 30-day refund period offers an exit.

Platforms

Hangfire supports API, Linux, self-hosted, web and Windows environments. It is a self-hosted deployment rather than a managed service, and its purpose is specifically background processing in .NET and .NET Core applications without requiring a Windows Service or separate process.

Who it's for

Hangfire is a strong fit for .NET teams that need persistent background work, recurring schedules, automatic retries and visibility into job state, particularly when they want to distribute processing across machines. The free Core license makes it accessible for commercial projects. Teams that need batches, batch continuations or throttling should budget for the appropriate paid tier; teams unwilling to manage storage or configure remote dashboard authorization may prefer a different approach.

Pros and cons

Pros

• Free commercial Core: Teams can use the open-source Core without a license fee, including in commercial applications.
• Useful job coverage: Fire-and-forget, delayed and recurring jobs plus continuations serve several common background-work patterns.
• Resilience and scale: Persistent storage, automatic retries and multi-machine processing help jobs outlive process interruptions and support distributed work.
• Visible job state: The built-in dashboard provides a direct view of processing and individual job states.

Cons

• Advanced functions cost extra: Batches and batch continuations require Pro, while throttling requires Ace.
• Storage remains an operational choice: Hangfire is self-hosted, and the team must select and run a storage backend; the free plan names SQL Server 2008 R2+ and In-Memory.
• Remote dashboard access needs configuration: Authorization must be set up before remote requests are allowed.
• No Pro trial: There is no free trial, so buyers must rely on the 30-day refund period rather than a trial license.

Alternatives

For broader Task Queue Software comparisons, start with the category list. Choose IronWorker if its free Basic plan's one-concurrency, five-hours-per-month allowance, 512 MB RAM, 30-minute runtime and 50 scheduled tasks suit a small workload; its free plan also includes a public cluster and basic support. Django Q2 is a free, MIT-licensed option for teams working in its Linux, macOS, self-hosted or web environments. Faktory offers a free AGPL-licensed OSS plan without dedicated support, and a $99 a month Enterprise additional-pack option for teams considering paid expansion.

Graphile Worker is a free MIT-licensed alternative, with a Worker Pro Launch Offer at $25 a month from $25+ /mo as sponsorship. pg-boss is a free MIT-licensed option that runs in your own database with no per-job charges. Gearman is a free, BSD-licensed alternative. Inngest offers a free tier with five seats, 50k executions, 500k events ingested and 24-hour trace history, making those explicit limits relevant when evaluating its fit. Procrastinate is a free, open-source Python library using PostgreSQL 13+.

Verdict

Choose Hangfire if you are building .NET software and want persistent, retrying background jobs with multiple scheduling patterns and a built-in dashboard, while retaining control of your deployment. Its free commercial Core is a clear starting point; look elsewhere if you need advanced batch or throttling features without a paid license, or do not want to manage storage and dashboard authorization.