Introducing Smart Router

RPC orchestration and security for blockchain enterprises. Open source, with a managed service.

Today we're launching Smart Router, the RPC layer built for companies that can't afford downtime or bad data.

Smart Router is the accomplishment of more than a year of intense research and development, and thanks in part to the fantastic input and feedback from our early design partners and clients. The first of those partners was Fireblocks, the enterprise platform that thousands of institutions use to custody and move digital assets and that has handled more than 10 trillion transactions. They came to us about a year ago.

During the launch of the $TRUMP token in early 2025, one of the most congested events in Solana's history, Fireblocks needed to keep transactions flowing for their clients while Solana RPC providers failed one after another, and the routing layer running on top of our open-source core held. They asked us to turn that core into a product they could run in production.

"That was the moment we realized it's a new category," says co-founder Yair Cleper. "Every serious team is quietly building the same thing in the back end, patch on patch, and none of them knows a product can take the nightmare away." So we built one: a single reliability and security layer for RPC that any enterprise can adopt.

Smart Router sits between your application and your RPC providers. It routes, retries, validates, and observes every request in real time, across every provider and every chain, from one control plane. It removes any single provider's uptime or security posture as your point of failure.

Think of it as the Cloudflare of blockchains: the layer you put in front of blockchain access to keep it fast, available, and verifiably correct, without managing which node answers which call.

tl;dr: Smart Router is an open-source core, free to run, with a commercial self-host license and a fully managed enterprise service on top. It terminates a single RPC endpoint, scores and selects upstreams per request, retries and fails over on error, cross-validates responses across providers using configurable cross-validation policies, and exposes the full request lifecycle through an observability platform. It is chain-agnostic, including non-EVM, and already runs in production for Kraken, Fireblocks, GK8 (by Galaxy), and Hypernative, and is available via the Google Cloud Marketplace.

Why now

Financial institutions are operating on blockchains today. The time that these mass-scale enterprises were evaluating digital assets is over. They are now running on them. At that scale, downtime and bad data aren't engineering inconveniences, they are business and security events with direct financial consequences.

Regulation is accelerating the shift. In the EU and beyond, new rules push blockchain teams toward higher standards for reliability and security and require accurate, machine-readable records, which means reducing dependence on any single third party.

"Financial institutions are moving into digital assets today. It's not a future mission. When they're that deeply involved, they can't afford mistakes or downtime. If your access to the blockchain is down, that's not a dev-team problem. It's a business problem."

The problem every serious team already knows

The standard RPC endpoint is a single point of failure that understands nothing about the requests it serves. The exposure it leaves teams with is concrete: downtime when a provider goes dark, security risk when a node returns wrong or malicious data, latency on time-sensitive calls, and failed transaction broadcasting. So teams compensate: several providers behind a hand-rolled load balancer, basic retry logic, health-check scripts, and an on-call rotation to absorb what leaks through. It works until a reorg, a rate limit, or a silently truncated response says otherwise.

Wiring two or three providers together with basic retries is the easy version of this problem; a small team can do it in a month. Doing it at institutional scale is a different undertaking: hundreds of upstreams across hundreds of chains, connection and session management, response-aware failover, and a scoring system that continuously ranks providers to match the right one to each call. It's about building an intelligent platform for blockchain orchestration, not just a script. As CTO Idan Hen puts it, "connecting to hundreds of RPC nodes, with session management, fallback, and live ranking of every provider, is a hard problem. It's not a few prompts, it's a substantial platform."

It's easy to underestimate how deep that dependency runs. An analysis of Fireblocks' public incident history (more than 1,200 incidents since 2021) found that blockchain-node and RPC issues account for 59% of all incidents, that a single RPC incident has taken down as many as 46 chains at once, and that node work drives 85% of scheduled maintenance. At institutional scale, RPC isn't one risk among many. It's the dominant one.

No existing product solves the whole of it in one place: every blockchain including non-EVM, production SLAs, compliance, and genuine RPC security, including meaningful cross-provider validation policies. That is the gap Smart Router was built to close. And the stakes go beyond uptime. The $292M KelpDAO exploit was an RPC data-poisoning attack, the kind that becomes possible when infrastructure trusts a single validator or RPC.

What Smart Router does

You point your application at a single endpoint and keep the providers you already use: Alchemy, Infura, Helius, QuickNode, your own nodes, or any mix of paid and free upstreams. From there, Smart Router handles the hard parts:

• Smart, method-aware routing. Every request is classified and scored across providers on latency, sync (closeness to the chain head), and availability, then sent to the best fit, never round-robin. Routing strategy is configurable, including a primary-backup mode that lets you pin a preferred node when you don't want the router making real-time choices.
• Automatic recovery. Failed requests retry on a different provider, slow ones are hedged in parallel so the first good answer wins (cutting tail latency), and an exhausted pool fails fast with a clear error. Node-down, transient, and slow-response incidents recover on their own.
• Data consistency. Smart Router ensures responses are up to date with the latest available blocks and rejects older responses to ensure no backtracking.
• Cross-provider consensus. For critical reads and writes, the same request fans out to several providers and a result is returned only once a configurable number of independent sources agree, catching a single lying or compromised provider, the failure mode behind the $292M KelpDAO exploit. Teams can also define policies that enforce different levels of quorum based on each request's security posture and value. Cryptographic verification of responses is on our Q3 roadmap.
• Block-aware, reorg-aware caching. Finalized reads are served in-process while chain-tip data is never served stale, often the single largest reduction in monthly RPC spend.
• Any chain, not just EVM. Smart Router speaks JSON-RPC, REST, gRPC, and Tendermint RPC across a maintained catalog of 67 mainnets and 64 testnets: EVM L1s and L2s, non-EVM L1s, the full Cosmos/IBC ecosystem, and Bitcoin. Adding a chain is simple.
• Observability, built in. The full request lifecycle is exposed through a built-in dashboard, Prometheus metrics, OpenTelemetry traces, and structured logs, making visible which providers underperform, which nodes are unhealthy, and where spend actually goes, the basis for renegotiating provider contracts on evidence rather than anecdote.

As BD Lead Yuval Binder puts it, "Smart Router is much more than a failover system. It surfaces issues you didn't know existed and shows which providers deliver value and which cause problems. There are far more RPC issues than teams realize, like silent incidents and inaccurate data, alongside the RPC security exposure most companies don't take seriously."

Open source, with a managed service

Smart Router's core is open source under a noncommercial license: free to download, run, contribute to, and build on, as long as it isn't used in production or commercially. The free version deploys via Docker Compose and ships the full feature set: every blockchain, cross-validation, and the built-in dashboard. An open core is how infrastructure earns trust: you can read exactly what is routing and validating your traffic, run it next to your own services, and keep full control of configuration. The repository is public (Magma-Devs/smart-router).

On why the core is open, CEO Tal Bar David says: "The signal is trust. If you're not a large organization, use it for free. Enterprises need more than the code: support, an SLA, and the assurance it's implemented correctly. Open source is how you see who we are."

Smart Router is built for every kind of enterprise: free and open source for developers, a commercial license to self-host, or a fully managed service we run for you. The open-source tier is a real entry point. Deploy in minutes, exercise the dashboard, and validate the behavior before committing. From there, you choose how production runs.

Across every tier, Smart Router is a reliability and security layer rather than a migration. It sits on top of the providers you already use, same keys and one endpoint, and makes that infrastructure resilient. Security documentation for vendor review is available in our Trust Center.

In production today

Smart Router runs in production at some of the most demanding institutions in the market: Kraken, Fireblocks, GK8 (by Galaxy), and Hypernative.

Fireblocks runs Smart Router through peak market events to maintain uptime and performance for its institutional client base. Hypernative queries data across 70+ networks through Smart Router to power real-time threat detection that has helped customers prevent more than $2B in losses. Kraken runs Smart Router to ensure reliable on-chain activities, optimize latency and validate data integrity across 130+ networks for over 1.5 million active users.

The metric we track first is success rate: the share of requests fulfilled without hitting an error. By that measure, the results are concrete:

• A 99% reduction in RPC errors at GK8: They were absorbing on the order of 5,000 errors a day that were invisible to them. Smart Router surfaced the issues, and we resolved them together.
• 100+ chains fronted at Fireblocks: Smart Router sits in front of RPC traffic across more than 100 chains for Fireblocks' 2,000+ institutional clients, coverage at the scale where a single upstream RPC incident has historically cascaded across dozens of chains at once.
• 50–70% fewer upstream RPC calls through caching: GK8 ran near-identical staging and production environments issuing the same heavy calls. Because both routed through Smart Router, shared caching cut upstream usage by more than half, and by up to 70% on Ethereum. For a large RPC bill, that's anywhere from a few thousand to hundreds of thousands of dollars a year.

The team

Smart Router is built by a new engineering team assembled to build enterprise-grade infrastructure from the ground up, headed by CTO Idan Hen. Idan spent some 16 years in a leadership role at a critical IDF intelligence unit, operating across large-scale software and DevOps platforms, then served as VP R&D of a cybersecurity startup through its acquisition, and went on to found his own company. RPC security and data integrity at institutional scale demand exactly that background. They're the foundation Smart Router is built on.

Where this is going

Smart Router is the first step. We see Magma as the Cloudflare of enterprise blockchain, and routing is where it begins. Security and observability for institutional on-chain operations follow from there.

Success a year from now, as CEO Tal Bar David frames it, is "a meaningful set of organizations whose teams can rely on fast, validated, uninterrupted access to the blockchain, and stop thinking about it."

For any serious multi-chain operation, standalone RPCs no longer make sense. In an unstable environment, you need a layer that keeps the whole application stable. That is what Smart Router is.

Get started

Magma Devs builds enterprise-grade blockchain infrastructure for companies that can't afford downtime. Its product, Smart Router, is an RPC orchestration and security layer that routes, validates, and observes RPC traffic across every provider and chain from one control plane. The project is backed by Tribe Capital, HashKey Capital, and Jump, among others.