Solana Developer Platform

• Name: Solana Developer Platform
• URL: https://solana.com/solutions/sdp
• Category: institutional tokenization-and-payments control plane / Solana API and custody orchestration layer / compliance-heavy asset-lifecycle platform
• Tags: solana-ecosystem
• Summary: Solana Developer Platform (SDP) is institutional Solana middleware: custody orchestration, token administration, compliance actions, payments flows, and asset-profile management in one operator-facing package. The project note should stay focused on that product surface. The separate question of who controls the public Solana-branded dashboard, docs, signup, support, and legal/privacy shell around it now lives in solana-foundation.
• What it does:
  • Provides a dashboard and REST API for real-world asset issuance, payments, and markets on Solana
  • Handles wallet custody through integrated signing providers so customer teams do not directly manage private keys
  • Supports token lifecycle operations such as create, deploy, mint, burn, supply management, and Token-2022-based configuration
  • Exposes compliance actions including freezing accounts, pausing token activity, seizing tokens, and managing allowlists for regulated flows
  • Orchestrates payment-related flows including balances, transfers, counterparties, and ramp/provider readiness checks
  • Offers organization, project, member, wallet, and API-key scoping so teams can separate environments and permissions cleanly
  • Publishes AI-ready docs, OpenAPI, Swagger UI, Postman collections, and llms.txt / llms-full.txt discovery surfaces
• Key claims:
  • The solution page says SDP is institutional infrastructure for digital assets built for compliant issuance, seamless payments, and efficient trading from a single platform on Solana
  • The same page says the platform is fully API driven, designed for institutions, and meant to work with AI coding tools
  • The docs introduction says SDP is a dashboard and REST API for real-world asset issuance, payments, and markets on Solana with built-in compliance controls
  • That introduction also says SDP handles wallet custody, onchain transaction construction, and compliance operations so teams can bring regulated assets onchain without managing keys or setting up Solana infrastructure
  • The wallet-setup docs say wallets are Solana keypairs managed by custody providers and that a signing provider must be initialized before creating tokens or executing transactions; provider capability chips are explicitly broken out across issuance, transfers, and compliance
  • The API-key docs say api_admin grants full access including custody and platform operations, while api_developer excludes custody actions, which is strong evidence that SDP is not merely exposing generic chain access but a managed operator permission model
  • The OpenAPI schema exposes machine-readable control states and enforcement/error codes including INVALID_API_KEY, EXPIRED_API_KEY, REVOKED_API_KEY, NOT_ALLOWLISTED, ACCOUNT_FROZEN, PROVIDER_NOT_CONFIGURED, and PROVIDER_UNAVAILABLE
  • The same schema also describes organization/project-scoped counterparties, payment accounts, ramp-readiness workflow, and atomic token-plus-asset-profile creation, which makes SDP look more like a full institutional control plane than a thin token helper
• Whitepaper: No canonical standalone Solana Developer Platform whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official SDP solution page, the public docs corpus, and the machine-readable llms.txt / OpenAPI surfaces; see ../whitepapers/solana-developer-platform-primary-sources-2026-05-04.md.
• Sources:
  • https://solana.com/solutions/sdp
  • https://platform.solana.com/docs/ai/llms.txt
  • https://platform.solana.com/docs/ai/llms-full.txt
  • https://api.solana.com/openapi.json

Internal linkages

• Public-operator and legal/support boundary for the Solana-branded shell around SDP: solana-foundation.
• Useful adjacent institutional-platform comparison: coinbase-developer-platform.

Protocol / company boundary

• Keep this note on the product surface: custody-provider orchestration, token lifecycle management, payment flow packaging, asset-profile workflow, API-key roles, and compliance actions.
• Use solana-foundation for the separate question who controls the public Solana-branded web, account, support, and legal/privacy perimeter institutions onboard through?
• That split matters because what can SDP do? and which named entity controls the official distribution and trust shell around SDP? are related but not identical questions.

Control surface

• Practical leverage inside SDP sits in custody-provider configuration, signing mode selection, project and wallet scoping, API-key issuance and revocation, provider onboarding, compliance-action exposure, and ramp/payment workflow packaging.

• The important read is not just Solana has token APIs. It is that SDP centralizes a meaningful amount of operational policy around who can sign, who can administer, which provider is configured, and when transfers or token accounts can be paused, frozen, seized, or allowlisted.

• Read SDP as a managed institutional operating layer above raw Solana primitives, not as a neutral pass-through to the chain.

• Last reviewed: 2026-08-12 UTC