pg-boss
pgboss.io
- Free plan
- Linux
- Web
- API
- Self-hosted
What pg-boss is
pg-boss is a Node.js job queue that uses PostgreSQL for background processing and asynchronous execution. It lets applications enqueue work in the same database transaction as a related data change, so the job is recorded only when that transaction commits. Workers use PostgreSQL SKIP LOCKED to claim jobs without blocking one another, with atomic commit safety; delivery is at least once, so handlers may run more than once. Queue controls include priorities, rate limits, debouncing, concurrency policies, retries with exponential backoff, and dead-letter queues. It also supports cron and RRULE schedules, deferred jobs, dependencies, and workflow orchestration. Adapters are available for Knex, Kysely, Drizzle, and Prisma. Supported database backends include PostgreSQL, CockroachDB, YugabyteDB, Citus, and PGlite. Separate packages provide a web dashboard and a JSON HTTP API proxy. pg-boss is MIT-licensed and self-hosted, with no per-job charges. It requires Node 22.12 or higher or Bun, plus PostgreSQL 13 or higher.
Who it suits
It suits teams already using PostgreSQL who want background job processing without operating another system. The documentation is aimed at teams comfortable with relational database semantics, SQL, queries, and backups.
Good to know, and what to watch
- Jobs can share transactions with related data changes.
- Includes retries, priorities, rate limits, and dead-letter queues.
- Supports cron, RRULE, deferrals, and dependency workflows.
- Adapters cover Knex, Kysely, Drizzle, and Prisma.
- MIT-licensed with no per-job charges.
- Requires Node 22.12 or higher or Bun.
- Requires PostgreSQL 13 or higher.
- Job delivery is at least once, so handlers may repeat.
- Queues share a partitioned table by default.
Plans
Every plan and pricepg-boss
Free plan
The verdict
pg-boss brings job processing, scheduling, and queue controls to teams already operating a supported database. Account for its runtime and database requirements, at-least-once delivery, and shared-table behavior when planning its use.
What the maker publishes
- Concurrency
- It uses PostgreSQL SKIP LOCKED so concurrent workers claim jobs without blocking each other, with atomic commit safety. source
- Dashboard
- The @pg-boss/dashboard package provides a web dashboard for monitoring and managing jobs, queues, and schedules. source
- Dashboard
- The separate @pg-boss/dashboard package provides a web dashboard for monitoring and managing jobs, queues, and schedules. source
- Database backends
- Supported backends include PostgreSQL, CockroachDB, YugabyteDB, Citus, and embedded PGlite. source
- Database backends
- The documented backends are PostgreSQL, CockroachDB, YugabyteDB, Citus, and embedded PGlite; the page says Aurora DSQL and Spanner are not yet supported. source
- HTTP API
- The @pg-boss/proxy package exposes pg-boss methods through a JSON HTTP API for non-Node runtimes, connection pooling, or scalability. source
- HTTP API
- The @pg-boss/proxy package exposes pg-boss methods over JSON HTTP for use from other runtimes and offers optional basic authentication and configurable CORS. source
- Intended users
- The maker says pg-boss suits teams already running PostgreSQL that want to avoid adding another system to operate and monitor. source
- Job delivery
- Jobs are delivered at least once, so a worker may run a handler more than once for the same job. source
- License and maintenance
- pg-boss is MIT-licensed and maintained by one person; the maker says sponsorship supports maintenance, security response, and support. source
- License and support
- pg-boss is MIT licensed, maintained by one person, and sponsorship funds maintenance, security response, and support. source
- Observability
- The project lists OpenTelemetry traces and metrics, including continuation of a job's trace from send() to the worker processing it. source
- Operational limit
- By default all queues share one partitioned job table, which can affect performance if a queue grows significantly or develops an unexpected backlog. source
- ORM integrations
- Transaction adapters are provided for Knex, Kysely, Drizzle, and Prisma. source
- ORM integrations
- Its transaction adapters support Drizzle, Knex, Kysely, and Prisma. source
- Proxy security
- The proxy supports optional basic authentication, configurable CORS, and route allowlists or denylists. source
- Queue features
- The project lists retries with exponential backoff, priorities, dead-letter queues, rate limiting, debouncing, and concurrency policies. source
- Queue policies
- Features include rate limiting, debouncing, concurrency controls, priorities, dead-letter queues, and retries with exponential backoff. source
- Requirements
- The project requires Node 22.12 or higher or Bun, plus PostgreSQL 13 or higher. source
- Requirements
- The homepage lists Node 22.12 or higher, or Bun, and PostgreSQL 13 or higher as requirements. source
- Scheduling
- It supports job dependency workflows, cron and RRULE scheduling, and job deferral. source
- Scheduling and workflows
- pg-boss supports cron and RRULE scheduling, job deferral, and dependency-based workflow orchestration. source
- Target users
- The documentation says it is most suited to teams familiar with relational database semantics, SQL, querying, and backups, especially teams already using PostgreSQL. source
- Transactions
- Jobs can be sent in the same database transaction as the data change they belong to, so the job exists only if that transaction commits. source
Checked against the maker's pages on 2 Oct 2026.