Long-running processes
A worker is not a web app, so it does not need an open port. Makofy runs it as an always-on service that stays up and restarts after a crash.
Background worker hosting
Host background workers that chew through your queue 24/7.
Makofy runs your worker as a long-lived process so it keeps pulling jobs off a queue without a web server attached to it.
Queue-friendly
Pair a worker with managed Postgres or Redis to drive Celery, BullMQ, Sidekiq, or your own loop. Scale the worker independently from your web service.
Visibility and control
Watch live logs as jobs process, set concurrency through your code, and use health checks to catch a worker that has stalled or stopped consuming.
Questions
Can I run a background worker 24/7 on Makofy?
Yes. A worker runs as an always-on service with no web endpoint required, and Makofy restarts it if it crashes. Plans start at $6.99/mo with a 7-day free trial.
Does a worker need its own web server?
No. Workers run headless and pull from a queue, so there is no port to expose. You deploy it as a separate service from your web app.
What queue backends can I use?
Connect to Makofy managed Redis or Postgres to back Celery, BullMQ, Sidekiq, RQ, or a custom queue. The worker reads jobs and processes them continuously.
Can I scale workers separately from my app?
Yes. Deploy the worker as its own service so you can resize or run more of them without touching your web service. Boost adds 4GB and 2 vCPU for heavier jobs at $15/mo.
Related pages