Side by side
JobRunr vs Machinery
Both stand on task queue software. Which one you can start free with, which one lets you read the code, and what each costs once you pay.
Free plan APISelf-hostedWeb
JobRunr combines JVM job scheduling with a free OSS plan and paid capabilities for queues, workflows, and larger deployments. Teams should account for the OSS recurring-job limit and use persistent storage for production.
Visit JobRunr Free plan Self-hosted
Machinery provides a broad queue and workflow feature set in a self-hosted Go library with no listed cost. Broker, result-backend, inspection, and JSON constraints should shape deployment choices.
Visit MachineryThe facts
| JobRunr | Machinery | |
|---|---|---|
| Free plan | Yes | Yes |
| Open source | Not published | Not published |
| Runs on | API, Self-hosted, Web | Self-hosted |
| Lowest paid plan | Startup: €1,200 a year | Free or on request |
| Plans published | 4 | 1 |
| Maker | Not published | Not published |
| Website | jobrunr.io | github.com |
| On task queue software | #20 of 37 | #24 of 37 |
JobRunr: what it does well
- Free OSS plan includes scheduling and automatic retries.
- Supports delayed and recurring asynchronous jobs.
- Official integrations for Spring Boot, Micronaut, and Quarkus.
- Business adds priority queues and workflow management.
- Enterprise supports OpenID Connect dashboard sign-on.
What to know first
- OSS supports up to 100 recurring jobs.
- Production use calls for persistent SQL or NoSQL storage.
- Business license covers one production cluster.
- Enterprise pricing is custom.
Machinery: what it does well
- Free open-source Go library
- Scheduled and periodic tasks
- Custom retry counts with Fibonacci spacing
- Multiple message brokers
- Workflow groups, chains, and chords
What to know first
- Pending inspection requires Redis broker
- JSON limits supported task data
- Results expire after 3600 seconds by default
- AMQP result backend has a parallel-task caution
Alternatives to JobRunr Alternatives to Machinery The whole list