Skip to main content
Flare · Background jobs as a service

Background jobs for teams who'd rather operate their app than their queue.

Enqueue jobs from any service in any language — .NET, TypeScript, Python, Go, Java, PHP, or Ruby — and let Zeridion handle queueing, retries, recurring schedules, and dead letters. Your workers pull and execute. No queue to babysit.

Start in 5 minutes →Browse the API
7 official SDKs
.NET, TypeScript, Python, Go, Java, PHP, Ruby
At-least-once
Idempotency-Key replays the original response (Idempotent-Replay: true)
0 ops
No queue infra to run or babysit

What is Flare?​

Flare runs the durable background-job plumbing so you don't have to:

  • Email fan-out · Scheduled work · Retries with backoff · Per-project isolation

Flare is a managed background-jobs platform with official SDKs for .NET, TypeScript, Python, Go, Java, PHP, and Ruby. Install the SDK for your language, point it at the Flare API, and enqueue jobs from any service. The .NET SDK ships a built-in in-process worker (IJob<T> handlers registered via AddZeridionFlare); the other SDKs are REST clients you call from your own worker process or scheduler. Zeridion durably stores every job and dispatches it to exactly one of your workers, with at-least-once delivery and idempotency-key support.

You bring the worker process. We handle the queue, retries, dead-letters, recurring schedules, per-project rate limits, and observability.

How it fits together​

Your app calls the REST API to enqueue. Flare durably stores the job, fans out recurring schedules, applies retries with exponential backoff, and emits signed webhooks on every state change. Your worker poll-and-claim leases jobs concurrently, heartbeats while running, and acks with the result. The platform handles the rest.

Explore the docs​

→
Quickstart
Install the SDK, enqueue your first job, and see it run in a worker — five minutes total.
Get started →
⚙
SDK reference
IJob, IJobClient, JobContext, retry policies, and the option precedence rules.
Read SDK docs →
{ }
API reference
Every endpoint under /flare/v1 with parameters, examples, and response shapes.
Open reference →
⌘
Guides
Retries, idempotency, recurring jobs, queues, progress reporting, and monitoring.
View guides →

How Flare fits together​

Three boxes: your app enqueues via the SDK, Zeridion durably stores and dispatches each job, and your workers pull and execute it. Retries, recurring schedules, and per-project rate limits are handled for you.

High-level topology
Your application
SDK in .NET / TS / Python / Go / Java / PHP / Ruby
Your worker process
.NET in-process handler · or REST poll from any SDK
→
Flare API
api.zeridion.com/flare/v1
Recurring schedules
cron · timezone-aware
→
Retries & dead-letter
exponential backoff · DLQ on exhaustion
Per-project rate limits
quotas enforced server-side

When to use Flare​

  • Email and webhook fan-out. Anything you'd Task.Run and regret.
  • Scheduled work. Cron expressions with timezone awareness.
  • Retry-with-backoff workflows. Exponential backoff is built in; dead-letter is automatic at attempt exhaustion.
  • Per-project isolation. Every job, schedule, and API key is scoped to a Project. Rate limits and quotas are enforced per Project.