Blockchain infrastructure your risk team can sign off on
Smart Router is one control plane in front of the RPC providers you already use. It routes across them, cross-validates the data your systems act on, and logs every response as evidence for your risk reviews.
In production behind Kraken, Fireblocks, Hypernative and GK8. $8T+ in activity across client platforms.
One record per response: provider, latency, validation result, timestamp.
Smart Router runs in production for
Provider Tracker
Provider outages are not hypothetical
We publish a normalized, continuously updated feed of incidents across the major RPC providers - public, and free to check against your own vendor list before you take our word for any of this.
Your chain data is a third-party dependency
Digital-asset services depend on RPC data from third-party providers. For a regulated institution that is an ICT third-party dependency like any other: concentration risk on a single provider, failure modes outside your own monitoring, and unvalidated data feeding regulated workflows. It sits in scope of the same reviews as the rest of your critical vendor path.
Who this is for
Banks and bank-owned custodians
Digital-asset services under existing operational-resilience obligations.
Regulated custodians
Client assets, third-party risk reviews, and audit evidence on demand.
Exchanges and brokers
Vendor registers, concentration limits, incident attribution.
Regulated fintechs and payment firms
Stablecoin rails running inside a licensed perimeter.
What Smart Router does
Three things a risk function asks about, answered by one layer in front of the providers you already use.
Validate the data you act on
Cross-provider validation for balances, confirmations and transaction status. Responses are checked against independent sources before your systems act on them.
Uptime without provider concentration
Route every request across independent providers and your own nodes from one control plane. No single provider stays a critical dependency, and one provider going down stops being your outage.
Evidence for audits and reviews
Latency, failover events, validation results and provider health, logged per response and exportable. Resilience questions get answered with data instead of recollection.
Deploy inside your perimeter
Self-hosted or single-tenant dedicated. SOC 2 Type II compliant and ISO/IEC 27001 certified, DPA available, full security package under NDA.
The evidence a risk review asks for, in a few clicks
Every provider response is logged as it happens, so reporting is an export, not a project.
Third-party risk review pack
PDFCSVTamper-evident+
Provider inventory, request share, validation results and incident history for a sampled period, in the form a vendor-risk reviewer works from.
Incident attribution bundle
JSONTimeline+
Everything on one incident: which providers were serving, what each returned, when failover happened, and which workflows were affected.
Provider performance report
PDFCSV+
Per-provider uptime, latency and disagreement rates, feeding annual vendor due diligence reviews.
DORA and MiCA
Where this sits in your regulatory obligations
In the EU these expectations are already written down. Magma supports them with evidence produced continuously rather than reconstructed. The compliance determination stays yours.
ICT third-party register
DORA expects an inventory of the third parties serving critical functions. Per-provider request share, criticality and substitutability come from live routing rather than a spreadsheet someone maintains by hand.
Concentration risk and incident reporting
Routing across independent providers and your own nodes reduces the exposure DORA asks you to limit. Per-response attribution names the provider behind an incident within hours, not after the fact.
MiCA record-keeping
A continuous record of the chain data your regulated workflows acted on, and whether it validated - exportable on your own retention schedule, inside your own environment.
Frequently asked questions
Does this replace our RPC providers?+
No. Smart Router routes across the providers you already contract with, plus your own nodes. Your provider relationships, contracts and data agreements stay exactly as they are.
Is the Provider Tracker free to use?+
Yes. It is public, needs no account, and covers the major RPC providers. Check it against your own vendor list before you take our word for any of this.
Do our engineers have to change how they make RPC calls?+
No. Custody, settlement, treasury and reporting keep their existing RPC clients. There is no SDK to adopt and no change to how your services make calls - Smart Router sits one hop in front of the providers you already use.
Who holds the provider contracts and credentials?+
You do. The pool is the providers you already contract with, plus your own nodes, and contracts, credentials and data agreements stay yours. Smart Router runs inside your perimeter, so provider credentials and request logs never leave it.
What exactly gets cross-validated?+
Balances, confirmations and transaction status are checked against independent sources before your systems act on them. Every check is logged per response, including each case where providers disagreed.
What happens if every provider is down?+
Smart Router forwards requests, it does not sync the chain, so an empty pool has nothing behind it. A backup tier takes over if configured. It removes single-provider risk, not the need for more than one provider.
Where does our data live?+
Self-hosted and single-tenant dedicated deployments are supported. Credentials, request path, logs and metrics stay inside your infrastructure. The architecture never requires Magma to retain your data.
Is this in production, or a roadmap item?+
In production. Smart Router runs behind Kraken, Fireblocks, Hypernative and GK8, with $8T+ in activity across client platforms.
Can you satisfy our vendor security review?+
SOC 2 Type II compliant and ISO/IEC 27001 certified. The security package includes the SOC 2 report, ISO certificate, DPA, penetration test summary, subprocessor list and a pre-filled CAIQ, available under NDA.
Does this make us compliant with DORA or MiCA?+
No tool does. Your compliance programme and your regulator determine your obligations and how you meet them. What this adds underneath is a continuous record of which provider served each response and whether the data validated, which is the evidence those reviews ask for.