Graphile Worker

Graphile Worker is a self-hosted PostgreSQL queue that runs background tasks through Node.js. It suits teams already operating PostgreSQL and wanting queue behavior close to their application data. The open-source core is capable and economical, but running the database and workers remains your responsibility.

Overview

Jobs are stored in PostgreSQL and executed by Node.js, keeping slow or failure-prone work out of request responses. You can run workers as standalone processes or embed them in the same Node.js process as an application server. Standalone deployment separates queue load from web traffic; embedding can reduce the number of moving parts, but it also couples worker and application lifecycles.

Graphile positions the project as a queue that regular organizations can maintain, not infrastructure intended to replace dedicated queues at Facebook scale. That makes its database-first design sensible for small and midsize teams, while unusually large workloads may warrant a purpose-built queue platform.

Key features

Retries and job control

Jobs execute at least once, and failures receive automatic retries with exponential backoff. Custom retry policies let you tune recovery to the workload, but at-least-once execution requires idempotent task design: a retried job can run again. There is no dead-letter queue, so teams that need failed work isolated for later inspection or replay will need another mechanism.

A unique job_key can deduplicate tasks, preventing repeated requests from creating unnecessary duplicate work. Batch jobs can append data to an already enqueued job, which is useful when many related events should be consolidated before processing.

Scheduling and speed

Recurring tasks use crontab-like schedules, with optional backfill when scheduled runs were missed. The feature set says execution typically begins in under 3ms through PostgreSQL LISTEN/NOTIFY, making it appropriate for responsive background actions when the database is nearby and healthy. That figure is a stated typical behavior, not a guarantee for every deployment.

Database and operations

Graphile Worker pairs naturally with PostGraphile, PostgREST and other database-centric frameworks. PostgreSQL connections can use SSL encryption with CA certificate configuration. Installation is available through npm, Yarn or pnpm; global installation is discouraged. The current requirements are PostgreSQL 12 or newer and Node 22.18 or newer, so older estates may face an upgrade before adoption.

Community assistance is available through Graphile Discord, while professional support contracts provide a commercial route. Worker Pro adds crashed-worker recovery and live migration to new Worker versions, capabilities absent from the free core.

Pricing

Graphile Worker: free. This is free and open-source software under the MIT license, with self-hosted operation and no per-job charge stated. It is the practical choice for teams able to run PostgreSQL and Node.js themselves and willing to handle operational recovery.

Worker Pro Launch Offer: $25 a month. The sponsorship offer provides early access, a limited feature set and a proprietary preset for sponsors. It is aimed at organizations that want to support the project and access Pro capabilities before the regular price.

Worker Pro regular price: $100 a month. The stated regular price covers the proprietary preset. Pro is the relevant tier for teams that specifically need crashed-worker recovery or live migration; the core package does not include those features. No seat, execution or quota limits are stated for these plans.

Platforms

Graphile Worker supports API use and self-hosted deployment on Linux, macOS and Windows. Its official SDK languages are JavaScript and TypeScript. The infrastructure is yours to deploy, including the PostgreSQL service and worker processes.

Who it's for

Choose Graphile Worker when PostgreSQL is already the system of record, your application runs on Node.js, and you prefer an MIT-licensed queue you can embed or operate separately. It is particularly well suited to scheduled maintenance, notifications and other background jobs that benefit from database transactions, deduplication and retry control.

Look elsewhere if you require a hosted service, a built-in dead-letter queue, or support for runtimes outside the JavaScript and TypeScript ecosystem. Teams unwilling to maintain PostgreSQL connectivity and worker processes will also find the self-hosted model demanding.

Pros and cons

• Pro: PostgreSQL storage keeps queue state alongside application data and fits database-centric frameworks.
• Pro: Exponential retries, custom policies, deduplication and batch appending cover common reliability and throughput patterns.
• Pro: Crontab-like schedules, optional backfill and typically sub-3ms starts support responsive recurring work.
• Pro: The MIT-licensed core costs $0.00 and can run embedded or standalone.
• Con: At-least-once delivery and no dead-letter queue place idempotency and failed-job handling on your team.
• Con: PostgreSQL 12+ and Node 22.18+ requirements can exclude older environments.
• Con: Hosted deployment is not part of the model; operations, upgrades and recovery are yours unless you buy Worker Pro features.

Alternatives

Browse the broader Task Queue Software category when you want to compare queue designs beyond a PostgreSQL-first worker.

IronWorker is a better fit when you want a freemium public-cluster option with one concurrency, five hours per month, 512 MB RAM and 50 scheduled tasks on its Basic plan.

Django Q2 suits Python and Django teams seeking free MIT-licensed software rather than a Node.js worker.

Faktory is worth choosing when an AGPL open-source core and optional $99-per-month Enterprise packs for additional connections match your deployment.

Gearman is a free BSD-licensed alternative for teams wanting a general distributed job system across Linux and Windows.

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

Hangfire fits .NET environments that prefer its free LGPL core and SQL Server or in-memory storage options.

Inngest is the stronger choice when a freemium service with hosted execution quotas, seats and trace history is preferable to self-hosting.

pg-boss is a close alternative for teams wanting MIT-licensed, PostgreSQL-backed jobs running in their own database without per-job charges.

Verdict

Graphile Worker is a strong recommendation for Node.js teams already committed to PostgreSQL that want an inexpensive, maintainable queue with retries, scheduling and database-aware controls. Its main reason to choose it is the tight PostgreSQL integration and flexible deployment model. Look elsewhere when you need hosted operations, a dead-letter queue, or recovery and migration features without upgrading to Worker Pro.