What is Solana Developer Platform?

Solana Developer Platform (SDP) is a dashboard and REST API for issuing, transferring, and managing tokens on Solana. It handles wallet custody, onchain transaction construction, and compliance operations so your team can integrate Solana into existing systems without managing keys or setting up a Solana environment.

What you get

Token lifecycle management — Create tokens from pre-built templates (stablecoin, tokenized security) or configure your own using Token-2022 extensions. Deploy, mint, burn, and manage supply through the dashboard or API.

Wallet custody — Provision signing wallets through integrated custody providers. SDP manages the signing infrastructure so your team never handles private keys directly.

Projects and scoped access — Organize integrations by project, assign members, and issue project-scoped API keys so teams or environments do not share the same wallet and token surface.

Compliance operations — Freeze individual accounts, pause token activity, seize tokens, and manage allowlists for regulated issuance flows. Selected compliance actions accept reason or memo fields for audit trails.

Two signing modes — SDP supports both modes for transaction-building flows such as issuance, payments, and compliance actions:

• Execute — SDP builds, signs, and submits the transaction in one API call
• Prepare — SDP builds the transaction and returns it unsigned. You sign with your own infrastructure (hardware wallet, multisig, internal HSM) and submit it yourself.

Transaction simulation — Prepare endpoints accept a simulate: true option that dry-runs the transaction before you sign, returning compute units consumed, program logs, and any errors.

Scoped API keys — Generate keys with specific permission sets (tokens:read, tokens:write, tokens:admin, etc.) and rotate them without downtime.

Architecture

SDP exposes two interfaces that connect to the same backend:

• Dashboard — browser-based UI for setup, token management, and compliance operations. Authenticate via Clerk (email, Google, or GitHub).
• REST API — programmatic access for backend integrations. Authenticate with an API key in the Authorization header.

The typical integration path:

1. Create an organization and generate API keys
2. Provision a signing wallet
3. Create and deploy tokens (from templates or custom configuration)
4. Integrate minting, transfers, and compliance operations into your product
5. Manage supply, allowlists, and frozen accounts as your product operates

Environments

Both environments expose identical APIs. Develop and test against sandbox, then switch to production by swapping your API key.

Next steps

• Getting Started — create an organization, provision a wallet, and issue your first token
• Guides — step-by-step walkthroughs for each workflow