Graphile Worker

Graphile Worker is a self-hosted PostgreSQL queue that runs background jobs on Node.js. It best suits teams whose applications already depend on PostgreSQL and who want queue behavior they can operate themselves. The open-source core is capable and inexpensive, but its runtime requirements and missing dead-letter queue make the deployment choice consequential.

Overview

Graphile Worker stores jobs in PostgreSQL and executes them in Node.js, preventing background work from delaying application responses. It can run as a standalone worker or inside the same Node.js process as an application server. Standalone deployment separates queue processing from request handling, while embedded mode can reduce the number of services to operate.

The project is positioned as a queue that regular organizations can maintain, not as a substitute for dedicated queue infrastructure at Facebook scale. That focus is sensible for database-centric applications, particularly those using PostGraphile or PostgREST, but it leaves teams responsible for the worker runtime, PostgreSQL operations and production scaling.

Key features

Retries and job control

Jobs execute at least once. When a job fails, Graphile Worker retries it automatically with exponential backoff, and custom retry policies allow failure handling to match the workload. At-least-once delivery is useful for recovering from transient failures, but task code must tolerate repeat execution. There is no dead-letter queue, so permanently failing jobs do not have a built-in destination for isolation and later inspection.

Unique job_key values provide task de-duplication, helping prevent repeated requests from creating duplicate work. Batch jobs can append data to an already enqueued job, which is useful when several events can be consolidated before processing rather than handled as separate tasks.

Scheduling and responsiveness

Recurring tasks use crontab-like schedules, with optional backfill when scheduled runs were missed. That combination covers routine maintenance and periodic application work without requiring a separate scheduler. The feature list says execution typically starts in under 3ms through PostgreSQL LISTEN/NOTIFY, a strong fit for applications that need queue dispatch without adding a separate messaging service.

Operations and security

Graphile Worker supports SSL-encrypted PostgreSQL connections and CA certificate configuration. Installation is available through npm, Yarn or pnpm; global installation is not recommended, so projects should keep the package in their application dependency workflow. The current version requires PostgreSQL 12 or newer and Node 22.18 or newer, requirements that may rule it out for older production stacks.

Worker Pro adds crashed-worker recovery and live migration to new Worker versions. Those features address operational continuity, but they are proprietary additions rather than part of the MIT-licensed core. Community assistance is available through Graphile Discord, with professional support contracts for organizations that need a formal support relationship.

Pricing

Graphile Worker costs free and is free, open-source software under the MIT license. It is the natural choice for teams willing to run PostgreSQL and workers themselves, with no per-job charge stated.

Worker Pro Launch Offer costs $25 a month, billed from $25+ per month. It is a sponsorship plan with early access, a limited feature set and a proprietary preset, intended for sponsors rather than as a full-featured general tier.

Worker Pro regular price is $100 a month, billed monthly. It includes the proprietary preset at the stated regular price. Choose it when crashed-worker recovery and live migration justify paying for the Pro feature set; otherwise, the free core provides the primary queue functions.

Platforms

Graphile Worker is available for API, Linux, macOS and Windows environments, with a self-hosted deployment model. Official SDK languages are JavaScript and TypeScript. PostgreSQL 12+ and Node 22.18+ are required for the current version.

Who it's for

This is a strong fit for JavaScript or TypeScript teams already centered on PostgreSQL, especially those using PostGraphile, PostgREST or similar database-first frameworks. It suits organizations that want scheduling, retries and queue state in infrastructure they control and can maintain.

Look elsewhere if you need a hosted queue, exactly-once processing, a dead-letter queue or compatibility with older PostgreSQL or Node releases. Very large installations should also consider the project's stated focus on regular organizations rather than Facebook-scale queue infrastructure.

Pros and cons

• Pros: MIT-licensed core at no cost, PostgreSQL-backed persistence, automatic exponential-backoff retries and configurable retry policies.
• Pros: Crontab-like recurring schedules with optional backfill, de-duplication by unique job key and appendable batch jobs.
• Pros: Standalone or embedded deployment, with SSL and CA certificate support for PostgreSQL connections.
• Cons: Self-hosting leaves teams responsible for PostgreSQL, Node.js and worker operations.
• Cons: At-least-once execution requires idempotent task design, and there is no dead-letter queue for failed work.
• Cons: PostgreSQL 12+ and Node 22.18+ requirements can exclude older environments; advanced recovery and migration features require proprietary Worker Pro plans.

Alternatives

pg-boss is a direct database-oriented alternative: free MIT-licensed software that runs in your own database with no per-job charges.

Faktory fits teams wanting a freemium self-hosted queue with an AGPL open-source edition and optional enterprise packs priced at $99 a month.

IronWorker is the better comparison when API, web and hosted-style deployment options, a free trial and a Basic plan with defined concurrency and runtime quotas matter.

Django Q2 suits Django-oriented teams seeking free MIT-licensed software across Linux, macOS and self-hosted web deployments.

Hangfire is an alternative for .NET environments needing its free LGPL 3.0 Open edition and SQL Server or in-memory storage.

Gearman offers another free, open-source option under the BSD license for API, Linux, macOS, self-hosted and Windows use.

Inngest is preferable when a freemium service with hosted quotas, seats and execution limits is a better fit than operating PostgreSQL-backed workers.

Google Tasks is for personal task lists, subtasks, due dates and notifications on Android, iOS and the web, not application background-job processing.

Browse the Task Queue Software category for more queue options.

Verdict

Choose Graphile Worker if your JavaScript or TypeScript application already relies on PostgreSQL and you want a free, self-hosted queue with scheduling, retries and database-native controls. Its main reason to choose it is the capable MIT-licensed core; its main reason to look elsewhere is the operational burden and lack of a dead-letter queue.