Lurind
Lurind APIv1
POST /v1/queues/{q}/jobsPublish a job to a queue.
GET /v1/queues/{q}/_streamStream jobs to a consumer.
POST /v1/queues/{q}/ack/{id}Acknowledge a completed job.
GET /v1/queues/{q}Queue depth and retry stats.

Message queue & event broker

A small, fast broker for background work.

Lurind moves jobs and events between your services with at-least-once delivery, retries, and a live view of every queue — in a single binary.

Read the documentation →$ lurind start

Capabilities

Durable queues

Jobs are persisted before they're acknowledged, so nothing is lost when a worker restarts.

Retries & delays

Failed jobs back off and retry on a schedule you control, with a dead-letter queue for the rest.

Streaming consumers

Workers subscribe over a long-lived connection and receive jobs the moment they're enqueued.

Lurind Message·At-least-once delivery·Automatic retries·Streaming consumers·REST API

From enqueue to done.

Publish a job over HTTP, consume it from a worker. Lurind handles delivery and retries.

  1. 1Start the broker on any host.
  2. 2Publish jobs to a queue over the API.
  3. 3Consume them from one or more workers.
# start the broker $ lurind start --data ./queue # publish a job $ curl -X POST /v1/queues/email/jobs \ -d '{"to":"a@b.c"}' → queued · id job_8f2a # a worker consumes the stream $ lurind consume email