head to head · open source
conductor vs resque-scheduler
conductor has 32,401 GitHub stars, 1,051 forks, 253 open issues and last shipped yesterday. resque-scheduler has 1,746 stars, 479 forks, 87 open issues and last shipped yesterday. conductor leads on adoption by 1,756% (32,401 vs 1,746 stars). conductor is written in Java under Apache-2.0; resque-scheduler is written in Ruby under MIT. conductor has attracted 3% as many forks as stars, resque-scheduler 27%. conductor was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| conductor | resque-scheduler | |
|---|---|---|
| GitHub stars | ★ 32K | ★ 1.7K |
| License | Apache-2.0 | MIT |
| Written in | Java | Ruby |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 1.1K | ⑂ 479 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick conductor if
- You weight community size — 32K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Java
- You value the larger contributor base for long-term maintenance
pick resque-scheduler if
- You want the resque-scheduler feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Ruby
- You evaluated both and resque-scheduler fits your workflow better
About conductor
Conductor Durable Execution for Workflows and Agents Build agents that adapt. Run graphs that endure. Conductor is an open source durable execution platform for microservices, AI agents, and adaptive workflow graphs. It turns runtime choices—loops, branching, fan out, tool calls, approvals, retries, and cancellation—into durable, inspectable execution. It originated at Netflix and is actively maintained by Orkes and the community. Get Running in 60 Seconds Prerequisites: Node.js v16+ and Java 21+ must be installed. Open — your server is running with the built in ui next UI. Upgrading from a previous version? The…
read the full conductor overview →
About resque-scheduler
resque scheduler ================ Description Resque scheduler is an extension to Resque that adds support for queueing items in the future. Job scheduling is supported in two different ways: Recurring (scheduled) and Delayed. Scheduled jobs are like cron jobs, recurring on a regular basis. Delayed jobs are resque jobs that you want to run at some point in the future. The syntax is pretty explanatory: Documentation This README covers what most people need to know. If you're looking for details on individual methods, you might want to try the rubydoc. Installation To install: gem install resque scheduler If you…
read the full resque-scheduler overview →
More in Infrastructure & Operations
Related comparisons
More Orchestration & Scheduling projects
Compare either of these against the rest of the Orchestration & Scheduling field.
Frequently asked questions
Is conductor or resque-scheduler more popular?
conductor has 32,401 GitHub stars and resque-scheduler has 1,746. conductor has the larger community by that measure.
Are conductor and resque-scheduler free?
Both are open source. conductor is licensed under Apache-2.0 and resque-scheduler under MIT. Neither carries a licence fee.
What is the difference between conductor and resque-scheduler?
conductor is written in Java and resque-scheduler in Ruby. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, conductor or resque-scheduler?
Choose conductor if you want the larger community (32,401 stars) or its Apache-2.0 licence terms. Choose resque-scheduler if its feature set, stack or MIT licence fits better. Both are self-hostable.