What it is

Quirrel is an open-source task queueing solution built for serverless applications. It is written in TypeScript, distributed under the MIT license, and lives in the JavaScript and TypeScript ecosystem that surrounds serverless platforms such as Next.js deployments. The project describes itself as the task queueing solution for serverless, and its homepage and documentation sit at quirrel.dev and docs.quirrel.dev. The repository has been public for roughly six years, holds 928 stars and 68 forks, and was most recently pushed in September 2026. A notice in the README states that Quirrel joined Netlify, and the original author documented the acquisition and the move to Netlify in a linked post.

The concrete problem it solves is background work in environments that do not keep a process alive. Serverless functions terminate once a request finishes, so scheduling a job for later, retrying it, or running it on a repeating schedule is not something the runtime provides. Quirrel adds that missing layer: it accepts jobs and delivers them back to the application on a schedule or on demand. The README names delayed jobs, fanout jobs, recurring jobs, and CRON jobs as supported categories. That covers the common cases where an application needs to send a reminder later, broadcast one task to many consumers, or run a job on a fixed cadence without a long-running worker.

Key capabilities

• Delayed jobs, which run at a time chosen when the job is enqueued.
• Fanout jobs, which distribute a single job to multiple recipients.
• Recurring jobs, which repeat on a defined schedule.
• CRON jobs, which follow cron-style scheduling.
• Tailor-made client libraries, exposed through the documented queue API.
• A development UI, described in the Next.js getting-started section of the documentation.
• End-to-end encryption, listed by the README as a privacy property.

Who uses it and how

• Serverless applications on Next.js, covered by a dedicated getting-started path in the documentation.
• Applications that need a reminder flow; the project's own tutorial builds a water-drinking reminder with Next.js and Quirrel.
• Existing applications being retrofitted with queueing, handled through the Getting Started Guide.
• Teams that prefer a managed setup, using the hosted offering at quirrel.dev.
• Teams that prefer to run it themselves, using the on-prem option the README calls easy.

Getting started

The README points to a hosted offering at quirrel.dev and to an easy on-prem option, alongside a tutorial and a Getting Started Guide in the documentation. Integration into an existing application goes through the client libraries and the documented queue API.

When to use it — and when not to

Quirrel is the free, MIT-licensed alternative to a paid queueing service, and it offers both a hosted route and self-hosting, so the choice between them stays open. A self-hoster takes on operating the service, and the README does not detail the backing components, so that burden should be assessed from the documentation before committing. The repository carries 39 open issues and its author has joined Netlify, which is worth weighing for anyone depending on the on-prem path long term.