# Background workers on Unbroker

Run queue consumers as worker services with their own start commands, configuration and logs.

Canonical URL: https://unbroker.cloud/solutions/background-worker
Updated: 2026-10-14
Author: Unbroker

[Add a worker on Unbroker](https://app.unbroker.cloud/login)

[Deployment tutorial](https://docs.unbroker.cloud/guides/background-worker)

## Build with Unbroker

- **A dedicated worker category:** Run a long-lived process without creating an HTTP endpoint it does not need.
- **Separate application concerns:** Give processing its own start command and resource configuration.
- **Keep the stack connected:** Operate the worker, API and supporting database in the same Unbroker project.

## Move slow work out of the request path

Email delivery, indexing and file processing often belong outside the HTTP request. Unbroker's worker service gives that processing a dedicated place to run while staying close to the application that produces the jobs.

Connect the worker's repository, set the consumer start command and supply queue credentials through runtime variables. You can follow deployment and runtime output from the service in Cloud.

## Give processing its own lifecycle

### Release the consumer independently

A worker change does not have to be a web-server change. Keep the consumer's build and runtime configuration separate so you can understand which process is handling the work.

### Inspect the process doing the job

Use runtime logs and metrics to investigate failures, restarts or memory pressure. Pair those signals with queue age and completion records from your application to understand whether jobs are actually progressing.

## Keep durable work in a durable queue

Bring the queue or job store that fits your application. Unbroker runs the consumer; the queue's acknowledgement and retry mechanisms define job delivery. Design idempotent processing for effects that must not happen twice.

For client notifications after a job completes, you can add Beacon to the product. The durable result stays in the database while connected clients receive an update.

## Deploy a worker with a clear recovery path

The tutorial walks through local queue checks, worker service creation, graceful shutdown and verification with a test job. Use it to establish the operating behavior before connecting production jobs.

## Choose your plan

Worker services require Pro and run one replica. Queue or database resources are separate; configure concurrency inside the consumer for your workload.

[Current pricing](https://unbroker.cloud/pricing)

## Related solutions

- https://unbroker.cloud/solutions/api-with-postgres.md
- https://unbroker.cloud/deploy/nodejs.md
- https://unbroker.cloud/agents.md