Update:Our Privacy Policy has changed

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 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

Upstash QStash is a serverless message queue and task scheduler that works over HTTP. You publish a message to QStash with an HTTP request or the @upstash/qstash SDK, and QStash delivers it to your endpoint as an HTTP request, retrying failed deliveries up to a configurable limit before moving the message to a dead letter queue. It also runs cron schedules, delays messages, and fans out to multiple endpoints.

A message queue stores work handed off by one part of a system until another part processes it. The producer does not wait for the work to finish, and if the consumer is slow or unavailable the message waits instead of being lost. Queues are the standard way to run background jobs, smooth traffic spikes, and decouple services.

No. QStash pushes messages to your endpoint as HTTP requests, so any serverless function, API route, or server that can handle HTTP is a consumer. There is nothing to poll and no connection to keep open, which is why QStash works on Vercel, Cloudflare Workers, AWS Lambda, Deno Deploy, and similar platforms.

If your endpoint returns an error or times out, QStash retries the delivery with exponential backoff. You can set the number of retries per message. Messages that still fail after the last retry move to a dead letter queue, where you can inspect them and retry them from the console or the API.

Yes. Create a schedule with a CRON expression and a destination URL, and QStash calls that URL on time. This gives you reliable cron on serverless platforms, with the same retries and logs as any other message.

Up to 7 days on the free plan and up to a year on pay as you go. Fixed plans have no maximum delay. You can set a relative delay or an exact delivery time.

Every request QStash sends is signed with your signing keys. The SDKs include a receiver that verifies the signature, so your endpoint can reject anything that did not come from QStash.

The free plan includes 1,000 messages a day. Pay as you go is $1 per 100K messages, with 50 GB of bandwidth free each month and $0.05 per GB after that. Fixed plans start at $180 a month for 1M messages a day. Each delivery attempt counts as one message, so a retry counts as another message. See the pricing page for details.

QStash delivers individual messages and runs schedules. Upstash Workflow is built on QStash and runs multi-step processes, where each step is retried on its own and its result is saved, so the workflow can sleep, wait for events, and pick up where it left off. Use QStash for single jobs and Workflow when the job has several steps.

Publish your first message in minutes

Start on the free tier with 1,000 messages a day. No credit card required.