Developers struggle to run and monitor long-lived background jobs
Developers running ad hoc or API-triggered tasks need those tasks to keep running independently of the caller and need a straightforward way to inspect their status and output. The evidence describes cumbersome framework or container setups, costly monitoring, and Windows services that require executable-specific support and do not capture standard output to a file. A lightweight job runner could address most of these needs, though durable workflow platforms are a more specialized adjacent problem.
For python developers and small teams running background jobs. Mentioned from Mar 2024 to Oct 2025 on Hacker News and Stack Exchange.
4 different people described this problem in 4 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Tried with Django and celery and docker, ended up being a pain in the ass since I have to modify on the fly. Pm2 is neat, but the monitor solution is pricey
A client/user (not necessarily a human, but may be another script) has to trigger a long running task (containing some input arguments) via calling an API
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks