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

# Fault Tolerance

> Security without compromising on UX or DevEx through multi-vendor key redundancy and automated failover systems

Grid Accounts deliver enterprise-grade security without compromising on user experience or developer experience. Built on the fully open-source Squads Protocol, Grid provides a unique non-custodial architecture that virtually eliminates vendor lock-in while maintaining the simplicity and reliability that modern applications require.

## Fault Tolerance and Redundancy

Grid's non-custodial architecture provides unprecedented fault tolerance and redundancy:

<CardGroup cols={2}>
  <Card title="Open Source Foundation" icon="git-branch">
    Built on Squads Protocol, fully open source and auditable. No proprietary
    custody mechanisms or hidden dependencies.
  </Card>

  <Card title="Easy Migration" icon="rotate-ccw">
    Simply prompt users to update signing keys on their accounts. No manual
    backups.
  </Card>

  <Card title="Implementation Flexibility" icon="settings">
    You can implement Squads Protocol directly without Grid APIs if needed in
    the future.
  </Card>

  <Card title="True Ownership" icon="key">
    Users control their accounts directly through the blockchain. Grid provides
    tooling, not custody.
  </Card>
</CardGroup>

## How Grid Works: Automated Multi-KMS Architecture

<Note>
  **Protection Against Catastrophic Scenarios** When you deploy a Grid Account,
  keys are automatically created with your user's email address and deployed
  across multiple KMS providers. This protects against vendor business failures,
  security breaches, key loss, or extended service unavailability.
</Note>

<Steps>
  <Step title="Automatic Multi-KMS Deployment">
    Every Grid account is deployed with 2 signer keys (1 of 2 threshold) across
    different KMS providers using the user's email as the identifier.
  </Step>

  <Step title="Vendor Risk Mitigation">
    If a KMS provider goes out of business, loses keys, or becomes permanently
    unavailable, the backup key with another provider maintains full account
    access.
  </Step>

  <Step title="Seamless Key Rotation">
    Any compromised or lost key can be rotated without changing the user's
    wallet address, since keys are purely for signing operations.
  </Step>

  <Step title="Business Continuity">
    Your application remains operational even during extended vendor outages or
    permanent provider changes.
  </Step>
</Steps>

## The Key Management Challenge

<Info>
  **Building Complete Solutions** Key management services provide excellent
  security for individual keys, but building fault-tolerant applications
  requires additional layers of redundancy and user ownership. Grid complements
  KMS providers by adding the missing pieces for complete custody solutions.
</Info>

When building robust applications, teams often need to address critical risk scenarios:

**Key Challenges:**

* **Vendor business failure**: What happens if a KMS provider goes out of business?
* **Permanent key loss**: How to maintain access if keys are irretrievably lost?
* **Security breaches**: Quick key rotation to mitigate risks during provider compromises
* **Extended outages**: Business continuity during prolonged service unavailability
* **Migration constraints**: Avoiding architectural lock-in that limits future flexibility

## How Grid Completes the Solution

<Note>
  **Complementary Architecture** Grid doesn't replace key management services –
  it orchestrates them. By combining multiple KMS providers with non-custodial
  account architecture, Grid delivers the complete custody, security, and user
  experience solution that applications need.
</Note>

## Enterprise-Grade Vendor Selection

Grid's fault tolerance relies on strategic partnerships with verified key management service providers:

**KMS Partner Criteria:**

* **Security certifications**: SOC 2 Type II, ISO 27001 compliance
* **Proven reliability**: Track record of uptime and security

## Key Benefits

<CardGroup cols={3}>
  <Card title="Regulatory Compliance" icon="shield-check">
    Multi-vendor architecture solves for vendor risk mitigation and redundancy
  </Card>

  <Card title="Simplified Experience" icon="zap">
    Enterprise-grade security without managing backups
  </Card>

  <Card title="Business Continuity" icon="refresh">
    Protection against vendor failures, security breaches, or extended service
    unavailability
  </Card>
</CardGroup>

<Tip>
  **Integration Strategy** Grid's architecture lets you leverage the best key
  management services while building complete, fault-tolerant applications. You
  get enterprise-grade KMS security with the operational resilience and user
  ownership that modern applications require.
</Tip>

## Next Steps

<CardGroup cols={2}>
  <Card title="Implementation Guide" icon="code" href="/grid/v1/accounts/quickstart">
    Learn how to integrate fault-tolerant Grid Accounts into your application
  </Card>

  <Card title="Authentication Methods" icon="lock" href="/grid/v1/accounts/authentication-methods">
    Explore Grid's authentication methods
  </Card>
</CardGroup>