Real-time visibility, alerts, and insights for your background jobs, powered by your existing database.
Sign in or register to get started
Install the SDK, register DurableStack in your host, configure storage, and start at least one worker process. Once the runtime is connected, the platform can ingest execution events and begin building an operational history.
Start with the .NET documentation, then follow the getting-started guide to verify your first runs.
Scheduling is the easy part. Operating distributed background workloads in production is where most teams lose time.
DurableStack is built to close that gap by turning runtime events into actionable state: attempts, retries, latency, worker heartbeats, failure samples, and alert transitions. It gives developers a system-level view of job behavior without bolting together multiple tools.
The dashboard is designed for investigation, not just status reporting. You can inspect run timelines, retry behavior, and worker availability in real time, then scope every view by organization, project, and tenant to isolate impact quickly.
When a job fails, failure analysis views surface the execution context you need to reproduce and fix issues without digging through unrelated logs first.
Alert policies let you define operational thresholds around error rates, retry saturation, worker health, and other runtime signals. When a rule opens an incident, DurableStack carries forward context about scope and severity so responders can triage immediately.
This workflow moves teams from passive monitoring to explicit incident handling with fewer false starts.
DurableStack does not require replacing your current observability tooling. Execution events can be exported through OpenTelemetry and event sinks so traces, metrics, and job-level outcomes stay correlated in your existing pipeline.
You can adopt the platform incrementally while preserving established dashboards, alert destinations, and incident workflows.
Use this sequence to validate the full loop in a development environment: