> For the complete documentation index, see [llms.txt](https://fusionauth.io/docs/llms.txt)

# SLA

FusionAuth Cloud's service-level agreement of instance availability.

Availability of your system is critical; below are some of the steps FusionAuth takes to ensure that FusionAuth Cloud systems are always available:

## All Deployments

*   All components are monitored via external software systems as well as internal metrics gathering systems.
*   The application architecture is not exotic, reducing risk. This is a three tier web application, which is a well understood architecture.
*   Third party security researchers can submit security issues via a bug bounty program.
*   The FusionAuth software and infrastructure is pentested on a regular basis.
*   Major changes, such as FusionAuth upgrades or operating system upgrades, are scripted and rollout timing is controlled by the customer.
*   Modifications to the underlying product are tested extensively, including load testing where appropriate.
*   Automated rulesets provide protection against DDoS.
*   A world class cloud provider's managed services for system components are used where appropriate.
*   Network firewalls are automatically configured on deployment to set up "least privileged" access to each architectural component.

## High Availability (HA) Deployments

*   Each deployment has redundant components. This includes, but is not limited to, the DNS system, load balancer, and the compute nodes running FusionAuth.
*   Each deployment's relational database is set up in a primary/secondary configuration. If the primary becomes unavailable the secondary will "stand up" and the instance will continue to be available. This is also known as "full database replication".
*   Each set of components is run in separate geographic availability zones, geographically separated. This prevents disasters from affecting all components.
*   The FusionAuth engineering team will consult on product implementation and can offer "best practices" advice to further ensure system stability.
*   We size the instance properly for expected traffic, in consultation with the customer.

You can find more information about service level agreements (SLAs) in the [FusionAuth license](https://fusionauth.io/license.md) and [license FAQ](https://fusionauth.io/license-faq.md), including uptime numbers and definitions of downtime.

For all deployments which include backups (HA and Business Cloud), the default backup retention is 3 days.