Resilience documentation
How Authonomy keeps authentication working when an IdP degrades.
Architecture, failover behavior, operational envelope, and reference. Written for an identity or platform engineer evaluating the design against an enterprise deployment.
Start here
What is Resilience?
The availability layer that keeps authentication working when a provider degrades.
Continuity vs. backup
The distinction that decides whether this is the right category of product for the requirement.
Architecture at a glance
The components of an Authonomy instance and the two axes a deployment configures.
Browse by section
Introduction
The shape of the problem, the shape of the solution, and the distinction that decides whether you are evaluating the right thing.
Start here →Getting Started
For a reader who has decided to evaluate. Pick a failover shape, understand the drift window, choose a deployment placement.
Start evaluating →How it works
Failover behavior between identity providers and into the native floor. Site-deployed instances. Reconciliation and the drift-window contract.
Read the mechanism →Operations
Health monitoring, audit continuity across the failover boundary, and the security posture of the deployment.
Read the operational surface →Reference
Glossary, scope boundary, and the operational envelope as a constraint list with the levers each admits.
Look it up →