Fivexer

The Twilio TaskRouter alternative that runs on your own Redis

TaskRouter is a hosted routing API you pay per task, forever. This is a self-hosted, Redis-backed matching engine with the same job — skill/tag routing, priority, worker capacity — plus hard-veto rules and a learning layer that retunes itself from real outcomes, with your assignment data never leaving your infrastructure.

Runs on your own Redis, nothing leaves your infrastructure · Open source (MIT)

assignment-user-matcher vs Twilio TaskRouter

Fit as a routing engine, not overall product quality — TaskRouter is excellent at what it is built for, which is Twilio Flex and telephony-first contact centers.

Capabilityassignment-user-matcherthis libraryTwilio TaskRouterTwilio TaskRouter alternative
Data sovereignty
Yes: Runs in your network — EU data residency by construction; nothing leaves your Redis
No: Tasks and worker data are processed in Twilio's cloud
Self-hosted deployment
Yes: Open source (MIT), plain npm library — runs in your own infrastructure
No: Hosted only — Twilio's cloud, not yours
Hard veto guarantees
Yes: Zero-weight = absolute; the learning layer cannot override it
Partial: Expressible in workflow rules you write and maintain yourself
Explainable decisions
Yes: Decision traces built in — every match records who won, who was vetoed, and why
Partial: Task lifecycle events log what happened, not why a worker was chosen
Fair work distribution
Yes: Built-in fairness modes — best-match, balanced, or spread-work — with rolling grant caps
Partial: Longest-idle ordering within a queue; anything beyond it is yours to build
Self-tuning routing weights
Yes: Learning layer built in, learns from real outcomes
No: Static workflow rules; retuning is manual
Geo-distance matching
Yes: First-class, combined with skills and priority
Partial: Custom worker attributes plus expressions
Any assignment domain
Yes: Tickets, cases, field work, AI agents as workers — tags are generic
Partial: Contact-center shaped; other domains fight the grain
Pricing model
Yes: Free (MIT) + your own Redis hosting; not metered per task
No: $0.06/task after the first 100 free, every month, forever
Managed service & SLA
No: Self-managed — Fivexer offers implementation and support
Yes: Twilio's platform SLA
Telephony & omnichannel
No: Routing engine only, by design
Yes: Native voice, SMS, chat

Reflects Twilio's published docs and pricing as of July 2026. TaskRouter is excellent at what it's built for — this page is about fit as a routing engine, not overall product quality.

What this costs at 50k assignments/mo, 25 agents

Published list prices against a representative snapshot. The engine is MIT-licensed and free — its whole bill is the Redis it runs on.

assignment-user-matcherMIT-licensed, no license fee — this is the all-in price
$0.70/mo

runs on the Redis instance you already operate — $0.70/mo estimated marginal load, not a list price

Twilio TaskRouter
$2,994/mo

100 free + 49,900 × $0.06 per month

List prices as of July 2026; excludes negotiated discounts, HA replicas, and egress. Play with your own volume and team size on the full interactive comparison →

Where TaskRouter is still the better fit

If you're already on Twilio Flex, or you need native voice/SMS/chat with a platform SLA and don't want to run any infrastructure yourself, TaskRouter's tight integration with the rest of Twilio's stack is a real advantage this engine doesn't try to match — it's a routing engine, not a telephony platform.

Right people. Right work. Right time.

Free during launch — no card, no sales call — a working API key about two minutes from now. And if you ever want out, the engine underneath is open-source (MIT): self-host it and your rules and traces leave with you.

Enterprise, BYO Redis, or just questions? Talk to us.