Alternatives

QStash alternatives for scheduled and retried HTTP delivery

The strongest QStash alternatives are Hooksbase when you need signature verification on ingest, payload persistence, and replay rather than a queue that posts to URLs, Inngest or Trigger.dev when the real requirement is durable multi-step execution, and Zeplo when you want the smallest possible retry layer — though QStash remains the better fit when you need topic fan-out.

Pricing and capability claims verified as of 2026-08 from public pricing pages and documentation. Hooksbase is one of the options below — it is our product, and its limitations are listed alongside everyone else's.

How to compare QStash alternatives

Which channels can start an event

Most options here accept HTTP and nothing else. If any part of your workload arrives by email, through a form, or on a schedule, an HTTP-only tool means running separate infrastructure for each of those and reconciling the results.

What happens after the last retry

Every option retries. The difference is what exists when retries are exhausted — a dead-letter path you can inspect and re-drive, or a log line. Ask this before comparing retry counts, because the counts matter far less than the floor underneath them.

Whether a replay is the same event

Replay means two different things. Re-running against current configuration produces something that resembles the original; re-sending a persisted snapshot reproduces it. When you are replaying to investigate a failure, only the second one tells you anything.

How failure affects the bill

Per-message pricing usually counts each delivery attempt, so a destination having a bad day costs more the worse it behaves. Flat tiers move that risk to the vendor. Check this against your own retry profile rather than your happy-path volume.

What is QStash?

QStash is a serverless message queue from Upstash that speaks HTTP. You publish a message to a QStash endpoint and it handles scheduling, one-off delays, retries, topic fan-out to multiple subscribers, and a dead-letter path, with no queue infrastructure of your own to run.

QStash key features

• HTTP publish with retries and a dead-letter path
• Recurring cron schedules and arbitrary one-off delays
• Topic fan-out to many subscribed endpoints
• Message deduplication
• Native integration with the Vercel and Cloudflare ecosystems

QStash advantages

• Scales to zero, which suits bursty and low-volume workloads
• Topic fan-out, which most alternatives in this set do not offer
• A URL-based API any HTTP client can call, with no SDK required
• Sits alongside Upstash Redis and Kafka if you already use them

QStash disadvantages

• Every delivery attempt is billed as a message, so retries cost more the worse a destination behaves
• No payload persistence, replay from stored payload, or delivery history interface
• No signature verification on ingest and no outbound signing
• The free tier caps at 1,000 messages a day

QStash alternatives

Best for multi-channel ingest feeding an AI agent: Hooksbase

Our product

Event infrastructure for AI agents. Accepts events over HTTP, inbound email, HTML form post, and scheduled cron, verifies provider signatures on the way in, routes and transforms them, and delivers to HTTP or typed cloud destinations with retries, ordering, signing, deterministic replay, and a dead-letter path.

Where it is strong: Four ingest channels in one project rather than HTTP alone, provider-verified inbound for Stripe, GitHub, Clerk, Slack, and Resend, typed outbound to SQS, EventBridge, Pub/Sub, and S3-compatible storage from Pro, and replay that reads persisted snapshots so a replay re-sends what was originally dispatched.
Where it falls short: It is not an execution engine — there is no durable multi-step workflow, and no topic fan-out to many subscribers, since routing selects one destination per delivery. It is hosted-only with no self-hosted build, and it is a young product without the enterprise compliance surface Svix carries.
Pricing: Free at 5,000 deliveries a month with no card. Starter $25/mo, Pro $79/mo, Business, and Enterprise. Flat tiers — retries are not billed as additional messages.

Best for durable multi-step workflows on your own compute: Inngest

A durable execution engine. You write a workflow as steps in your own code and Inngest runs it so state survives failure — a run that dies partway resumes from the last completed step rather than starting over.

Where it is strong: A genuinely strong durable workflow model with step-level retry rather than full re-run, excellent TypeScript DX, concurrency and throttling controls, and it runs on compute you already have.
Where it falls short: It is not an ingest or delivery network. HTTP webhooks trigger it, but there are no email, form, or scheduled ingest channels, no typed outbound to SQS or EventBridge, no outbound signing, and its replay is execution retry rather than deterministic replay from a stored payload.
Pricing: Hobby free at 50,000 executions a month with 5 concurrent, Pro from $99/mo with 1M executions and pay-as-you-go to 20M, Enterprise custom.

Hooksbase vs Inngest, head to head

Best for long-running AI agent tasks with no timeout ceiling: Trigger.dev

A managed durable task engine. You write tasks as ordinary code in your repository and Trigger.dev runs them in isolated containers with no timeout limit, retrying and resuming across failures.

Where it is strong: No task timeout, which matters when an agent run takes hours, plus managed elastic compute, strong agent primitives including human-in-the-loop and realtime progress back to your frontend, and an open-source build.
Where it falls short: It executes work rather than moving events: no ingest channels beyond HTTP triggers, no outbound signing or idempotency, no typed cloud destinations, and no deterministic replay from a stored payload. Stacked base, per-run, and per-second pricing is harder to forecast than a flat tier.
Pricing: Free with $5 of monthly credits and 20 concurrent runs, Hobby $10/mo, Pro $50/mo with 200+ concurrent, Enterprise custom. Per-second compute and a per-run invocation charge stack on top of the plan.

Hooksbase vs Trigger.dev, head to head

Best for the smallest possible retry layer: Zeplo

An HTTP request queuing service with a deliberately minimal surface — prefix a URL with theirs and get automatic retries, scheduling, and fan-out with no SDK to install.

Where it is strong: Almost no friction to adopt, and flat pricing rather than per-message metering.
Where it falls short: The feature surface is narrow by design: no delivery history, no dead-letter path, no payload persistence, no signature verification, and no typed outbound. Teams tend to outgrow it as soon as they need to answer what happened to a specific event.
Pricing: A limited free tier, with paid plans from $39/mo at flat pricing.

Best when the requirements are genuinely narrow and stay that way: Building it yourself

A queue, a worker, and a retry loop on infrastructure you already run — Cloudflare Queues, SQS with a Lambda, or a Postgres-backed job table.

Where it is strong: Complete control, no per-event cost, and nothing new in the vendor stack. For one provider and one consumer with no compliance requirement, this is often the correct answer.
Where it falls short: The work is not the queue, it is everything around it: signature verification per provider, idempotency, a retry budget, a dead-letter path, payload persistence, replay, and delivery history. Each is small and none is interesting, and together they become a service someone has to own.
Pricing: Infrastructure cost only, plus the engineering time to build and operate it.

Overview of QStash alternatives

Option	Best for	Pricing
Hooksbase	multi-channel ingest feeding an AI agent	Free at 5,000 deliveries a month with no card. Starter $25/mo, Pro $79/mo, Business, and Enterprise. Flat tiers — retries are not billed as additional messages.
Inngest	durable multi-step workflows on your own compute	Hobby free at 50,000 executions a month with 5 concurrent, Pro from $99/mo with 1M executions and pay-as-you-go to 20M, Enterprise custom.
Trigger.dev	long-running AI agent tasks with no timeout ceiling	Free with $5 of monthly credits and 20 concurrent runs, Hobby $10/mo, Pro $50/mo with 200+ concurrent, Enterprise custom. Per-second compute and a per-run invocation charge stack on top of the plan.
Zeplo	the smallest possible retry layer	A limited free tier, with paid plans from $39/mo at flat pricing.
Building it yourself	the requirements are genuinely narrow and stay that way	Infrastructure cost only, plus the engineering time to build and operate it.

See it on your own events

The Hooksbase free plan covers 5,000 deliveries a month with no card. Point one event source at it and compare the delivery history against whatever you are evaluating.

Start free See the four ingest channels

Frequently asked questions

QStash alternatives, answered.

What is the best QStash alternative?

It depends what you are using QStash for. As a webhook delivery layer, Hooksbase adds signature verification on ingest, payload persistence, replay, and a delivery history interface that QStash does not have. As a workflow runner, Inngest and Trigger.dev do durable multi-step execution properly. As a plain retry layer, Zeplo is smaller and flat-priced.

Does QStash charge for retries?

Yes. Every delivery attempt counts as a message, including each retry, so the cost of a flaky destination scales with how badly it is failing. This is the most common reason teams re-examine QStash, and it is worth modelling against your real retry profile rather than your successful-delivery volume.

What does QStash not do?

It does not verify inbound signatures, persist payloads, replay a past message from storage, or show you delivery history. It accepts HTTP only, with no email, form, or provider-verified ingest. It is a queue that posts to URLs, which is what it is designed to be — the gap only matters if you were expecting a gateway.

What does QStash do that Hooksbase does not?

Topic fan-out. One QStash publish can reach many subscribed endpoints, whereas Hooksbase routing selects exactly one destination per delivery. If fan-out is the requirement, QStash is the right tool and Hooksbase is not.