Skip to content
Magma Devs
Services / Private Hosting

Your own RPC routing environment. Operated by Magma.

Get a dedicated, single-tenant Smart Router deployment on Magma-operated servers with managed RPC access, your existing providers and private nodes, or a hybrid of both. Magma handles agreed connectivity, upgrades, monitoring and applicable Enterprise response. Upstream ownership, usage fees and support commitments follow your agreement.

The control of a dedicated deployment, without the operational burden of running the routing layer yourself.

  • Dedicated single-tenant deployment
  • Magma-operated infrastructure
  • 24/7 Enterprise monitoring
  • SOC 2 Type II and ISO/IEC 27001

Enterprise customer

Application Services
Blockchain Operations
Internal Systems

Private Enterprise Hosting

Dedicated Smart Router
Routing & Failover
Data Integrity Controls
Observability
Managed Operations

Hosted on Magma-operated servers

Configured RPC upstreams

Provider A
Provider B
Customer-operated Node
Ethereum
Solana
Bitcoin

Customer application sends a supported RPC request

Illustrative Private Hosting architecture. Magma operates the dedicated Smart Router environment. Upstream RPC providers and customer systems remain subject to their own operational arrangements.

The challenge

You need dedicated infrastructure. You don't need another platform to operate.

Enterprise blockchain teams already manage a complex technology environment. Their applications depend on blockchain networks, RPC providers, internal nodes, monitoring systems, and operational processes.

Adding Smart Router can strengthen that infrastructure. But running another production routing layer internally also creates responsibilities.

Someone needs to deploy it. Someone needs to maintain it. Someone needs to monitor it. Someone needs to handle upgrades. And when a problem occurs outside business hours, someone needs to investigate the routing infrastructure.

Shared managed cloud removes some of that work, but a shared deployment model may not match every organization's infrastructure requirements.

Private Hosting offers a different operating model. A dedicated routing environment for your organization, operated by Magma.

Infrastructure ownership

Running a production routing service requires configuration, monitoring, deployment management, and ongoing maintenance.

These responsibilities compete with the customer's application development priorities.

Deployment requirements

Some Enterprise organizations prefer a dedicated routing environment rather than sharing a managed routing deployment with other customers.

Operational continuity

Infrastructure must be monitored and maintained over time, including during provider incidents, software changes, and network upgrades.

Dedicated infrastructure should provide more control over the environment, not more operational work for your engineering team.

A clear infrastructure model

Your own Smart Router deployment. Not shared with other Magma customers.

Private Hosting is a dedicated deployment model for Enterprise customers who want Magma to operate their Smart Router environment.

The routing infrastructure is hosted on Magma-operated servers and dedicated to that customer. This is different from the shared managed cloud service and from running Smart Router inside the customer's own infrastructure.

Dedicated routing deployment
The Enterprise customer has its own Smart Router deployment rather than sharing the same routing environment with unrelated Magma customers.
Hosted by Magma
The deployment runs on servers operated by Magma, not automatically inside the customer's own cloud account or data center.
Managed infrastructure operations
Magma operates the agreed environment, including relevant software maintenance, upgrades, monitoring, and incident response.
Independent upstream providers
The deployment can route supported requests to compatible external RPC providers and customer-operated nodes configured for the customer.

Private Hosting provides a dedicated Magma-managed routing environment. It does not automatically make every upstream provider, network connection, or blockchain node dedicated to the customer.

Customer Application

Single-tenant routing infrastructure

Dedicated Magma Smart Router Deployment
Configured Independent Upstreams
Blockchain Networks
Choose your deployment model

Shared cloud, your own infrastructure, or a dedicated environment we operate.

Different teams want different levels of infrastructure ownership. Smart Router supports more than one deployment model so organizations can choose how the routing infrastructure is operated.

Explore the differences between Shared Managed Cloud, Self-hosted, and Private Enterprise Hosting.

Private Hosting

A dedicated Smart Router deployment, operated by Magma.

Magma hosts and manages a dedicated single-tenant routing environment for one Enterprise customer.

The customer retains its application systems and compatible upstream provider strategy.

  • Dedicated routing deployment for one customer
  • Hosted on Magma-operated servers
  • Managed infrastructure and upgrades
  • Monitoring and Enterprise incident response
  • Enterprise support commitments under contract
  • Multi-chain support according to the agreement

"Dedicated infrastructure, without operating the routing layer yourself."

Customer Application

Dedicated, Magma-operated

Dedicated Magma Smart Router Deployment
Configured RPC Providers and Private Nodes
Infrastructure operator
Magma
Tenant model
Single-tenant
Monitoring
Managed Enterprise
Support
Enterprise support commitments under contract

Routing environment

Shared Managed Cloud
Shared managed model
Private Hosting
Dedicated single-tenant deployment
Self-hosted
Customer-operated

Infrastructure operator

Shared Managed Cloud
Magma
Private Hosting
Magma
Self-hosted
Customer by default

Hosted on Magma infrastructure

Shared Managed Cloud
Yes
Private Hosting
Yes, dedicated deployment
Self-hosted
No

Provider independence

Shared Managed Cloud
Supported
Private Hosting
Supported
Self-hosted
Supported

Software updates

Shared Managed Cloud
Managed under plan
Private Hosting
Magma-managed under agreement
Self-hosted
Customer responsibility

Monitoring

Shared Managed Cloud
Plan-dependent
Private Hosting
Managed Enterprise
Self-hosted
Customer responsibility unless agreed

Incident response

Shared Managed Cloud
Plan-dependent
Private Hosting
Enterprise agreement
Self-hosted
Separate agreement if applicable

Deployment control

Shared Managed Cloud
Managed service
Private Hosting
Dedicated managed environment
Self-hosted
Customer-controlled

Commercial model

Shared Managed Cloud
Plan-based
Private Hosting
Enterprise agreement
Self-hosted
Applicable license and support agreement

Deployment models shown conceptually. Specific infrastructure topology, hosting terms, supported networks, and service commitments depend on the selected plan or agreement.

One routing layer across your providers

Keep your providers. Let Magma operate the infrastructure connecting them.

Private Hosting doesn't require customers to replace the RPC providers they already use. Smart Router can operate above compatible external RPC services and customer-operated nodes.

The dedicated deployment provides the routing layer through which supported application requests reach those upstreams.

Smart Router evaluates provider availability, performance, and applicable chain freshness signals. For eligible requests, it can route around failing providers. For supported sensitive reads, independent cross-provider validation can be configured where appropriate.

The customer continues controlling its blockchain applications and financial or business logic.

Provider-independent routing

Configure compatible RPC providers and private nodes within the dedicated routing environment.

Automatic recovery

Use eligible retries and failover to reduce the impact of individual upstream failures when suitable alternatives are available.

Configurable data integrity

Apply independent cross-provider verification to supported sensitive reads according to the defined policy.

Operational visibility

Use relevant metrics and monitoring signals to understand routing behavior, provider health, errors, and supported validation outcomes.

Customer application

Dedicated hosting boundary

Dedicated Smart Router
Provider A
Provider B
Private Node

Request served

Illustrative. Cross-provider validation applies only to supported reads with an explicitly configured policy, not to every request.

One dedicated routing deployment can coordinate multiple upstream providers and supported blockchain networks without becoming the owner of the underlying blockchain services.

Fully managed routing infrastructure

We don't just host the router. We operate the environment behind it.

Running production routing infrastructure is an ongoing responsibility.

Private Hosting gives Enterprise customers a deployment model in which Magma operates the agreed Smart Router environment. The service combines the routing technology with the engineering and operational work required to maintain that environment.

Deployment
Upgrades
Monitoring
Dedicated Smart Router
Incident Response
Engineering
Operational Review
  1. 01 - Infrastructure operation

    Magma operates the dedicated routing deployment on its managed servers.

    The agreed environment and infrastructure components are managed according to the Enterprise service arrangement.

  2. 02 - Software maintenance

    Magma handles applicable Smart Router upgrades and deployment maintenance under the agreed change and release processes.

    Relevant network and software compatibility requirements are considered as part of ongoing operations.

  3. 03 - Monitoring

    Monitor the managed environment and relevant routing infrastructure signals, including provider availability, request errors, latency, and operational health.

  4. 04 - Incident response

    Provide 24/7 monitoring and incident response for eligible Private Hosting customers under their Enterprise support arrangements.

    Investigate relevant managed infrastructure issues and coordinate applicable mitigation.

  5. 05 - Engineering assistance

    Support agreed configuration, provider integration, and connectivity requirements through the applicable Enterprise engineering arrangement.

  6. 06 - Operational coordination

    Clarify issues affecting the managed routing layer and coordinate with the customer or external providers when the investigation requires it.

Private Hosting is infrastructure plus operational ownership. It is not simply a virtual machine with Smart Router installed.

All operational commitments remain subject to the Enterprise agreement.

From deployment to ongoing operations

The important part of managed infrastructure starts after deployment.

A production routing layer needs ongoing attention. Providers change behavior. Blockchains upgrade. Software requires maintenance. Operational issues must be investigated.

Private Hosting combines the deployment with an agreed operating model, so the customer does not need to manage every routing infrastructure responsibility internally.

Stage 1 - Deploy

Magma prepares the dedicated Smart Router environment according to the approved configuration and Enterprise deployment requirements.

Dedicated Smart Router
Provider A Provider B Private Node

Deployment environment prepared

Conceptual lifecycle, not a real deployment manager.

Clear ownership

We operate the routing layer. You stay in control of your business infrastructure.

A managed deployment works best when responsibilities are defined clearly.

Private Hosting changes who operates Smart Router. It does not transfer ownership of the customer's applications, signing systems, financial records, or business processes to Magma. And it does not automatically transfer responsibility for every third-party RPC provider to Magma.

The service agreement should establish the operating boundary, relevant infrastructure access, monitoring responsibilities, and escalation arrangements.

Customer responsibilities

The customer generally retains control of:

  • Application systems
  • Business logic
  • Transaction signing
  • Private keys and wallet controls
  • Internal financial records
  • Blockchain confirmation policies
  • Business-level user permissions
  • Provider contracts unless separately agreed
  • Customer application monitoring
  • Business continuity planning outside Magma's scope

Magma responsibilities

Within the agreed Private Hosting scope:

  • Dedicated Smart Router deployment
  • Routing infrastructure operation
  • Applicable software maintenance
  • Infrastructure monitoring
  • Routing-related incident response
  • Agreed configuration management
  • Technical infrastructure support

Third-party responsibilities

External RPC providers remain responsible for:

  • Their own node infrastructure
  • Their endpoint availability
  • Their supported methods
  • Their provider-side authentication
  • Their network capacity
  • Their contractual services

The blockchain network itself remains outside Magma's direct operational control.

Customer-controlled environment

ApplicationsSigning & keysFinancial records

Dedicated Magma-operated routing environment

Magma operates
Smart RouterMonitoringUpgradesIncident response

External RPC providers and customer nodes

Provider AProvider BCustomer nodes

Blockchain networks

Consensus outside Magma's control

Clear operational boundaries are part of what makes managed infrastructure dependable.

Security and trust

Dedicated infrastructure needs an infrastructure partner your security team can evaluate.

When a third party operates infrastructure used by critical blockchain applications, the provider's own security and operational practices matter.

Magma Devs has completed a SOC 2 Type II examination and holds ISO/IEC 27001 certification. Our security program covers relevant areas such as access management, infrastructure monitoring, incident response, change management, and vendor oversight.

Qualified customers and prospects can request relevant documentation through Magma's Trust Center.

SOC 2 Type II

Independent examination of Magma's applicable security controls over an audit period.

ISO/IEC 27001

Certification of Magma's information security management system within its defined scope.

Security documentation

Relevant reports, certificates, security information, and vendor review materials are available through the appropriate request process.

What Enterprise buyers can review

  • Access management approach
  • Security governance
  • Infrastructure controls
  • Monitoring and alerting
  • Operational change management
  • Incident response processes
  • Vendor management
  • Applicable security documentation

Magma's security credentials support your vendor assessment. They do not automatically certify the security or regulatory compliance of every customer application, provider, or deployment configuration.

Your providers, one dedicated routing layer

A private deployment shouldn't lock you into one RPC vendor.

Enterprise blockchain environments often use several independent RPC providers. Different vendors may be better suited for different blockchain networks, methods, throughput requirements, or operational needs. Some organizations also operate their own nodes.

Private Hosting allows customers to retain this approach while moving the routing and orchestration layer into a dedicated Magma-managed environment.

Smart Router sits above the compatible upstreams the customer selects. It handles supported provider routing, recovery, and observability within the configured infrastructure.

Retain your provider relationships

Keep compatible third-party RPC vendors and customer-operated nodes as part of your blockchain access strategy.

Reduce single-provider exposure

Use appropriate eligible alternatives instead of relying on one endpoint for every critical request.

Operate through one routing layer

Bring supported multi-chain traffic into a shared orchestration model within the dedicated customer deployment.

Customer Application
Dedicated Magma Smart Router
Provider group AProvider group BCustomer nodes
Supported Blockchain Networks

Private Hosting changes where Smart Router runs and who operates it. It does not automatically replace your upstream providers or transfer all provider contracts to Magma. The provider commercial model depends on the Enterprise agreement.

Built for enterprise operations

For companies that want dedicated RPC infrastructure without operating it themselves.

Private Hosting can be relevant to organizations whose blockchain connectivity is business-critical and whose deployment requirements make a dedicated managed environment preferable.

Custody Platforms

Dedicated connectivity beneath critical custody workflows.

Custody platforms depend on blockchain information and transaction submission infrastructure while maintaining their own key management, signing, and asset controls.

Private Hosting allows the RPC routing layer to be operated by Magma in a dedicated Enterprise environment.

Related industry: Custody Platforms

Exchanges

Managed routing infrastructure across complex blockchain operations.

Exchanges operate across multiple networks, providers, and critical RPC workloads.

A dedicated routing deployment can provide a clear operational boundary while Magma manages the agreed infrastructure and incident response.

Related industry: Exchanges

Wallet Infrastructure

A dedicated routing foundation beneath your wallet platform.

Wallet infrastructure providers can keep their wallet APIs, signing systems, and customer management while using a separate Magma-managed routing deployment for supported blockchain connectivity.

Related industry: Wallet Infrastructure

Financial Institutions

Dedicated blockchain connectivity with clear operational responsibility.

Financial institutions may require closer review of technology dependencies, vendor responsibilities, security documentation, and deployment architecture.

Private Hosting provides a dedicated routing environment and an Enterprise operating model that can be evaluated as part of those requirements.

Related industry: Financial Institutions

The appropriate hosting model depends on the organization's infrastructure requirements, security review, expected workload, and commercial agreement.

From requirements to managed infrastructure

Your providers and networks are already there. We help build the dedicated routing environment around them.

Private Hosting onboarding starts with understanding the infrastructure the customer already operates. The implementation approach depends on the supported networks, configured providers, expected traffic, security requirements, and deployment arrangements.

Magma works with the customer to prepare the routing environment, configure compatible upstreams, validate the agreed behavior, and coordinate the transition to production use.

  1. 1 Review
  2. 2 Deploy
  3. 3 Validate
  4. 4 Operate
  1. 01 - Review the requirements

    Discuss the required networks, RPC methods, provider connections, deployment needs, traffic expectations, and operational constraints.

  2. 02 - Prepare the dedicated environment

    Magma configures the agreed Smart Router deployment on its managed infrastructure.

  3. 03 - Connect and validate

    Compatible provider endpoints and customer-operated nodes are configured.

    Relevant health checks, supported methods, and agreed routing behavior are reviewed.

  4. 04 - Review go-live and operations

    The customer and Magma coordinate the production readiness process, confirm responsibilities, and establish the ongoing managed service arrangement.

Deployment readiness depends on the customer's requirements, available upstream access, infrastructure prerequisites, and agreed validation scope.

The Onboarding service may target one-day setup for supported, prepared environments. Dedicated Enterprise deployments with special requirements may involve additional technical or commercial work.

Explore our Onboarding service
Operating blockchain infrastructure at scale

A dedicated deployment model, built on a routing platform already trusted in production.

Smart Router operates in production environments supporting leading digital asset infrastructure companies, including Kraken, Fireblocks, Galaxy, and Hypernative.

These companies rely on dependable blockchain access across demanding networks and provider environments. That production experience supports Magma's ability to build and operate the routing infrastructure for Enterprise customers.

KrakenFireblocksGalaxyHypernative

These logos show production use of Smart Router. Deployment models differ by customer.

Fireblocks

Designed to fit enterprise blockchain infrastructure without replacing its providers.

Fireblocks uses Smart Router as a reliability and orchestration layer above its existing blockchain RPC infrastructure.

Magma's published case study demonstrates that Smart Router can integrate with existing Enterprise provider environments and support demanding blockchain workloads.

For Private Hosting prospects, the relevant principle is the separation between the customer's application and providers and the routing layer that Magma can operate.

This case study illustrates product architecture and production credibility. It is not evidence that Fireblocks specifically uses Magma Private Hosting.

Read the Fireblocks case study
Application
Smart Router routing layer
ProviderProviderInternal
Conceptual. Not a customer topology.
Understand the difference

Managed doesn't always mean dedicated.

Magma offers more than one way to consume Smart Router as a managed service. The important distinction is the infrastructure model.

RPC as a Service is the managed cloud offering where customers can use Magma's shared routing infrastructure under the applicable plan.

Private Hosting is the Enterprise service where Magma operates a dedicated Smart Router deployment for one customer on Magma-managed infrastructure.

Both can provide managed routing. But their deployment boundaries, service arrangements, and commercial terms are different.

RPC as a Service

Deployment
Shared managed cloud routing environment.
Customer receives
Managed Smart Router connectivity under the applicable plan.
Operations
Magma operates the managed cloud service.
Support
Defined by the selected plan.
Best aligned with
Customers whose workloads and requirements fit the shared managed environment.
About RPC as a Service

Private Hosting

Deployment
Dedicated single-tenant Smart Router environment on Magma-operated infrastructure.
Customer receives
A separately deployed and managed Enterprise routing environment.
Operations
Magma operates the agreed deployment, including applicable upgrades, monitoring, and incident response.
Support
Enterprise support arrangements under the customer agreement.
Best aligned with
Organizations that require a dedicated managed routing deployment and a defined Enterprise operating model.

The distinction concerns the hosting and operation of Smart Router, not ownership of every underlying blockchain node or RPC provider.

Compare plans and deployment options
On the roadmap

More deployment flexibility for complex Enterprise environments.

We're extending Private Hosting to support a wider range of Enterprise infrastructure requirements. The goal is to give customers more options for where dedicated routing infrastructure runs and how deployment environments can be organized.

Planned capability 1

More region choices

Expand the available deployment region options for Enterprise customers with relevant latency, resilience, or infrastructure requirements.

Planned capability 2

Dedicated regional environments

Support additional dedicated deployment configurations across selected regions, subject to technical feasibility and commercial scope.

Planned capability 3

Greater deployment visibility

Improve customer visibility into relevant managed infrastructure status and deployment changes.

Planned capabilities. Availability, scope, and deployment regions may change.

Frequently asked questions

Private Hosting is a dedicated, single-tenant Smart Router deployment operated on Magma-managed servers for one Enterprise customer. Magma operates the agreed routing infrastructure, including relevant maintenance, monitoring, upgrades, and incident response under the applicable agreement.

No. Shared managed cloud uses Magma's shared routing service. Private Hosting provides a separately deployed Smart Router environment dedicated to one Enterprise customer.

Private Hosting runs on infrastructure operated by Magma. It is not automatically deployed inside the customer's own cloud account or data center. Specific deployment requirements are reviewed during the Enterprise engagement.

No. Private Hosting is hosted and operated by Magma. Customers who want to run Smart Router inside their own infrastructure can discuss self-hosted deployment under the applicable license and service agreement.

The service provides dedicated routing infrastructure for one Enterprise customer on Magma-operated servers. Exact physical or virtual resource allocation, hardware specifications, and infrastructure topology are subject to the agreed deployment architecture. Do not assume bare-metal exclusivity unless explicitly contracted.

Not automatically. Private Hosting concerns the Smart Router routing environment. Compatible external RPC providers and customer-operated nodes can remain upstream. Dedicated third-party node services, if needed, require separate technical and commercial arrangements.

Yes. Smart Router is designed to operate above compatible external RPC providers and private nodes. Customers can retain their upstream provider strategy, subject to the supported network, interface, and method configuration.

Provider contracts, usage fees, procurement, and billing responsibilities depend on the Enterprise agreement. Private Hosting should not automatically be understood as including all third-party RPC provider costs.

Private Hosting is specifically a managed Smart Router deployment, not a general-purpose blockchain node hosting service. Any additional node infrastructure requirement needs separate technical review and an explicit agreement.

Specific regional requirements can be discussed during Enterprise scoping. Available locations and commitments must be confirmed in the agreement. Do not assume any requested region is already generally supported.

No universal data residency guarantee is made on this page. Data location, relevant processing, logging, third-party upstreams, and applicable controls must be evaluated against the customer's requirements and the agreed architecture.

A dedicated routing environment provides a different deployment and isolation model. Security depends on the full architecture, configuration, operational processes, access controls, and external dependencies. Private Hosting should not be marketed as automatically secure against every risk.

It provides a dedicated Smart Router deployment. Some underlying infrastructure, networks, external provider services, or supporting systems may have separate tenancy and operational characteristics. Exact isolation boundaries are defined by the deployment architecture and agreement.

Magma offers 24/7 monitoring and incident response under applicable managed Enterprise agreements, including Private Hosting arrangements with that coverage. Exact escalation, severity definitions, response commitments, and operational scope are established contractually.

Enterprise support and service commitments are defined in the applicable agreement. This page does not publish universal response times, recovery guarantees, or a standard uptime commitment.

Magma manages applicable software upgrades and infrastructure maintenance for the Private Hosting environment according to the agreed operational and change-management arrangements.

Configuration policies and change responsibilities are agreed as part of the Enterprise deployment. The customer can retain decision-making authority over its provider strategy and routing requirements, while Magma operates the agreed routing environment.

Private Hosting provides a managed routing deployment. Specific management interfaces, configuration controls, and access capabilities depend on the available product and service arrangement. Do not assume that planned self-service configuration or audit features are already generally available.

Yes. Smart Router supports 284 blockchain networks across multiple protocol families and interfaces. The customer's Private Hosting configuration must include the relevant supported networks and compatible upstream providers.

Smart Router supports configurable cross-provider validation for eligible sensitive reads. The feature requires suitable provider groups and a defined policy. It is not automatically applied to every request and does not guarantee absolute blockchain data correctness.

For supported requests, Smart Router can route through another eligible healthy provider when a suitable alternative is available. If no suitable provider exists, some requests may fail. Private Hosting does not guarantee recovery from every provider or blockchain outage.

Magma is responsible for the managed infrastructure and incident response services defined in the Enterprise agreement. Customer applications, third-party providers, blockchain networks, and other external systems remain subject to their own operational ownership.

Private Hosting is a managed deployment and operations service. Dedicated Engineering focuses on separately scoped integrations, custom features, and technical changes. An Enterprise customer may use both services, but the scope and commercial terms are defined in the agreement.

Magma reviews the required networks, upstream providers, interfaces, deployment needs, and critical workloads. The team prepares the dedicated routing environment, configures compatible endpoints, validates relevant behavior, and coordinates readiness for production according to the agreed onboarding scope.

It may be relevant to institutions that want a dedicated routing environment, managed operations, and a clear vendor responsibility model. Suitability depends on the institution's technical, security, regulatory, and commercial requirements. Private Hosting does not automatically establish regulatory compliance.

Magma has completed a SOC 2 Type II examination and holds ISO/IEC 27001 certification. Relevant documentation is available through the Trust Center request process.

A transition can be reviewed as part of an Enterprise engagement. Required configuration, provider connectivity, application changes, migration steps, and any applicable service interruption risks must be assessed. A universally automatic or zero-downtime migration is not promised.

Private Hosting pricing and capacity are defined through an Enterprise commercial agreement. Do not assume the shared Cloud Pro pricing model applies unchanged to a dedicated deployment.

Contact Magma with your supported blockchain networks, provider environment, expected traffic, infrastructure requirements, and operational expectations. Our team can review the requirements and discuss an appropriate Private Hosting architecture and Enterprise agreement.
Your infrastructure. Our operational responsibility.

What if you could have a dedicated RPC routing environment without running it yourself?

Tell us which blockchain networks, providers, private nodes, and critical workloads your infrastructure depends on.

We'll help you evaluate whether Private Hosting fits your architecture, what the dedicated deployment would need, and how Magma could take responsibility for operating the routing layer.

Keep your applications and provider relationships. Get a dedicated Smart Router environment with an experienced infrastructure team behind it.

A dedicated routing environment. The providers you choose. Magma running the infrastructure behind it.