Self-hosting
Run the Solana Developer Platform on your own infrastructure with Docker Compose.
Self-hosting runs the full Solana Developer Platform (API, dashboard, docs, database, and cache) on infrastructure you control, from prebuilt container images. You bring your own authentication (Clerk), Solana RPC, and signing provider.
What you run
The release's compose.yml starts six services:
| Service | Image | Purpose |
|---|---|---|
sdp-api | sdp-api | The API, on port 8787 by default. |
sdp-web | sdp-web | The dashboard, on port 3000 by default. |
sdp-docs | sdp-docs | These docs, on port 3001 by default. |
sdp-migrate | sdp-api | Applies pending database migrations, then exits. |
postgres | postgres:16-alpine | The bundled database. You can use an external one instead. |
redis | redis:7-alpine | The bundled cache. You can use an external one instead. |
Start here
- Quickstart: install the stack and bring it up.
- First devnet deployment: sign in to the dashboard, create a local wallet, and call the API with a wallet-scoped key.
- Configurator: generate a complete
.envin your browser or terminal. - Environment reference: what the variables do and which ones are required.
Operate
- Upgrade and backup: move to a new release and protect your data.
- Troubleshooting: common startup and configuration failures.
- External co-signers: host provider-specific signing services beside the stack.
Requirements
- A 64-bit Linux or macOS host (x86-64 or Arm64) with Docker Engine and Docker Compose v2.
- Outbound network access to pull images and reach your Solana RPC and Clerk.
- A Clerk application and a Solana RPC endpoint. The environment reference lists the rest.