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

# Business Continuity & Disaster Recovery

> How Artu maintains operational continuity, responds to incidents, and restores service if a failure occurs

Artu is designed so that application failures can be recovered without losing customer data. This page explains the infrastructure model, incident response process, recovery objectives, and backup options that support continuity of operation.

<Info>
  This page complements [Security & Trust](/concepts/security-trust), which
  covers application-level security controls, and [Data Governance](/concepts/data-governance),
  which covers ownership, storage, portability, and retention of customer data.
</Info>

## Infrastructure Model

Artu runs on managed, redundant cloud infrastructure. The application and API tier is stateless — all durable data lives in the managed database and object storage — so application instances can be redeployed or replaced without data loss. The database and object storage inherit the storage-level redundancy and automated backups of our managed cloud providers.

## Incident Detection and Response

Artu continuously monitors the health of the platform, with automated alerting to surface failures quickly. When an incident occurs, our team investigates and works to restore normal service, prioritizing the integrity of your data above all else.

Because the application tier is stateless and your data is continuously backed up, service can typically be restored without data loss. For incidents that materially affect your service, we keep affected customers informed and communicate remediation steps through your support channel.

## Recovery Objectives

| Objective                                                        | Default target               |
| ---------------------------------------------------------------- | ---------------------------- |
| **RTO** (Recovery Time Objective) — time to restore service      | ≤ 24 hours, typically faster |
| **RPO** (Recovery Point Objective) — maximum potential data loss | ≤ 24 hours                   |

With point-in-time recovery configured (see below), the RPO can be reduced to approximately **2 minutes**.

## Backups & Data Retention

<Info>
  Your data is retained for the life of your account — the backup policy below
  is **separate** and does **not** limit how long we store your data.
</Info>

By default, Artu keeps **daily backups covering the most recent 7 days**, allowing us to restore your data to any of those daily points in the event of a disaster. This is a disaster-recovery safeguard, not a retention limit: your live data remains available continuously for as long as your account is active.

If your compliance requirements call for a longer recovery window or finer-grained recovery, we can configure **point-in-time recovery** (restore to within minutes) or **extended daily-backup retention** for your organization. [Contact us](mailto:support@artu.ai) to set this up.

## Continuity Options

The default continuity model is designed for a conservative RTO/RPO target without requiring customers to manage infrastructure themselves. If your organization has stricter continuity requirements, we can discuss enhanced backup retention, point-in-time recovery, or other deployment and recovery options for your organization.

## Questions

For security questionnaires, vendor reviews, disaster-recovery reviews, or continuity requirements, contact [support@artu.ai](mailto:support@artu.ai).