River review
A self-hosted queue for transactional jobs, scheduling, retries, and multiple language integrations.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
River is an open-source background job system for backend teams building applications with PostgreSQL or SQLite. Its core job processing includes transactional enqueueing, multiple isolated queues, job prioritization, recurring and cron jobs, scheduled jobs, automatic retries with configurable attempts and delays, and unique jobs. The software is self-hosted and includes an optional web interface, making it a fit for teams that want queue processing alongside their application infrastructure rather than a separate queue service. Go is the primary application focus, with integrations for Python, Ruby, and TypeScript ecosystems.
The Open Source plan costs $0 and includes reliable background jobs, an intuitive web UI, multiple queues, periodic jobs, and unique jobs. The Pro plan costs $125 per month and adds workflows, batching, concurrency limits, and email support. Pro also includes all Open Source features, while the Enterprise plan adds email and Slack support plus access to a SOC 2 report. River Pro includes dead-letter queues, workflows, batching, sequences, and operational controls for teams that need more structured job handling. The paid tiers are most relevant when basic queueing is not enough or when commercial support is part of the operating model.
River fits teams working with PostgreSQL, SQLite, or supported database libraries such as pgx, SQLAlchemy, ActiveRecord, Sequel, node-postgres, and Prisma. OpenTelemetry integration supports observability workflows, while the self-hosted model keeps deployment under the team’s control. That control also creates an operational responsibility: teams must run and maintain the queue system and its optional web interface themselves. Choose River when transactional job enqueueing, scheduling, retries, and multi-language database integration matter. Choose another task queue when a managed service or a fully hosted operating model is required.
River pros and cons
- Where it wins
- Transactional enqueueing with configurable retries and delays
- Queues support scheduling, priorities, recurring jobs, and isolation
- Open source with Go, Python, Ruby, and TypeScript integrations
- Where it doesn't
- Self-hosted deployment requires infrastructure and operational ownership
- Workflows, batching, and dead-letter queues require the Pro plan
- Commercial support is limited to Pro and Enterprise plans
River 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