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

# Production architecture

> Generic service topology and persistence boundaries.

```mermaid theme={null}
flowchart LR
  IN[Internet] --> WEB[Next.js web]
  WEB --> API[Go API]
  WEB --> RPC1[Browser-safe Base RPC]
  API --> PG[(PostgreSQL)]
  API --> OBJ[(Object storage volume)]
  API --> RPC2[Server Base RPC]
  IDX[Go indexer] --> RPC2
  IDX --> PG
  API -. configured dependency .-> R[(Redis)]
  IDX -. configured dependency .-> R
```

Compose publishes web and API only on loopback in the repository topology, leaving public ingress and TLS to external infrastructure. PostgreSQL is loopback-only and Redis is not host-published. Persistent volumes hold PostgreSQL, Redis, and metadata objects.

The public frontend RPC is safe to expose but rate-limited. Production API/indexer traffic should use a dedicated server-side Base Mainnet RPC. Server RPC URLs can contain credentials and must never be copied into `NEXT_PUBLIC_` variables.

No private hostnames, addresses, SSH details, or credentials are part of the public architecture contract.