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

Oban review

Freemium#13 of 36 in Task Queue Software

A PostgreSQL-backed queue for durable jobs, with advanced workflows and rate limiting in Pro.

8.0/10Editor score
Oban8.0 Visit Oban

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Oban is a background job framework for Elixir and Python applications that stores jobs in PostgreSQL. It is designed for teams building production systems that need durable asynchronous processing, including independent queues, concurrency controls, retries, scheduled jobs, recurring cron jobs, cancellation, snoozing, retention, and pruning. Oban can run as a standalone worker process or be embedded within an application, making it a fit for Elixir teams and Python applications using PostgreSQL-related integrations such as SQLAlchemy and psycopg.

The Open Source edition is free and includes reliable background jobs, scheduled jobs and Cron, and community support. Pro is available at $150 per month with monthly billing or $135 per month with annual billing. Both Pro options add durable workflows, global and rate limiting, queue partitioning, bulk operations, one application, and unlimited nodes. Enterprise adds application bundles, Elixir and Python included, multi-year licenses, payment via invoice or purchase order, and enterprise support availability. The published plans make Pro relevant when workflow orchestration or rate controls are central requirements, while the free edition covers core queue processing.

Oban’s strongest fit is a self-hosted system where PostgreSQL is already part of the application architecture and durable job state matters. Transactional insertion, configurable retry behavior, independent queues, and scheduled execution give teams control over how background work is stored and processed. Teams needing advanced workflow and rate-limiting features should consider Pro, while teams that only need core background jobs can start with Open Source. It is less suitable for organizations seeking a managed deployment rather than a self-hosted worker and database setup.

Oban pros and cons

  • Where it wins
    • PostgreSQL-backed durable storage with transactional job insertion
    • Independent queues, concurrency limits, retries, and configurable backoff
    • Scheduling, cancellation, snoozing, retention, and pruning included
  • Where it doesn't
    • Self-hosted deployment requires application and PostgreSQL infrastructure
    • Durable workflows and rate limiting require a Pro plan
    • Open Source support is community-based

Oban 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