Reliability Fabric
Provider-flexible delivery with built-in safeguards
Plug your providers, keep routing logic, and rely on Nimbus for retries, backoff, and observability.
Delivery safeguards
Reliability baked in
Bring providers
Swap email/SMS/push without flow rewrites.
Retries & backoff
Exponential backoff, jitter, DLQ support.
Channel fallback
Failover to secondary channels automatically.
Health & logs
Per-tenant health with searchable logs.
Compliance
Consent-respecting delivery and audit trails.
API-first
Consistent payloads, idempotent endpoints.
How it works
Route smart, retry safely
- Define primary/secondary providers per channel.
- Let Reliability Fabric handle retries with backoff and jitter.
- Observe per-tenant health, failures, and DLQs in one pane.
channel: emailprovider: primary-email
Retry policyBackoff
Exponential · max 4 attempts · jitter on.
FallbackSMS secondary
If email fails after 2 tries, switch channel.
Reliability Fabric FAQ
Delivery and routing questions
Can we control retry policy?+
Yes. Configure attempts, backoff, jitter, and DLQ per channel.
Do you support multiple providers?+
Yes. Choose primaries and fallbacks; swap without changing flows.
How do we monitor failures?+
Use per-tenant health, logs, and DLQ exports; send alerts to ops tools.