Infrastructure Provider Onboarding
Add an infrastructure provider integration to SDP through the self-service contribution process.
SDP currently supports infrastructure provider integrations across custody, RPC, compliance, and ramps. We will add future integration categories as SDP expands.
Onboarded providers are presented as available integrations, not endorsed or recommended partners. Institutions using SDP are responsible for their own provider due diligence.
Start here
Select the category that matches your integration, complete the intake form, and review the criteria before opening a pull request.
| Category | Intake form | Criteria |
|---|---|---|
| Custodial enterprise wallet | Complete custody intake | Download custody criteria PDF |
| RPC infrastructure | Complete RPC intake | Download RPC criteria PDF |
| Ramp | Complete ramp intake | Download ramp criteria PDF |
If your integration is for compliance or another infrastructure category without a published intake, contact the SDP team before opening a pull request.
Onboarding steps
- Review the criteria PDF for your category.
- Complete the matching intake form.
- Provide sandbox or playground API access.
- Share documentation, test credentials, supported networks, rate limits, and sandbox limitations.
- Build the SDP integration with tests and docs.
- Open a pull request that links to the intake submission or tracking issue.
The SDP team reviews intake completeness within five business days. Gate evaluation usually takes one to three weeks depending on category, documentation completeness, and required technical validation.
Evaluation
Each category uses the finalized criteria linked above. Every review starts with hard gates, followed by scored evaluation when applicable.
At a high level, SDP evaluates:
- Solana compatibility for the category.
- Stable sandbox or playground access.
- Clear API and integration documentation.
- Predictable error handling and testability.
- Operational readiness and support.
- Required regulatory, compliance, or security posture for the category.
Providers that do not clear the required gates may be tracked for future support, but should not be presented as generally available in SDP until gaps are resolved.
Access requirements
Provide access suitable for repeatable validation, including:
- Sandbox API keys or equivalent credentials.
- Test accounts, wallets, endpoints, or settlement rails when required.
- Supported Solana networks.
- Known rate limits, feature flags, and sandbox limitations.
- Technical support contact for review.
Pull request expectations
An SDP infrastructure provider contribution usually includes:
- Provider metadata and capability registration.
- API support for setup, configuration, and category-specific runtime operations.
- Dashboard support where applicable.
- Tests for setup, success paths, failure states, disabled configuration, and missing credentials.
- User-facing docs for setup, sandbox behavior, and provider limits.
Open the pull request after intake is complete, or after the SDP team has created a tracking issue while intake is being finalized.