Bee-Queue
5.4#33 in task queue softwareAPISelf-hosted
VisitBee-Queue vs Hangfire
What both publish
| Fact | Bee-Queue | Hangfire |
|---|---|---|
| Dashboard | The README points to Arena for managing jobs and inspecting queue health; Arena's README describes it as a web GUI for Bee Queue, Bull, and BullMQ. | A built-in web dashboard shows job states and processing activity. |
| Integrations | Bee-Queue requires Redis 2.8 or newer; its README recommends Redis 3.2 or newer because some jobs may be delayed with earlier Redis versions. | The documentation lists integrations with ASP.NET, ASP.NET Core, console applications, Windows Services, WCF, Nancy, and ServiceStack. |
| License | The repository includes an MIT license that grants permission to use, copy, modify, distribute, sublicense, and sell copies of the software. | Hangfire Core is open source under LGPLv3 and free for commercial use. |
| Purpose | Bee-Queue is a job/task queue for Node.js, backed by Redis. | Hangfire performs background processing in .NET and .NET Core applications without requiring a Windows Service or separate process. |
Bee-Queue plans
No prices published.
Hangfire plans
- OpenFree
- Startup$500 a year
- Business$1,500 a year
- Enterprise$4,500 a year
Pick Bee-Queue if…
You want what its maker publishes above — check its page for the details.
Pick Hangfire if…
Hangfire suits developers adding scheduled or background jobs to .NET applications. It is relevant for teams that need persistent jobs, retries or processing across multiple machines.