Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

pg-boss review

Free#6 of 36 in Task Queue Software

A deep, self-hosted queue for JavaScript teams already working with PostgreSQL.

8.7/10Editor score
pg-boss8.7 Visit pg-boss

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

pg-boss is an open-source background job queue for Node.js applications, built on PostgreSQL for asynchronous execution and worker processing. It suits JavaScript teams that want queue infrastructure alongside an existing PostgreSQL-backed application rather than a separate hosted queue service. The system supports PostgreSQL-compatible backends, including CockroachDB, YugabyteDB, Citus, and embedded PGlite, giving teams several deployment options within that ecosystem.

The feature set goes beyond basic enqueue-and-process workflows. Queue policies and priorities help organize work, while configurable retries support delay and exponential backoff. Failed jobs can move into dead-letter queues with redrive support. Cron and RRULE scheduling, deferred start times, job dependency workflows, throttling, and debouncing cover recurring, staged, rate-controlled, and duplicate-sensitive workloads. A web dashboard supports monitoring and job management, and optional proxy, CLI, and SQL components extend the surrounding toolkit. Teams choosing pg-boss should be prepared to manage their own deployment and operations.

Integration is a central strength. ORM transaction adapters are available for Knex, Kysely, Drizzle, and Prisma, which can help align job publishing with application data workflows. The open-source model and free plan make pg-boss a fit for teams seeking a queue without a stated paid-tier structure. It is less suitable for buyers who want a fully managed queue, a broad multi-language SDK ecosystem, or infrastructure independent of PostgreSQL-compatible storage. Choose pg-boss when PostgreSQL, Node.js, and detailed queue controls are already part of the application architecture; consider an alternative when hosted operations or a different persistence model matters more.

pg-boss pros and cons

  • Where it wins
    • Retries, backoff, redriveable dead-letter queues, and dependencies
    • Cron, RRULE, deferred jobs, throttling, and debouncing
    • Adapters for Knex, Kysely, Drizzle, and Prisma
  • Where it doesn't
    • Self-hosted deployment requires operational ownership
    • Its core fit is strongest for PostgreSQL-compatible systems
    • Official SDK support centers on JavaScript and TypeScript

pg-boss fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update