hangfireio/hangfire

An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 31 minutes ago
Added to GitGenius on September 6th, 2026
Created on August 6th, 2013
Open Issues & Pull Requests: 942 (+0)
GitHub issues: Enabled
Number of forks: 1,754
Total Stargazers: 10,135 (+0)
Total Subscribers: 306 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.4 days
Mean response time: 111.1 days
90th percentile: 232.6 days
Tracked items: 206

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "t: bug" is answered fastest, typically in about 15 hours, while "a: dashboard" waits about 4 days. Only 5% of issues opened in the past year have been closed. Three people close 56% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 139
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 1,241 days
Stale 30+ days: 134
Stale 90+ days: 128

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • t: bug (21)
  • t: question (21)
  • a: core (18)
  • a: dashboard (10)
  • t: problem (9)
  • t: feature-request (6)
  • a: sql-server (5)
  • a: dotnetcore (4)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Hangfire is a background job processing library for .NET and .NET Core applications that enables reliable execution of fire-and-forget, delayed, and recurring jobs without requiring a separate Windows Service or dedicated process.

Hangfire solves the problem of handling CPU and I/O intensive, long-running, and short-running background tasks within .NET applications. It provides a unified programming model that works across shared hosting, dedicated hosting, and cloud environments. The tool supports multiple storage backends including Redis, SQL Server, SQL Azure, and MSMQ, allowing jobs to be queued and processed by a dedicated worker pool that executes them as soon as possible. Delayed tasks can be scheduled to run after a specified time, and recurring tasks use CRON expressions for scheduling. The library also supports job continuations, enabling complex workflows by chaining multiple background jobs together.

Teams should adopt Hangfire when they need reliable background job processing integrated directly into their .NET application without operational overhead. It suits projects ranging from simple fire-and-forget notifications to complex scenarios like batch imports, image processing, recurring reports, and database maintenance. The README identifies Hangfire as a .NET alternative to Resque, Sidekiq, delayed_job, and Celery, positioning it for developers familiar with those tools in other ecosystems who are working in the .NET space.

The project maintains active build status tracking across multiple branches with continuous integration on Windows. Development activity spans both a main branch and a dev branch, indicating ongoing feature work and maintenance alongside stable releases. The tool includes a web dashboard for monitoring and managing background jobs, providing visibility into job execution and system health.