Platform
Background workers
A background worker is an always-on process that runs in the background with no public URL. It is the right shape for a bot, a queue consumer, a scraper, or any job that needs to keep running rather than answer web requests. Available on the Developer and Team plans.
What a worker is
Unlike a web app, a worker does not serve HTTP, so it has no domain and no port. It simply runs. Lofenta keeps the process alive, restarts it if it exits, and streams its logs, the same way it runs a web service, minus the public address. Use it for anything that should be up continuously in the background.
Create one
Start a new project and set the service type to Worker. A worker runs from a Git repository or a public Docker image. Then set the start command:
- From a repo. The start command is required. It is the command that keeps your worker running, for example
node bot.jsorpython worker.py. - From an image. The start command is optional. Leave it blank to run the image entrypoint, or set one to override it.
There is no port to configure, because a worker never receives traffic.
How it runs
A worker runs around the clock. If it crashes, Lofenta restarts it automatically, and it comes back on its own after a server reboot. Live logs stream on the project page just like a web app.
The project page shows the worker status as Deploying, Running, Crashed, Paused, or Stopped. Because there is no URL to probe, a worker counts as healthy as long as its process stays up.
Plans and limits
Workers are available on the Developer and Team plans. A worker counts toward your plan service allowance, shared with your web apps: Developer includes 5 services and Team includes 20.