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

# Protocol Overview

> The end-to-end architecture of Raydium across all four product lines, the infrastructure they share, and how versions have evolved.

## Who this chapter is for

Developers, researchers, and operators who want the 30,000-foot view before diving into a specific product. If you already know which product you need, skip to `/products`.

## Chapter contents

<CardGroup cols={2}>
  <Card title="Architecture" icon="sitemap" href="/protocol-overview/architecture">
    A single diagram showing all four programs (AMM v4, CPMM, CLMM, Farm/LaunchLab), their on-chain state, off-chain infrastructure (API, SDK, indexers), and the user/aggregator entry points.
  </Card>

  <Card title="Shared infrastructure" icon="network-wired" href="/protocol-overview/shared-infrastructure">
    Cross-program primitives: authority PDAs, admin/config accounts, fee collection, oracle usage, the REST API surface that fronts all products.
  </Card>

  <Card title="Versions and migration" icon="code-branch" href="/protocol-overview/versions-and-migration">
    Release history per product, deprecations, and the recommended migration paths (notably AMM v4 → CPMM, Farm v3/v5/v6).
  </Card>
</CardGroup>

## Writing brief

* `architecture.mdx` should have ONE canonical diagram that every other chapter can reuse. Commit the source (Mermaid or draw\.io) alongside the SVG.
* `shared-infrastructure.mdx` is where repeated patterns (e.g., the protocol/fund-fee collection pattern) are *defined once*. Product pages link here.
* `versions-and-migration.mdx` is the chapter to check when something is deprecated — link to it from every page that uses a deprecated primitive.