> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Business Continuity

Beyond preventing incidents, we prepare for recovery. Continuity combines backups, plans with clear recovery objectives, and exercises that test whether the team can execute what is written.

## Pillars

<CardGroup cols={3}>
  <Card title="Backups">
    Critical systems have backups. We periodically validate restore capability — because a backup without a tested restore is only a hypothesis.
  </Card>

  <Card title="Recovery objectives">
    Continuity and disaster plans define how long we accept to return to operation and how much recent data loss is tolerable for essential components, guiding priorities in a crisis.
  </Card>

  <Card title="Exercises">
    Periodic simulations and tests expose process gaps, forgotten dependencies, and role ambiguity — and produce concrete plan improvements.
  </Card>
</CardGroup>

## Service availability

We pursue high availability, with commercial targets of up to **99.9%** depending on the Enterprise contractual offer. Capacity and usage are monitored to absorb demand spikes without prolonged degradation.

## External dependencies

Cloud, payments, and AI model providers are treated as critical links in the chain. We assess risk, contracts, and security assurances from those partners — because Tess resilience also depends on them.

<Note>
  Continuity does not eliminate every outage; it reduces impact duration and makes recovery predictable and communicable.
</Note>

## Related

* [Infrastructure](/Infrastructure)
* [Incident Response](/Incident-Response)
* [Responsibilities](/Responsibilities)