Question 1

Do I have to host workers myself?

Accepted Answer

You host the job code, we host everything else. In .NET, the Zeridion.Flare NuGet package registers a hosted service inside your existing ASP.NET Core app that polls our API for work — no separate worker process needed. In TypeScript, Python, Go, Java, PHP, and Ruby, the SDK is a REST client you call from your existing service or a small worker process. The data plane (queue, scheduler, retries, dashboard) is fully managed in all cases.

Question 2

Which .NET runtime versions are supported?

Accepted Answer

The SDK multi-targets net10.0 and netstandard2.1, so it runs on any project that supports .NET Standard 2.1 or later, including .NET 6, 7, 8, 9, and 10 on Windows, Linux, macOS, and ARM. ASP.NET Core is recommended but not required.

Question 3

How is this different from running a job library in-process?

Accepted Answer

An in-process library couples job durability to your web tier's deployment, scale, and storage. Flare provides a managed queue and dashboard that survive deploys and process restarts, exponential-backoff retries with dead-lettering on by default, and a real-time UI for inspecting payloads and failures, without standing up Redis, Postgres, or a worker host of your own.

Question 4

What happens when I hit my plan's daily limit?

Accepted Answer

New POST requests to create jobs return HTTP 429 with error code daily_quota_exceeded and X-Quota-* response headers showing your limit, current usage, and the UTC midnight reset. Jobs already in the queue continue to run. There is no overage billing surprise.

Question 5

Is there a free tier, and does it stay free?

Accepted Answer

Yes — 1,000 jobs per day, one project, hosted dashboard, $0 per month, no credit card. The free tier is part of the published pricing model, not a trial; it does not expire and does not auto-convert.

Question 6

Can I run Flare offline or on-premises?

Accepted Answer

Not today. Flare is a hosted service; the API and dashboard run on our infrastructure. If a fully self-hosted deployment is a hard procurement requirement, contact us — we cannot promise it on the roadmap.

Question 7

How is my data stored — what about GDPR?

Accepted Answer

Job payloads and metadata are stored in managed Postgres on Azure with TLS in transit and encryption at rest; transient queue state lives in managed Redis. A DPA referencing the EU SCCs is available on request. Region pinning beyond the default is in progress.

Question 8

What if I want to leave?

Accepted Answer

All seven SDKs (.NET on NuGet, TypeScript on npm, Python on PyPI, Go on pkg.go.dev, Java on Maven Central, PHP on Packagist, Ruby on RubyGems) are open packages, and every operation has a documented REST endpoint, so you are never blocked on us to read your data or wire a different client. Job payloads are your JSON — export from the dashboard or the API. Cancel any time.

Background jobs for every stack, fully managed.

From dotnet add to first job

Automatic retries

Progress reporting

Recurring jobs

Queue visibility

Every entry point has one job

API

Dashboard

Docs

Ship background work in minutes, not sprints.