# Spooler

> A simple, managed message queue

Source: https://rankcert.com/product/spooler
Website: https://spooler.sh
Verification: Unverified
Upvotes: 0
Launch week: unscheduled · Updated: 2026-11-04

## Verified signals

- No signals submitted. This listing is unverified.

## About

Spooler is a durable, fully managed message queue designed for background jobs, webhook delivery, and worker coordination. It offers a simple send/recv API with lease‑based retries, an atomic ack‑and‑send operation, and built‑in state‑machine modeling. Each queue lives in a spool that uses a write‑ahead log and replication for durability. The service is inspired by Go channels but eliminates the need to self‑host or write custom queue logic.

## Spooler as an alternative

People evaluate Spooler against RabbitMQ, AWS SQS, Google Cloud Pub/Sub, Azure Service Bus, Kafka.

## Questions

### Is Spooler self-hosted?

No, the server is closed source; currently only the managed service is available.

### What languages does Spooler support?

It provides a Go library and CLI; other languages can use the HTTP API.

### Does Spooler guarantee message durability?

Yes, messages are written to a write‑ahead log and replicated; operations are considered durable only after replication.

### How do I test Spooler locally?

Use the Docker image at docs.spooler.sh/local; it provides an in‑memory server with the same API.

### What happens if a message is not acknowledged?

The lease expires, and the message is returned to the queue for redelivery, or moved to a failed state after too many retries.

Tags: message queue, background jobs, go, state machine