Builders need access to grow on your chain
Teams starting out need reliable, free or sponsored RPC access. Without it, they build somewhere else.
Spectrum for Foundations
Sponsored infrastructure for the builders on your chain, and a clear view of who they are. Support your developer ecosystem without becoming an infrastructure operator.
Oasis NetworkSponsored nodesLast 30 days
AUser A12.4M callsApproved
eth_call52%
eth_getLogs31%
eth_getBalance17%
BUser B8.1M callsApproved
eth_getBlockByNumber44%
eth_getTransactionReceipt36%
eth_call20%
Support your ecosystem, without running the nodes
Running the nodes yourself is a job
Dedicated nodes mean dedicating ops and engineering time to keeping them healthy, patched and available.
You cannot see who is building
Sponsoring access is worth little if you have no visibility into which teams are using it and how.
Foundation tier
Sponsored nodes, plus the rest of the platform
Sponsored Nodes, labelled as yours
Developers request access to your sponsored nodes on Spectrum. You whitelist them, and you see exactly who is building on your chain.
No rate limits within hardware bounds
Bespoke configurations for your foundation, rather than a generic plan your builders have to fit into.
Engineering you can reach
24/7 DevOps on call, a dedicated Slack channel into engineering, a technical account manager and custom SLAs.
Beyond RPC, at no additional cost
Your builders get the whole platform, not just an endpoint.
Spectrum APIsThe full data API surface across 20+ chains, included for your builders.
WebhooksTreasury, multi-sig and ecosystem monitoring, pushed to your systems.
TypeScript SDKA typed SDK for anyone building on your sponsored nodes.
See exactly who is building on your chain
Sponsored Nodes are labelled as yours on Spectrum. Developers either request access for you to approve, or join your organisation directly with its 8-character code, and from that moment you have the ecosystem data a foundation is normally guessing at.
- Which teams are on your sponsored nodes, and which are still waiting on approval.
- How much each builder consumes, so you can see who is scaling and who has stalled.
- Which methods they are calling, so you know what your chain is actually being used for.
- Usage over time per builder, so a spike or a drop-off is visible when it happens.
- Rate limits set per builder, so one team cannot crowd out the rest of your ecosystem.
Organisation join code
K7M2XQ94
Share it once, and builders join the organisation themselves.
Access requests
AUser A2h agoReview
BUser BYesterdayApproved
Rate limit per builder
User A200 req/s
User B50 req/s
Why Spectrum
Bespoke configurations
Built around your chain and your builders, not a generic tier you are squeezed into.
Builder visibility
See which teams are on your sponsored nodes, how much they are consuming, and which methods they are calling.
One platform, one bill
RPC, APIs, Webhooks and SDK together, which means a lower total cost than assembling them separately.
Direct engineering access
A Slack channel into the people who run the infrastructure, not a ticket queue.
Regional infrastructure
Western Europe, North America and Asia, on hardware we own and operate.
Architecture consulting
Protocol development support for the builders on your chain, not just endpoints.
Already building with us
For foundations
Sponsor the builders on your chain
Tell us about your ecosystem and we will put together a Foundation Tier around it, with sponsored nodes labelled as yours and the visibility to go with them.
Bespoke configuration · Direct engineering access