Skip to content
Magma Devs
Platform

The Intelligence and Security Layer for Blockchain.

Reach 284 blockchain networks through our RPC providers, your own infrastructure, or both. One platform to secure, monitor, and intelligently manage every request. Detect anomalies, enforce security policies, ensure reliable connectivity, and gain complete visibility with AI-powered insights and audit-ready evidence.

Your appSmartRouterMagma fleetYour RPCYour node
Managed access / BYOP / Hybrid

Run in production by

Kraken
Fireblocks
Galaxy
Hypernative
284
blockchain networks
3
ways to connect: our providers, yours, or both
4
interfaces: JSON-RPC, REST, gRPC, Tendermint
SOC 2 + ISO
SOC 2 Type II and ISO 27001 certified

BUYER QUESTIONS

What buyers ask first.

Do you provide the RPC access, or do I bring my own?

Either. Use our providers, connect your own provider accounts and nodes, or mix them per chain. What is included depends on your plan.

Supported connectivity and interfaces

What happens when a provider fails?

The router retries the request on another provider that can serve it, inside the same time limit. It needs a second provider set up for that chain to do this.

Provider selection and recovery

How do you check the data?

The router tracks each provider's latest block, and a provider that falls behind stops being picked. You can also turn on a check that compares answers across providers for the reads you choose.

Data integrity controls and scope

What does Magma run, and what stays with us?

We run the routing, the provider connections, monitoring and operations. Your applications, keys, signing and business logic stay with you.

Managed connectivity responsibilities

FIREBLOCKS

“With Magma Devs, we ensure our customers experience the speed, reliability, and data freshness they demand.”
Pavel Berengoltz, Co-Founder and CTO, Fireblocks

From the Fireblocks article "Can you trust your blockchain data", written with the Magma team.

Read the article on Fireblocks
The dashboard

What your team sees, for every chain and every provider

Smart Router dashboard: success rate, retries, cache offload, failed requests, lagging answers caught, and a table of routers per chain with availability, response time and status.
Kraken
"As crypto markets mature, infrastructure matters as much as liquidity. Integrating Magma Devs' Smart Router strengthens the resilience and reliability of our platform at global scale. It allows us to deliver consistent performance and secure access to digital assets, even during periods of extreme market activity."
Brett McLainVP & Head of Payments & Blockchain, KrakenRead the case study
Brett McLain

The problem

Most exchanges and custodians run RPC themselves: a few providers, some retry logic, their own dashboards. It works until a provider falls behind the chain and keeps answering, or rate-limits you in your busiest hour. Then the first hour goes on one question: is it us, the provider, or the chain?

Whose fault was it? You'll know.

Every reply carries headers that name the provider that served it and how many tries it took. Every failure is sorted by who caused it: your request, the contract, the provider, or the chain. A reverted contract never counts against a provider. When you want a person, our team looks at it with you, with the evidence.

What we keep track of, so your team does not have to

  • Every chain: hard forks, new RPC versions, retired methods and new interfaces, like a chain moving off JSON-RPC.
  • Every provider: outages, rate-limit changes, quiet lag behind the chain, and which methods each one really serves.
  • Your traffic: every request, which provider answered, how long it took, what failed and why.
Build or buy: the full comparison
provider: provider-a
retries: 1
cause: provider fell behind
Your requestThe providerThe chain

How a request moves

AppSmart Routercacheprovider scoringretryfailoverMagma fleet / BYOP / hybrid
  1. Your app sends a request to one endpoint.
  2. If the answer is cached and still valid, you get it back at once.
  3. If not, the router scores every provider for this chain and picks one. Providers that are slow, behind the chain, or rate-limited lose the pick.
  4. The request goes out. If the provider fails, the router retries on another one inside the same time budget.
  5. You get the answer, with headers that say which provider served it and how many tries it took.

Built to stay up

Your own deployment

On private hosting, your router runs in its own deployment. No other customer's traffic shares it.

Resilient by design

The setup is sized to your agreement, so traffic keeps flowing if a server has a problem.

Always yours

Your endpoints, settings and logs stay yours. You never lose access to your system.

Uptime commitments are set in your agreement.

How it compares

In-house proxyOpen-source proxy you runRPC providerSmart Router
More than EVM chainsYou build itPartialTheir chains only284 Supported Blockchain Networks
Failover and retry across providersYou build itYesInside their network onlyYes
Rate-limit handling per providerYou build itYesNoYes
Cache shared across replicasYou build itYesNoYes
Run for you 24/7Your teamYour teamYesYes
Compliance evidence (SOC 2 Type II, ISO 27001)You build itNoVariesYes

Detailed comparisons:eRPC vs Smart RouterdRPC vs Smart RouterAlchemy vs Smart RouterQuickNode vs Smart RouterInfura vs Smart RouterAnkr vs Smart RouterTatum vs Smart Router

One platform for dependable blockchain connectivity.