Serverless messaging and scheduling over HTTP
Upstash QStash is a message queue and task scheduler for serverless apps. Publish a message with one HTTP request and QStash delivers it to your endpoint, with retries, delays, cron schedules, and fan-out built in. No workers to run, no connections to keep open.
Why Upstash QStash
A message queue built for serverless functions and the HTTP endpoints they expose.
HTTP native
Publish with a single HTTP request and receive messages as plain HTTP calls. No consumers, workers, or TCP connections to manage.
Automatic retries
Failed deliveries retry with exponential backoff. Messages that still fail land in a dead letter queue you can inspect and replay.
Cron schedules
Run recurring jobs with standard CRON syntax. QStash calls your endpoint on time, even from platforms with no cron of their own.
Delayed delivery
Deliver a message after a delay or at an exact time, up to a year ahead on pay as you go.
Queues
Deliver messages one at a time in FIFO order with queues, so downstream services see a steady stream.
Flow control
Cap the rate and parallelism of calls per key to stay inside third-party API limits without writing a rate limiter.
Fan-out
Publish once to a URL group and QStash delivers to every endpoint in it, each with its own retries.
Pay per message
Start free with 1,000 messages a day. Pay as you go is $1 per 100K messages with no monthly base fee.
Send your first message
Publish, schedule, and queue messages with the @upstash/qstash and qstash SDKs, or call the REST API from any language.
import { Client } from "@upstash/qstash";
const client = new Client({ token: "<QSTASH_TOKEN>" });
await client.schedules.create({
destination: "https://example.com",
cron: "* * * * *",
});What can you build with QStash?
Common messaging and scheduling use cases, with a guide to build each one.
Background jobs
Move slow work like emails, image processing, and report generation out of the request and into a retried job.
Cron jobs
Run recurring tasks on Vercel, Cloudflare Workers, or any serverless platform with a CRON expression.
Periodic data updates
Refresh caches, sync third-party data, and rebuild aggregates on a schedule.
Fan-out to many services
Publish one event and deliver it to every subscribed endpoint, each retried on its own.
Rate-limited API calls
Throttle calls to LLM providers and other third-party APIs with per-key rate and parallelism limits.
Reliable webhooks
Accept incoming webhooks fast and process them asynchronously with retries and a dead letter queue.
What is a message queue?
A buffer between the code that asks for work and the code that does it.
A message queue lets one part of a system hand off work to another without waiting for it to finish. The producer publishes a message, the queue stores it durably, and a consumer processes it when it can. If the consumer is slow or down, the message waits instead of being lost.
Traditional queues assume long-running consumers that hold a connection open and poll for messages. Serverless functions do not work that way: they start on a request, run briefly, and stop. That mismatch is why background jobs and cron are awkward on platforms like Vercel and Cloudflare Workers.
Upstash QStash flips the model. Instead of your code pulling messages, QStash pushes each one to your endpoint as an HTTP request and retries failed deliveries, moving any that still fail to a dead letter queue. Anything that can serve HTTP can be a consumer, and every request is signed so your endpoint can verify it came from QStash.
Frequently asked questions
Publish your first message in minutes
Start on the free tier with 1,000 messages a day. No credit card required.