Skip to content
Magma Devs
Services / Onboarding

Get your blockchain connectivity ready for production.

Start with Magma-managed RPC access, bring your existing provider accounts and private nodes, or combine both. Magma helps configure supported networks, validate endpoints and routing, and prepare your applications for the agreed deployment. Provider procurement is not always your responsibility; access, usage and onboarding work follow your package.

Your providers. Your networks. One reliable routing layer, configured with Magma.

  • Onboarding within a day for prepared, supported setups
  • 284 Supported Blockchain Networks
  • Existing RPC providers supported
  • Endpoint validation before go-live

One-day onboarding applies to supported configurations with required endpoints, access, and deployment prerequisites ready. Complex or custom integrations are scoped separately.

  1. 1Configure
  2. 2Validate
  3. 3Connect

Your RPC infrastructure

Ethereum, Solana, Bitcoin
Existing providers & private nodes

Magma routing layer

One configuration
Network-aware provider selection

Configure your connectivity

Magma organizes compatible endpoints into network and provider groups.

Routing configuration prepared

Illustrative onboarding workflow. Actual readiness depends on the selected networks, endpoint access, required methods, deployment configuration, and agreed validation criteria.

The challenge

Adding a reliability layer shouldn't become another infrastructure project.

Your blockchain systems already depend on RPC providers and nodes.

The providers may come from different vendors. Your applications may use JSON-RPC, REST, gRPC, or other chain-specific interfaces. Some networks need specialized methods or infrastructure capabilities.

Adding Smart Router should make that environment easier to operate. But a successful integration requires more than placing a proxy in front of a few endpoints.

The networks must be configured correctly. The endpoints must be accessible. The supported capabilities must match the application's needs. And the customer should know what will happen when a provider fails before routing critical production traffic through the new infrastructure.

Too many endpoints to configure

A multi-chain environment may contain dozens of networks, each with its own interfaces, upstream URLs, authentication, and provider settings.

Manual setup creates repetitive work and room for mistakes.

Unknown provider readiness

An endpoint may respond to a basic request but lack an API capability needed by the application.

Problems with archive access, debug methods, WebSockets, or other supported interfaces may not be obvious until production traffic reaches the endpoint.

Risk during the transition

Changing the routing path of critical blockchain traffic requires coordination.

Teams need an agreed cutover process, relevant tests, and a way to assess whether the new setup behaves as expected.

The goal isn't just to deploy Smart Router. It's to know your blockchain connectivity is ready for the traffic that matters.

From requirements to connectivity

We help bring your existing blockchain infrastructure together.

Magma's onboarding process is designed around the networks, providers, and deployment environment the customer already uses.

The goal is to establish the agreed RPC connectivity and validate it before the environment carries the intended production workload.

01 - Understand your environment

Review the required blockchain networks, RPC interfaces, providers, private nodes, important methods, traffic expectations, and deployment needs.

Identify the configuration and access requirements before implementation.

Typical engagement structure. Actual scope and tests depend on the supported networks, customer environment, selected service, and agreed acceptance criteria.

We configure the connectivity layer. Your team retains control over application behavior, business logic, and the production cutover decision.

See the onboarding process

Your existing infrastructure, configured into one dependable routing environment.

A successful onboarding process must account for the networks, providers, and workloads your systems actually use.

Explore how a multi-chain environment can move from separate provider connections into a configured Smart Router setup.

Selected networks

Ethereum MainnetJSON-RPC
Solana MainnetJSON-RPC
Bitcoin MainnetJSON-RPC

Illustrative onboarding demonstration. Actual configuration, validation, and go-live depend on customer requirements, available endpoints, access, supported networks, and agreed acceptance criteria.

Check before go-live

An endpoint URL isn't proof that the endpoint is ready for your workload.

RPC providers don't always expose identical capabilities. Two endpoints may support the same blockchain while differing in available methods, archive access, WebSocket support, authentication, or operational behavior.

A basic successful response does not establish that every application requirement is supported.

Smart Router includes a specification-driven health-check command that evaluates configured upstream endpoints using the applicable checks defined for the network and interface. The onboarding process can combine those checks with additional tests for the methods and workflows agreed with the customer.

Endpoint connectivity

Confirm that the configured upstream is reachable and responds to the applicable health request.

Chain and interface compatibility

Check relevant network identity and supported interface behavior where defined by the specification and selected checks.

Required capabilities

Review addon and extension capabilities such as archive, debug, trace, or WebSocket functionality when applicable and supported by the network specification.

Customer workload readiness

Run additional agreed tests for important methods and routing behavior that a standard health probe alone cannot establish.

Illustrative endpoint health matrix
Configured upstreamReachableInterface CheckRequired CapabilityRouting EligibilityReview Status
Ethereum Provider A
Ethereum Provider B
Ethereum Private Node
Cosmos Provider A
Solana Provider A
Passed Requires attention Not applicable Not tested

Illustrative endpoint states. Not live customer results. The built-in health checker runs specification-defined checks; it does not execute every RPC method or guarantee future requests.

Validation should tell you where the infrastructure is ready and where an endpoint, permission, or configuration still needs attention.

Smart Router health checking
From configured to live

The final step isn't connecting providers. It's moving traffic with confidence.

Once the routing environment is configured and validated, applications need to start using it. For customers with existing blockchain infrastructure, this transition should be deliberate.

The application may already communicate directly with several providers or use an internal RPC gateway. The agreed cutover process defines how the new Smart Router connectivity is introduced into that environment.

The customer and Magma should review critical workflows, routing behavior, and operational responsibilities before considering onboarding complete.

  1. Confirm the production configuration

    Magma helps review the supported networks, interfaces, provider access and routing settings against the agreed requirements.

  2. Test the requests your application depends on

    Together, the teams run agreed workload tests to check relevant methods and routing behavior, and identify gaps before traffic moves.

  3. Coordinate the transition

    Magma helps prepare the connectivity layer. Your team authorizes and applies application changes through its own deployment and approval process.

  4. Review behavior after the change

    Magma reviews relevant routing telemetry while your team checks application outcomes. The teams coordinate outstanding issues within the agreed scope.

The customer retains control of application changes and business-level go-live approval. Magma helps prepare and validate the connectivity layer.

From a few networks to enterprise scale

A hundred networks shouldn't require a hundred separate onboarding projects.

Multi-chain infrastructure companies often operate across dozens of blockchain networks and API interfaces. Each network can have its own upstream endpoints, configuration requirements, and operational dependencies. Handling these integrations independently can create a large amount of repetitive work.

Smart Router uses a common orchestration architecture with chain-specific specifications. Magma's onboarding process can use that architecture to configure supported networks, connect existing providers, and perform relevant endpoint checks as part of one coordinated setup.

The website's onboarding target is within one day for prepared supported environments, including large configurations. The key is having the required networks, upstream access, infrastructure environment, and agreed requirements ready before execution.

  • EVM networks · JSON-RPC
  • Solana · JSON-RPC
  • Bitcoin-family · JSON-RPC
  • Cosmos · REST / gRPC / Tendermint RPC
  • Other non-EVM · Chain-specific interfaces

Magma Onboarding

Configuration · Provider integration · Validation

One Smart Router environment

0 of 5 network groups configured

One-day onboarding is the target for supported, prepared environments. Unsupported networks and additional engineering requirements are scoped separately.

One common infrastructure layer

Use a shared routing architecture across supported networks rather than building independent provider management for each chain.

Chain-specific configuration

Preserve network-specific RPC behavior while reusing the common orchestration system.

Coordinated validation

Review the configured environment through a structured onboarding process instead of treating every endpoint as a separate project.

The scale of your blockchain network catalog shouldn't dictate the amount of repetitive infrastructure setup your engineering team must perform.

Fireblocks
Proven in enterprise integration

A routing layer that fit into Fireblocks' existing infrastructure in one onboarding session.

Fireblocks operates institutional digital asset infrastructure across more than 100 blockchain networks. Its applications use a combination of internal and third-party RPC infrastructure.

Introducing a new routing and reliability layer into such an environment requires compatibility with systems that are already in use.

Magma's published Fireblocks case study reports that the initial Smart Router integration into Fireblocks' environment required only a single onboarding session.

The deployment demonstrated how Smart Router can be introduced above existing RPC providers rather than forcing the customer to replace its underlying infrastructure.

For enterprise teams, that is the important principle. A new reliability layer should work with the systems already supporting the business.

One session

Reported initial Smart Router integration at Fireblocks

100+ networks

Blockchain coverage operated by Fireblocks across its broader infrastructure environment

The single-session result refers to the initial Smart Router integration documented in the Fireblocks case study. It does not mean every blockchain can be newly integrated in one session, that all Fireblocks networks were added in that session, that every customer cutover takes the same time, or that every provider or method is automatically compatible.

Read the Fireblocks case study
Existing applications
Magma Smart Router
Internal RPCProvider group AProvider group B
Illustrative. Not Fireblocks' actual topology.
KrakenFireblocksGalaxyHypernative

Smart Router in production at leading digital asset infrastructure companies.

A clear starting point

Bring your infrastructure details. We'll help put the routing layer together.

The fastest onboarding engagements begin with a clear understanding of the environment being connected.

Magma can help configure the routing layer, but the customer or its providers must supply the access, infrastructure, and business requirements needed for the integration.

Blockchain requirements

The networks, environments, interfaces, and critical RPC methods the customer needs.

Provider endpoints

The compatible upstream URLs and relevant provider information, including customer-operated nodes where applicable.

Access and environment

The necessary provider permissions, secure credential delivery arrangement, and deployment access appropriate to the selected hosting model.

Application requirements

The important request types, routing expectations, validation requirements, and intended go-live conditions.

A complete requirements and access package makes it easier to configure, validate, and prepare the environment efficiently.

Please don't send API keys or credentials through the contact form. Sensitive onboarding details are exchanged through an agreed secure process after engagement.

Know who owns what

Your applications remain yours. The routing setup becomes a shared, clearly defined effort.

Successful onboarding depends on a clear boundary between the infrastructure Magma configures and the systems the customer continues to operate.

The exact responsibilities vary according to the selected service and deployment model.

Magma's onboarding responsibilities

As agreed:

  • Review RPC requirements
  • Prepare Smart Router configuration
  • Integrate supported networks
  • Configure compatible providers
  • Review relevant routing settings
  • Perform applicable health checks
  • Support agreed integration validation
  • Coordinate routing-related go-live readiness
  • Clarify ongoing service responsibilities

Customer responsibilities

  • Provide accurate network requirements
  • Supply required provider access
  • Maintain relevant provider accounts unless separately contracted
  • Provide necessary deployment information
  • Confirm application-critical methods
  • Perform or approve application-level tests
  • Authorize production changes
  • Manage business-level incident and transaction logic

Third-party provider responsibilities

  • Operate their own RPC endpoints
  • Maintain provider-specific API availability
  • Provide relevant method and interface support
  • Resolve problems in infrastructure under their control

Customer Systems

ApplicationsBusiness logicGo-live approval

Magma Onboarding and Smart Router

ConfigurationEndpoint checksRouting review

Independent RPC Providers

Own endpointsAPI availabilityMethod support
Magma does not receive signing keys or take custody of customer assets.

Magma helps make the RPC environment ready. The customer retains control of its applications and production decisions.

Deployment options

The onboarding process adapts to where Smart Router runs.

Smart Router can be operated in different environments. The configuration and validation approach follows the deployment model agreed with the customer.

Managed Cloud

Managed routing without operating the router yourself.

Magma provides a managed Smart Router environment under the selected cloud plan.

Onboarding focuses on the supported networks, provider configuration, application connection, and relevant validation.

Available network coverage, capacity, and support follow the selected plan.

Customer ApplicationMagma Shared CloudRPC Providers

Private Enterprise Hosting

Dedicated routing infrastructure operated by Magma.

For customers selecting Private Hosting, onboarding prepares a dedicated single-tenant Smart Router deployment on Magma-managed servers.

The agreed setup includes relevant provider connectivity, configuration, validation, and production readiness steps.

Customer ApplicationDedicated Magma DeploymentRPC Providers

Self-hosted

Run Smart Router in your own environment.

Smart Router provides self-hosted configuration and deployment tools, including a configuration wizard and specification-driven endpoint health checks.

The customer operates its infrastructure. Any additional assisted onboarding or engineering support depends on the applicable commercial arrangement.

Customer ApplicationCustomer-operated Smart RouterRPC Providers

The goal is the same across deployment models: a defined, configured routing environment with the appropriate readiness checks and clear operational ownership.

Explore deployment options
The right service for the job

Getting your existing setup running is different from building a new capability.

Not every integration requirement belongs in the same engagement.

Onboarding focuses on configuring and validating supported infrastructure so the customer can begin using Smart Router. Dedicated Engineering addresses additional requirements that may need new integration work, specialized behavior, or product changes.

Understanding that distinction helps both teams set the right scope and delivery expectations.

Standard configuration path

Onboarding

Configure supported blockchain connectivity using available product capabilities.

Typical requirements

  • Supported chains
  • Existing provider endpoints
  • Standard configuration
  • Health checks
  • Agreed routing tests
  • Go-live preparation

Outcome: "Configured environment ready for the agreed production review."

Custom engineering path

Dedicated Engineering

Scope and implement requirements that go beyond standard supported setup.

Typical requirements

  • Unsupported chain integration
  • Specialized provider API
  • Custom RPC behavior
  • Platform enhancement
  • Unusual deployment integration
  • New functionality

Outcome: "Agreed engineering deliverable with defined acceptance criteria."

The goal is to keep standard onboarding efficient while ensuring genuinely custom requirements receive appropriate engineering attention.

Explore Dedicated Engineering
Ready for operations

Onboarding ends with a connected environment. Operational ownership continues.

Once Smart Router begins serving the agreed traffic, the infrastructure still needs to be monitored and maintained.

Provider availability changes. Blockchains upgrade. Methods and interfaces evolve. Configuration changes may become necessary as requirements grow.

The operating model after onboarding depends on whether the customer self-hosts or uses a managed Magma service.

  1. Onboarding
  2. Go-Live
  3. Monitoring
  4. Ongoing Operations

Monitoring

Review relevant provider health, routing errors, request outcomes, and operational signals.

Maintenance

Keep the supported routing infrastructure and necessary configurations aligned with operational requirements and network changes.

Incident response

Follow the agreed service and escalation arrangements when infrastructure problems require engineering intervention.

Onboarding establishes the routing environment. Managed operations and Enterprise technical support define who is responsible for keeping that environment healthy afterward.

Explore 24/7 Technical Support
On the roadmap

Making blockchain infrastructure onboarding even more self-service.

We're extending the onboarding experience to give customers more direct control over supported network and provider configuration.

The goal is to preserve a clear path to reliable connectivity while reducing the amount of manual setup required.

On the roadmap · Planned capability 1

Dashboard-based onboarding

Introduce supported onboarding workflows through the Smart Router Dashboard, allowing customers to prepare configurations more directly.

On the roadmap · Planned capability 2

Self-service network management

Allow customers to manage additional supported network configurations through an appropriate interface.

On the roadmap · Planned capability 3

Greater onboarding visibility

Provide clearer status information about configured networks, upstream readiness, and outstanding integration requirements.

Planned capabilities. Scope, availability, and delivery dates may change.

Frequently asked questions

For supported configurations with the required provider endpoints, access, deployment environment, and technical requirements ready, onboarding can be completed within a day. Complex deployments, unsupported networks, missing access, or additional engineering requirements may extend that timeline. The applicable scope and readiness criteria are reviewed with the customer.

Smart Router supports 284 blockchain networks, and Magma's onboarding approach is designed to handle large multi-chain configurations. A supported, prepared environment involving approximately 100 networks can be onboarded within a day, subject to the required endpoints, access, configuration, and agreed validation scope being ready. This is not a guarantee that every unsupported chain or custom integration can be delivered in that time.

No. Smart Router operates above compatible providers and private nodes that you already use. The onboarding process focuses on connecting and configuring the existing upstream infrastructure rather than replacing every provider.

The standard onboarding approach can use provider accounts and endpoints supplied by the customer. Any arrangement in which Magma procures, manages, or pays for upstream provider services must be explicitly included in the applicable commercial agreement.

The main requirements are the supported networks, intended RPC interfaces, configured provider endpoints, appropriate secure access, critical methods, deployment requirements, and the technical criteria the application needs before go-live.

The process includes applicable endpoint checks and agreed integration validation. Smart Router has specification-driven health-check capabilities for configured upstreams. These checks do not automatically execute every possible RPC method or guarantee future availability. Additional workload-specific testing may be required.

Where supported by the chain specification and relevant configuration, the endpoint health-check process can evaluate applicable addon, extension, or WebSocket requirements. Any additional method-level or end-to-end testing must be defined according to the customer's workload.

The gap must be identified and addressed before that workload is considered ready. Depending on the chain and method, the solution may involve a different eligible provider, appropriate configuration, or additional engineering. Magma cannot create capabilities that an upstream provider does not offer merely through routing.

Not by itself. A standard health check establishes only the behaviors it actually tests. Production readiness may also require method compatibility, routing tests, application integration checks, operational review, and customer approval.

Yes. Compatible customer-operated nodes can be connected alongside third-party RPC providers, subject to the relevant network, interface, connectivity, and access requirements.

Yes. Smart Router supports 284 blockchain networks across multiple blockchain families and RPC interfaces. The exact supported methods and functionality depend on each network's specification.

Applications generally need to point their supported RPC connections at the appropriate Smart Router endpoint. Additional changes depend on the blockchain interface, deployment topology, authentication setup, and application requirements. Magma does not promise zero application changes in every environment.

Magma can help plan and coordinate routing-related cutover activities as part of the agreed onboarding scope. The customer remains responsible for authorizing relevant application and production environment changes.

Magma can review the network's interfaces, available providers, and integration requirements. Additional chain support may require separately scoped engineering work and validation. Unsupported networks are not covered by the standard one-day onboarding promise.

A full hosted self-service onboarding experience is part of Magma's roadmap. Smart Router already provides self-hosted configuration and health-check tooling, but that is not the same as a generally available customer dashboard for automatic hosted onboarding.

Yes. Smart Router supports self-hosted deployment under the applicable license. Additional assisted onboarding or Enterprise support arrangements depend on the customer's commercial agreement.

The customer and Magma follow the agreed operating model. With eligible managed services, Magma can operate the routing infrastructure and provide monitoring, upgrades, and incident response. Self-hosted teams generally remain responsible for their own infrastructure unless additional support is contracted.

24/7 monitoring and incident response are available under applicable Enterprise service arrangements. They are not automatically included in every cloud or self-hosted onboarding engagement.

Yes. Joint review and validation can be part of the agreed onboarding process, especially for critical application methods and production workflows. The relevant participants, tests, and approval process depend on the engagement.

Contact Magma with your supported networks, existing provider environment, deployment requirements, and intended workloads. The team can review the prerequisites and discuss an appropriate onboarding plan.
Ready to connect your infrastructure?

How many RPC providers and blockchain networks would your team need to onboard today?

Tell us which networks you support, which providers and private nodes you already use, and where your infrastructure runs.

We'll help you review the configuration requirements, identify the relevant validation steps, and plan the transition to Smart Router.

For supported and prepared environments, the routing setup can be ready within a day.

You keep your providers and applications. Magma helps bring the connectivity together.

Keep your existing infrastructure. Get more reliability from the way it works together.