Most net stars, last 30 days
triggerdotdev/trigger.devTrigger.dev – build and deploy durable AI agents and workflows
+264
18% of the net stars of this Tag
Tags / Backend and APIs /
A library or service that stores background jobs or tasks and runs them with workers, with retries (a task queue); not a general message broker.
The 38repositories with this Tag gained +1,451 net stars in the last 30 days, 3% more than the 30 days before.
0 created in the last 90 days · 16 published a release in the last 30 days · 252K stars in total
Oct 5, 2026Nov 3, 2026
Most net stars, last 30 days
triggerdotdev/trigger.devTrigger.dev – build and deploy durable AI agents and workflows
+264
18% of the net stars of this Tag
Largest Pace, last 30 days
celery/celeryDistributed Task Queue (development branch)
2.1×
+225 net stars, against +108 in the 30 days before
Most stars, created in the last 90 days
No other repository with this Tag was created in the last 90 days.
Net stars gained each week. The repositories that gained the most have their own color.
triggerdotdev/trigger.dev gained 19% of the net stars of this Tag in the last 13 weeks.
38 repositories with this Tag. Select a column name to change the order.
| # | Repository | Stars | Gained, 7 days | Pace | |
|---|---|---|---|---|---|
| 1 | triggerdotdev/trigger.dev Trigger.dev – build and deploy durable AI agents and workflows | 17K | +72 | 1.5× | |
| 2 | celery/celery Distributed Task Queue (development branch) | 29K | +47 | 0.7× | |
| 3 | skypilot-org/skypilot The AI Compute Platform for frontier teams. SkyPilot turns fragmented AI compute into one AI supercomputer, so frontier AI teams build custom intelligence faster. | 11K | +30 | 0.8× | |
| 4 | hatchet-dev/hatchet 🪓 An orchestration engine for background tasks, AI agents, and durable workflows | 8.2K | +29 | 0.9× | |
| 5 | riverqueue/river The polyglot queue: Fast and reliable background jobs in Go, Java, JS, Ruby, and Rust on Postgres/SQLite. | 5.9K | +29 | 1.1× | |
| 6 | timgit/pg-boss Queueing jobs in Postgres from Node.js like a boss | 4.1K | +25 | 1.0× | |
| 7 | taskforcesh/bullmq BullMQ - Message Queue and Batch processing for NodeJS, Python, .NET, Elixir, Rust and PHP based on Redis or PostgreSQL | 9.6K | +19 | 0.7× | |
| 8 | hibiken/asynq Simple, reliable, and efficient distributed task queue in Go | 14K | +11 | – | |
| 9 | oban-bg/oban 💎 Robust job processing in Elixir, backed by modern PostgreSQL, SQLite3, and MySQL | 4K | +7 | – | |
| 10 | graphile/worker High performance Node.js/PostgreSQL job queue (also suitable for getting jobs generated by PostgreSQL triggers/functions out into a different work queue) | 2.4K | +6 | – | |
| 11 | HangfireIO/Hangfire An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required | 10K | +5 | – | |
| 12 | RichardKnop/machinery Machinery is an asynchronous task queue/job queue based on distributed message passing. | 8K | +5 | – | |
| 13 | OptimalBits/bull Premium Queue package for handling distributed jobs and messages in NodeJS. | 16K | +3 | – | |
| 14 | sidekiq/sidekiq Simple, efficient background processing for Ruby | 14K | +3 | – | |
| 15 | Bogdanp/dramatiq A fast and reliable background task processing library for Python 3. | 5.3K | +3 | – | |
| 16 | rq/rq Simple job queues for Python | 11K | +2 | – | |
| 17 | coleifer/huey a little task queue for python | 6.1K | +2 | – | |
| 18 | jamesmh/coravel Near-zero config .NET library that makes advanced application features like Task Scheduling, Caching, Queuing, Event Broadcasting, and more a breeze! | 4.3K | +2 | – | |
| 19 | jobrunr/jobrunr An extremely easy way to perform background processing in Java. Backed by persistent storage. Open and free for commercial use. | 3.1K | +2 | – | |
| 20 | taskiq-python/taskiq Distributed task queue with full async support | 2.4K | +2 | – |
Net stars of the last 30 days are 2 or more times those of the 30 days before.
Net stars of the last 30 days are 50% or less of those of the 30 days before.
No repository with this Tag meets this rule now.
Created on GitHub in the last 90 days.
No repository with this Tag meets this rule now.
Created more than 2 years ago, with a push in the last 7 days and a GitHub release in the last 30 days.
The newest GitHub release is more than 180 days old. A repository that never published a release is not in this list.
An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The page of each repository shows the quote of each of its Tags. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository.
All numbers come from the Star History of the repositories that have the Tag now. A period is a run of complete UTC days. All numbers on this page count only the repositories that AwesomeRepos shows in lists. A machine computes them each hour.
For each repository, a period counts only when Star History has each of its days, or when the repository was created in the period. Otherwise the table shows "–". The bars of a week with no complete data are grey.
The Pace is the net stars of a period divided by the net stars of the period before. It shows only when Star History covers each day of the period before, with at least 3 net stars a day on average.
The chart at the top adds up the net stars of all the repositories with the Tag. The darker area is the part from the Seed Dataset; the rest is from rising Admissions. A rising Admission comes into the Repository Index because it gained stars quickly. Its Star History before its Admission comes from the Repository Host. Thus the days before many rising Admissions are higher than they were for the repositories in the index at that time. The repositories of the Seed Dataset are a set that does not change.
The releases are the GitHub releases of each repository. The lists and the table do not rank repositories, and they do not say that one repository can replace another.