Your blockchain infrastructure should meet the standards of the institution behind it.
Financial institutions need reliable blockchain access and clear operating responsibilities. Magma offers managed RPC access, Bring Your Own Providers and institution-operated nodes, or hybrid connectivity, with routing, eligible data checks and visibility in one platform. Provider coverage, hosting and operations are defined in your Enterprise agreement.
Keep your systems and providers. Strengthen the blockchain connectivity beneath them.
- SOC 2 Type II
- ISO/IEC 27001
- Private Enterprise Hosting
- 284 Supported Blockchain Networks
Financial Institution
Institution-controlledDedicated Magma Smart Router
Dedicated managed deploymentRPC Infrastructure
- Provider AHealthy
- Provider BHealthy
- Institution-operated NodeHealthy
Blockchain Networks
An institutional application sends a blockchain RPC request.
Blockchain infrastructure introduces risks your existing technology controls still need to manage.
Financial institutions spend years building mature technology operations.
Critical applications are monitored. Vendors are assessed. Security responsibilities are defined. Incidents are investigated and documented.
Blockchain integration should not become an exception to those standards.
But the RPC layer introduces a different kind of dependency.
A blockchain application may rely on several external providers for transaction status, balances, contract data, and network access.
Those providers can fail independently or experience shared infrastructure problems.
A node may stay online while serving outdated blockchain state.
And when an incident occurs, it may be difficult to determine what failed, which requests were affected, and whether the problem reached the institution's own systems.
Third-party infrastructure risk
Critical blockchain operations can depend on external RPC providers whose availability and performance the institution does not directly control.
Data that looks valid but isn't trustworthy
An RPC provider can return a technically successful response while serving outdated or conflicting blockchain information.
Evidence scattered across systems
After an incident, information may be spread across provider dashboards, application logs, and monitoring platforms, making a complete investigation harder.
An institution shouldn't have to lower its operational standards to connect to a blockchain.
Control the environment. Verify the data. Understand the infrastructure.
Magma brings together three capabilities that matter when blockchain connectivity becomes part of critical financial operations.
CONTROL
Dedicated deployment
Dedicated infrastructure with clear operational ownership.
Private Hosting provides a dedicated single-tenant Smart Router deployment on Magma-operated infrastructure.
The institution gets its own routing environment rather than using the same shared router deployment as other customers.
Magma manages the applicable infrastructure, upgrades, monitoring, and incident response under the Enterprise agreement.
VERIFY
Independent data checks
Critical blockchain decisions need more than one unchecked source.
Smart Router supports freshness-aware routing and configurable cross-provider verification for eligible reads.
Infrastructure teams can require agreement across independent provider groups before relying on selected sensitive blockchain responses.
UNDERSTAND
Operational telemetry
Know how your infrastructure behaved when something went wrong.
Smart Router provides operational telemetry around configured providers, request outcomes, retries, latency, and supported data validation behavior.
These signals can help institutions investigate incidents and prepare infrastructure-related evidence for internal review.
Institutional confidence comes from knowing how the infrastructure is deployed, how its data is checked, and how its behavior can be investigated.
Your institution's RPC routing environment. Operated by Magma.
For financial institutions, infrastructure architecture is a purchasing and operational decision, not simply a technical preference.
Shared cloud services can be appropriate for some workloads.
Other environments require a dedicated deployment, clearer operational boundaries, and specific support arrangements.
Magma's Private Hosting provides a dedicated, single-tenant Smart Router deployment on servers operated by Magma.
It allows the institution to keep its application systems and provider strategy while using a separately deployed RPC reliability layer managed under the Enterprise agreement.
Hosting boundary: Dedicated to one Enterprise customer, on Magma-operated servers
Operated by MagmaDedicated Magma Smart Router Deployment
Single-tenant routing deployment, operated by Magma
A separately deployed routing environment for your institution, managed by Magma under the Enterprise agreement.
What Private Hosting provides
Dedicated routing deployment
A Smart Router environment dedicated to one Enterprise customer rather than shared with unrelated Magma customers.
Managed operations
Applicable deployment maintenance, software upgrades, infrastructure monitoring, and incident response handled by Magma under the service agreement.
Provider flexibility
Connect compatible external RPC vendors and institution-operated blockchain nodes according to the supported network and interface configuration.
Operational visibility
Use available router metrics and monitoring signals to understand provider health, routing behavior, and request outcomes.
What the institution keeps
The institution remains responsible for:
- Financial systems
- Internal authorization
- Signing and private keys
- Business continuity planning
- Financial accounting
- Regulatory obligations
- Data classification
- Internal security policy
- Application-level access controls
A dedicated routing environment gives you a clearer infrastructure boundary without requiring you to replace the business systems and blockchain providers you already operate.
Discuss Private HostingA successful RPC response is not proof that the data is correct.
Financial institutions use blockchain information to support operational and financial processes.
Balances, transaction receipts, contract state, and network status may influence systems that move assets, reconcile records, or monitor exposure.
A provider can be online, responsive, and wrong.
It may be behind the current chain state.
It may disagree with another independent provider.
For eligible sensitive reads, Smart Router can compare responses across different RPC sources and require configured levels of agreement before returning a corroborated answer.
Cross-provider agreement improves confidence in selected data inputs. It does not establish absolute truth, automatically prove blockchain finality, or replace the institution's accounting and reconciliation rules.
Explore Data Integrity & ReconciliationFinancial Application
balance read @ fixed block
Magma Smart Router
Policy: 2 matching, ≥ 2 independent groups- Provider AGroup A
…
- Provider BGroup B
…
- Provider CGroup C
…
Select a scenario to evaluate the configured policy.
Illustrative cross-validation policy for eligible deterministic reads. Verification behavior depends on the selected policy, provider groups, method, block context, and upstream availability.
Freshness-aware provider selection
Monitor observed chain height and avoid eligible providers that fall behind the acceptable freshness policy.
Independent cross-provider verification
Configure quorum rules for supported sensitive reads, including agreement across distinct provider groups where required.
Data disagreement visibility
Use available validation outcomes, response metadata, and metrics to investigate conflicting provider answers.
One provider's outage should not automatically become your institution's outage.
Financial institutions may rely on different RPC providers for different blockchains, data requirements, or operating environments.
Those providers introduce third-party dependencies.
Adding independent upstreams can reduce concentration risk, but the institution still needs a way to monitor provider health and decide where eligible traffic should go when conditions change.
Smart Router continuously evaluates configured providers and supports automatic routing decisions, retries, and failover for eligible requests.
This helps reduce the effect of individual provider disruptions when suitable alternatives remain available.
Financial Application
Magma Router
Normal routing- Provider AHealthy
- Provider BHealthy
- Private NodeHealthy
All configured upstreams healthy.
Reduce single-provider exposure
Use compatible upstreams from independent vendors and private nodes where appropriate.
Route according to provider health
Consider relevant availability, error, latency, and freshness signals rather than treating every reachable endpoint as equally suitable.
Understand recovery behavior
Use operational metrics to distinguish upstream failures from requests that were recovered through retries or alternative providers.
The objective is not to promise that no infrastructure component will ever fail. It is to make critical blockchain connectivity more resilient and its behavior easier to understand.
The question isn't only whether the system recovered. It's whether your team can explain what happened.
Operationally mature institutions need to understand failures from several perspectives.
An infrastructure engineer wants to know which provider failed.
An operations leader wants to know whether critical requests continued working.
A risk reviewer may need to understand the available technical evidence supporting the investigation.
Explore three illustrative infrastructure scenarios.
Illustrative incident scenario
09:15:00
Provider A begins returning errors.
09:15:01
Smart Router identifies an eligible alternative.
09:15:02
Requests recover through Provider B.
09:18:00
Provider A returns to a healthy state.
Press Replay to run the scenario.
Evidence categories
What your investigation should establish
Illustrative incident scenario
- Affected blockchain
- …
- Time window
- …
- Involved providers
- …
- Observed failure mode
- …
- Router response
- …
- Client-facing outcome
- …
- Available validation signals
- …
- Items requiring further investigation
- …
An incident review needs more than a provider status page.
When an important blockchain infrastructure dependency fails, institutions need to understand the technical sequence of events.
Which upstream provider experienced the problem?
Did the routing layer recover the requests?
Was data returned by a provider that had fallen behind the blockchain?
Did the failure reach the application?
And what technical information remains available to support the investigation?
Smart Router provides operational metrics, traces, and logs that can help answer parts of these questions.
These signals can be used alongside the institution's application monitoring, incident management processes, and internal control records.
Provider health and availability
Relevant health signals, upstream errors, latency, and freshness measurements.
Routing and recovery
Retries, failover-related signals, and observed request outcomes.
Data validation
Available cross-validation results, mismatch metrics, and relevant response metadata for configured sensitive reads.
Customer-facing impact
Client-facing request measurements that can support an assessment of whether upstream problems affected application requests.
- 01
Infrastructure Events
Provider errors, latency, freshness, disagreements
- 02
Smart Router Telemetry
Metrics, traces, logs, validation signals
- 03
Institutional Operations
Monitoring, engineering investigation, incident response
- 04
Risk and Review Processes
Technical findings, vendor discussions, internal controls
Operational telemetry provides the foundation for a stronger investigation. It does not replace a documented incident process or automatically produce a complete audit package.
Magma can provide the infrastructure signals it collects and the agreed operational support. The institution determines the required review scope, evidence sufficiency, record retention, and regulatory reporting obligations.
Blockchain connectivity belongs in the conversation about technology risk.
Financial institutions already manage critical technology dependencies through established governance and risk frameworks.
Where blockchain infrastructure supports relevant financial activities, RPC providers and routing services can become part of that technology dependency landscape.
For institutions subject to applicable requirements, operational resilience, third-party risk management, incident handling, and the ability to support internal reviews are important considerations.
In the European Union, frameworks such as DORA and MiCA may be relevant to some digital asset and financial activities, depending on the institution, service, and applicable regulatory scope.
Magma helps provide technical capabilities and operational visibility that can support related infrastructure controls.
It does not determine whether an institution is compliant.
- 01
Third-party Infrastructure
- 02
Technical Resilience Controls
- 03
Operational Evidence
- 04
Institution-owned Risk & Compliance Process
Owned by the institution
Third-party dependency visibility
Understand which RPC providers and routing infrastructure support relevant blockchain operations.
Operational resilience
Reduce the impact of eligible provider failures and establish monitoring and response processes.
Incident documentation
Use available infrastructure measurements and investigation findings to support internal and external review processes.
The institution owns its compliance obligations. Magma helps strengthen the infrastructure and technical evidence supporting its operations.
Your infrastructure provider should be ready for your security review.
Choosing a technology partner for critical blockchain infrastructure requires more than evaluating its product features.
Financial institutions also need to understand the provider's security practices, operational processes, and supporting documentation.
Magma Devs has completed a SOC 2 Type II examination and holds ISO/IEC 27001 certification.
Our Trust Center provides information about Magma's security program and a path for qualified customers and prospects to request relevant assurance documents.


- SOC 2 Type II
- Independent examination of applicable security controls over an audit period.
- ISO/IEC 27001
- Certification of Magma's information security management system within its defined scope.
- Security documentation
- Available materials include the applicable security package, supporting policies and documents, and vendor review information under the appropriate request process.
What your review team can explore
- Access management approach
- Security governance
- Infrastructure controls
- Secure development practices
- Monitoring and incident response
- Vendor management approach
- Relevant assurance documentation
Magma's certifications and documents support your evaluation of us as a technology provider. They do not automatically certify the regulatory compliance of your own applications or operations.
Built on operational experience with companies that already depend on blockchain connectivity at scale.
Magma Smart Router operates in production environments supporting leading digital asset infrastructure companies.
These include Kraken, Fireblocks, Galaxy, and Hypernative.
Their blockchain workloads require reliable provider access, multi-chain infrastructure, and operational visibility.
This production experience supports Magma's approach to infrastructure reliability for organizations with demanding technology requirements.
Run in production by













Resilience when critical blockchain infrastructure is disrupted.
Fireblocks provides digital asset infrastructure used by institutional customers across a broad range of blockchain networks.
During Ethereum's Fusaka upgrade on December 3, 2025, its Ethereum RPC provider pool experienced disruption, while other endpoints fell behind the chain.
Magma Smart Router routed eligible requests toward healthier providers and helped maintain service continuity.
Numerical customer outcomes are withheld pending measurement verification and customer approval.
The example demonstrates how an independent routing layer can strengthen operational resilience when upstream providers experience disruption.
Provider disruption
Provider measurements require verification
Result withheld
No verified customer uptime result
Critical infrastructure should be designed for provider failures, with enough visibility to understand how it responded.
Read the Fireblocks case study
Another reliability layer for global blockchain operations.
Kraken integrated Magma Smart Router into its production environment to strengthen routing, resilience, and data accuracy across existing blockchain infrastructure.
The partnership demonstrates Magma's experience operating alongside mature digital asset technology systems.
Read the Kraken case studyCritical blockchain infrastructure needs an owner, not another dashboard.
A routing layer is valuable only if it is configured correctly, monitored, updated, and supported when conditions change.
Blockchain networks upgrade.
RPC providers change behavior.
Methods and interfaces evolve.
Incidents require investigation and decisions.
Financial institutions can operate Smart Router within their own infrastructure, or choose a managed service model under which Magma operates the routing deployment.
For eligible Enterprise engagements, Magma can provide a dedicated infrastructure environment, ongoing monitoring, technical support, and incident response according to the agreed responsibilities.
Managed infrastructure operations
Run and maintain the applicable Smart Router deployment, including supported infrastructure upgrades and monitoring.
Dedicated engineering support
Assist with supported network onboarding, provider integration, routing configuration, and institution-specific technical requirements.
Enterprise incident response
Provide operational response and investigation assistance under the agreed support and escalation arrangements.
The institution retains
- Application ownership
- Financial authorization
- Signing and custody
- Business controls
- Regulatory decisions
- Internal risk management
- Accounting and reconciliation
Magma can operate
- Smart Router deployment
- Supported provider orchestration
- RPC reliability controls
- Relevant infrastructure monitoring
- Routing-related incident response
- Agreed infrastructure maintenance
The goal is clear operational responsibility for the blockchain connectivity layer, without handing over control of the institution's financial systems.
A reliable foundation for institutional on-chain operations.
Financial institutions may connect to blockchain networks for different business reasons.
The underlying applications can be very different, but they often share the same requirement: dependable blockchain access and a clear way to manage infrastructure risk.
Digital asset operations
Keep critical asset-related workflows connected.
Institutional digital asset applications depend on blockchain data and transaction connectivity.
Magma can strengthen the RPC layer underneath those applications while the institution maintains its own custody, transaction policy, and accounting controls.
High AvailabilityBlockchain data used in financial controls
Improve confidence in the data entering financial systems.
Balance information, transaction receipts, and contract-state data may support internal financial processes.
Magma offers configurable verification for supported sensitive reads, helping reduce dependence on any one provider's answer.
The institution retains responsibility for reconciliation, accounting, and policy enforcement.
Data Integrity & ReconciliationIncident and third-party review
Understand the infrastructure behind important operational events.
Available routing telemetry, health measurements, and validation signals can help technical and risk teams investigate problems involving blockchain RPC dependencies.
These signals support, rather than replace, the institution's incident and vendor management processes.
Audit & Incident EvidenceMore control and evidence for institutional blockchain operations.
We're expanding the infrastructure capabilities available to customers that need deeper operational visibility, stronger review processes, and additional control over their blockchain connectivity.
- Planned 1
Structured audit evidence packages
Create more standardized exports supporting relevant operational resilience, incident review, and financial control processes.
- Planned 2
Access and configuration audit logs
Provide more complete historical records of relevant platform access and configuration changes, including API access to those records where supported.
- Planned 3
Provider SLA scorecards
Help customers review available provider performance information against agreed operational expectations.
- Planned 4
Enhanced incident analysis
Make it easier to turn available operational signals into structured incident findings and summaries.
- Planned 5
More private deployment flexibility
Explore additional deployment region and configuration options for enterprise infrastructure requirements.
Planned capabilities. Scope, delivery, and availability may change.
Frequently asked questions
Would your current RPC infrastructure stand up to your institution's technology risk review?
Tell us which blockchain networks, providers, and critical operations your institution depends on.
We'll help you evaluate the reliability, deployment model, provider dependencies, and operational visibility of your existing RPC environment.
Whether you are building a new blockchain capability or strengthening one already in production, Magma can help you design a more dependable connectivity layer.
Keep control of your financial systems. Bring institutional discipline to the blockchain connectivity beneath them.


