Reliability
Reliability & SLA
Fidacy is built for card-network volume, stateless and horizontally scalable, with the audit and trust guarantees intact. The numbers below are targets, not contractual guarantees. A contractual SLA is available in an enterprise agreement.
Uptime targets
We operate to the following availability targets. Because Fidacy is stateless and scales out, capacity is added by adding instances, and the fail-safe invariant means a fault degrades a decision to review rather than failing open.
| Tier | Availability target |
|---|---|
| Standard | 99.9% target |
| Enterprise | 99.95% target (contractual SLA available) |
These are operating targets for planning. They become a binding commitment only when written into an enterprise agreement. Nothing on this page is a guarantee.
How reliability is engineered
- ·Stateless & horizontal, every instance is identical and the verdict runs inside one tenant-scoped transaction; add instances to add capacity.
- ·Heavy work off the hot path, audit chaining, reasoning, and webhook delivery are decoupled, so a slow downstream can't slow a decision.
- ·Fail-safe, any error, timeout, or fault degrades to
review, never to a silent approval.
Incident communications
- ·During an incident, enterprise customers are notified through the agreed channel with impact, scope, and mitigation status.
- ·Material incidents receive a post-incident summary describing root cause and corrective actions.
- ·Security-relevant incidents follow the responsible-disclosure and notification terms in the enterprise agreement and DPA.
Status page
A public status page at status.fidacy.com is planned. Until it is live, subscribe to status and incident notifications through your account contact or sales@fidacy.com.