> [Agent navigation index](/llms.txt)

# Caching Data

Brix has two separate caching systems. Use these focused guides to configure policies, invalidate changed data, and select stores without crossing cache ownership boundaries.

- **Native data caching** (`brix/cache`) reuses validated JSON reads made with `executeApi`,
  `client.execute`, `useApi`, and Contentful Delivery clients. Nothing is cached until a read passes
  an explicit policy such as `dataCache.public("30s")`.
- **Route cache hints** (`cache` on page and fragment routes) only describe complete responses to
  your edge. Brix never stores route responses.

## Choose a workflow

- [Configure eligibility, scope, freshness, and fallback policies.](/docs/caching-policies.md)
- [Invalidate contracts or tags while preserving cache ownership boundaries.](/docs/caching-invalidation.md)
- [Select memory, DynamoDB, Fastly KV, or custom stores and configure edge hints.](/docs/caching-stores.md)
