Skip to content
Magma Devs
Services / Dedicated Engineering

Your blockchain roadmap shouldn't be limited by your RPC infrastructure.

Magma engineers help Enterprise teams integrate supported chains with Magma-managed RPC access, existing providers and private nodes, or a hybrid configuration. Scope chain specifications, provider compatibility and Smart Router extensions around your requirements without rebuilding the common connectivity foundation.

Your requirements. Our platform expertise. Engineering work designed around your infrastructure.

  • Custom features & integrations
  • Multi-chain engineering
  • Enterprise infrastructure expertise
  • 284 Supported Blockchain Networks
Customer requirement

New Blockchain Integration

  • Chain interface
  • RPC providers
  • Required methods
  • Operational requirements
Magma engineering
  1. Review
  2. Design
  3. Implement
  4. Validate
  • Network interface
  • Provider availability
  • Method compatibility
  • Routing requirements
Smart Router environment
Smart Router
Network 1Network 2New
Provider AProvider BProvider C

Existing infrastructure: Smart Router serving two supported networks

Illustrative engineering engagement. Actual implementation, validation, ownership, timelines, and deployment requirements are defined in the agreed scope.

The challenge

Your next infrastructure requirement shouldn't become another product your team has to build.

Enterprise blockchain systems rarely stand still.

A new network becomes a business priority. A customer needs access through a specialized RPC provider. An internal node requires a different integration approach. A production workload exposes an edge case that the default routing configuration doesn't fully address.

Each requirement may be reasonable on its own. But together, they create a growing engineering backlog around infrastructure your customers never see.

Your team must investigate blockchain behavior, build or adapt integrations, test them against real endpoints, and take responsibility for maintaining the result.

That work can pull experienced engineers away from the applications and services that actually differentiate your business.

New networks introduce unfamiliar interfaces

Every blockchain can bring different APIs, methods, provider options, and operational requirements.

The integration may require infrastructure work beyond adding another endpoint URL.

Provider differences create hidden complexity

Two RPC vendors supporting the same blockchain may behave differently across methods, rate limits, authentication, archive access, or response handling.

Your infrastructure must account for those differences.

Custom requirements become maintenance responsibilities

An internal workaround may solve a short-term issue.

But somebody must test it, deploy it, document it, and keep it working as networks and provider APIs evolve.

Your infrastructure shouldn't need a new internal engineering project every time the business needs another blockchain capability.

Engineering built around your requirements

From new blockchain networks to the integration your infrastructure actually needs.

Magma's engineering services focus on Smart Router and the blockchain connectivity layer surrounding it.

Rather than selling a fixed menu of generic development services, we evaluate requirements against the platform's architecture, supported interfaces, and the customer's existing environment.

New blockchain integrations

Connect the next network without building another routing stack.

New blockchain networks may introduce unfamiliar RPC interfaces, methods, and provider requirements.

Magma engineers can assess the network, work on supported chain specifications or necessary integration components, configure compatible upstreams, and validate the resulting connectivity.

The goal is to reuse the platform's reliability and orchestration capabilities wherever the network permits.

Simplified example

chain: new-network

interfaces: [jsonrpc, rest]

methods: [...]

health: latest-block

Related solution: New Chain Listings

Custom provider integrations

Work with the providers your business needs.

Some infrastructure environments depend on specialized RPC vendors, customer-operated nodes, internal gateways, or provider-specific authentication and routing behavior.

Magma can scope the engineering needed to integrate compatible endpoints and support relevant network or method requirements.

Smart Router
Specialized vendorCustomer nodeInternal gateway
Related solution: High Availability

Customer-specific Smart Router capabilities

Adapt the routing layer to agreed technical requirements.

Some customers need infrastructure behavior that goes beyond the standard configuration.

These requests may involve routing policies, supported method handling, verification requirements, observability, or integrations with surrounding systems.

Magma can evaluate whether the requested capability belongs in configuration, an extension, or a product change, then scope the appropriate engineering work.

ConfigurationExtensionProduct change
Related solution: Data Integrity & Reconciliation

Integration with existing infrastructure

Make Smart Router fit the environment you've already built.

Enterprise teams already operate their own services, networks, providers, and monitoring environments.

Magma can help design and implement agreed integration work around supported endpoints, deployment configuration, operational telemetry, and connectivity requirements.

Your existing infrastructure remains part of the architecture rather than something that must automatically be replaced.

Your systemsSmart RouterYour providers

We build and adapt the blockchain connectivity layer. Your team remains responsible for its application, business logic, signing, custody, and financial systems.

See how an engineering engagement works

Different infrastructure requirements. A process built to understand and deliver the right solution.

Not every requirement needs a new product feature. Sometimes the solution is configuration. Sometimes it is a new provider integration. Other cases require engineering changes and careful validation.

The first step is understanding the real operational need.

Customer need

Add a new blockchain

"We need to support a blockchain that is not yet configured in our RPC environment."

Engineering review
  • Network and interface discovery
  • Required RPC methods
  • Available upstream endpoints
  • Chain specification compatibility
  • Routing and health requirements
Potential engineering work
  • Chain specification or integration changes
  • Provider configuration
  • Relevant health checks
  • Supported method verification
  • Deployment preparation

Expected output category

Validated network connectivity integration

From technical requirement to defined engineering scope.

The actual approach, deliverables, estimated effort, implementation timeline, and commercial terms are determined during the engineering review.

Illustrative engineering scoping workflow. Each customer requirement is reviewed for feasibility, scope, dependencies, and delivery terms.

Direct product expertise

Work with engineers who understand the routing layer from the inside.

A blockchain RPC infrastructure problem can involve more than an endpoint configuration. It may require understanding chain specifications, provider selection, method behavior, caching, request validation, or how the router handles failures.

These components are closely connected. A change in one part of the infrastructure can affect how another part behaves.

Magma builds and maintains Smart Router. Our engineers work with the platform's architecture, its supported interfaces, and the operational challenges that come from running it in production.

That experience provides a more focused starting point for customer-specific engineering than treating every request as an isolated integration project.

Product-level understanding

Engineering work can be assessed against the actual Smart Router architecture and existing capabilities.

Multi-chain experience

Our platform supports 284 blockchain networks across EVM and non-EVM ecosystems, with different supported RPC interfaces and requirements.

Operational awareness

The engineering process can consider configuration, validation, monitoring, and how a change will behave in the customer's deployment environment.

Core Platform

RoutingValidationProvider managementObservability

Integration Layer

Chain specificationsProvider configurationsAgreed extensions

Customer Infrastructure

Existing applicationsPrivate nodesThird-party providers
Illustrative. An agreed extension connects through the integration layer without replacing the core architecture. Not every integration requires changing Smart Router source code.

The goal is not just to build an integration that works once. It is to understand how that integration fits into the infrastructure your business depends on.

Our engineering process

A clear process from the first technical conversation to a validated integration.

Custom infrastructure engineering works best when the requirement, ownership, and acceptance criteria are defined before implementation begins.

Magma's approach starts with understanding the customer's environment and the outcome the integration must support.

Step 1

Understand the requirement

Review the business and technical need.

Identify the relevant blockchain networks, interfaces, providers, critical methods, deployment model, and operational constraints.

The exact delivery process is adapted to the requirements and scope of each engagement. No fixed implementation timeline is implied by these stages.

Discuss a technical requirement
Beyond a working demo

An integration is more valuable when your team understands how to operate it.

An infrastructure integration should be evaluated in the environment and workflow it is intended to support. A request reaching a provider once does not necessarily establish production readiness.

Depending on the agreed scope, engineering work may require verifying interface compatibility, supported methods, provider behavior, routing policies, and operational expectations.

The deliverable should make clear what was implemented, what was validated, and what responsibilities remain with each team.

Implementation

Technical implementation

The agreed configuration, specification, integration, or platform change.

Testing

Validation results

Evidence from the agreed compatibility, endpoint, method, or integration checks.

Operations

Operational context

Relevant configuration notes, known limitations, dependencies, and monitoring considerations.

Ownership

Ownership and next steps

A clear understanding of who deploys, operates, maintains, and supports the resulting integration.

Specific deliverables and documentation are defined by the agreed engineering scope.

Working code is important. A clearly defined, validated, and supportable result is what makes infrastructure engineering useful in production.

Real platform architecture

A new blockchain doesn't always require a new routing implementation.

Smart Router supports many blockchain networks through chain-specific specifications. These specifications describe relevant network interfaces, supported methods, and behavior the routing system needs to understand.

For a compatible network, adding or adapting a specification can allow the existing routing infrastructure to serve that network without rebuilding the core router.

Other networks or unusual interfaces may require additional engineering work. Magma's engineers can help determine which approach is appropriate.

Chain specifications
Blockchain-specific definitions for supported RPC interfaces and methods.
Provider integration
Configure compatible upstream endpoints and relevant connection requirements.
Endpoint health checking
Use supported health and compatibility checks to assess configured infrastructure.
Shared routing infrastructure
Reuse applicable provider selection, recovery, and operational capabilities across supported networks.
Plan a new-chain integration
  1. 1New Network Requirement
  2. 2Chain & Interface Assessment
  3. 3Specification / Integration Work
  4. 4Provider Configuration
  5. 5Endpoint & Method Validation
  6. 6Smart Router Connectivity
Conceptual example. Effort and approach depend on the network.
Your infrastructure, extended

Your existing providers and systems should be part of the solution, not obstacles to it.

Enterprise teams rarely begin with a blank infrastructure environment. They already use different blockchain providers, internal gateways, private nodes, monitoring systems, and application-level integrations.

Replacing everything simply to introduce a new routing capability can create unnecessary work and risk.

Magma's engineering engagements can focus on fitting supported Smart Router connectivity into the environment the customer already operates.

Existing RPC providers

Review compatible upstream endpoints, authentication requirements, method support, and relevant routing behavior.

Customer-operated nodes

Integrate compatible internal blockchain nodes alongside external providers, respecting the customer's network and security requirements.

Operational environment

Consider deployment configuration, relevant monitoring, and interaction with the systems surrounding the RPC layer.

Customer services
Magma Smart Router

+ Agreed integration components

Provider AProvider BProvider CPrivate nodes
Illustrative. Your private infrastructure and security controls stay under your control unless explicitly agreed otherwise.

We design agreed connectivity work around the customer's existing architecture where technically feasible, rather than assuming every customer should use the same infrastructure topology.

Built for real enterprise infrastructure

Our engineering starts with a platform already used in production.

Magma Smart Router is used in production by major digital asset infrastructure companies, including Kraken, Fireblocks, Galaxy, and Hypernative.

These organizations operate blockchain systems that depend on reliable providers, multiple networks, and specialized infrastructure requirements.

The experience of building and operating Smart Router for demanding production environments informs the engineering work Magma can undertake with Enterprise customers.

KrakenFireblocksGalaxyHypernative
Kraken

A specialist infrastructure partner, integrated with existing systems.

Kraken integrated Magma Smart Router as an additional routing and resilience layer above its existing blockchain infrastructure.

The publicly documented partnership demonstrates an approach built around strengthening the infrastructure a customer already operates, rather than replacing it with an entirely new stack.

For companies evaluating custom RPC engineering, that architectural principle matters: successful infrastructure work must fit the customer's actual systems and operating requirements.

Read the Kraken case study
Fireblocks

Enterprise integration without replacing the existing RPC environment.

Fireblocks uses Smart Router above its existing blockchain RPC providers and infrastructure.

Magma's published case study reports that the initial integration of Smart Router into the existing Fireblocks environment was completed in a single onboarding session.

The case demonstrates compatibility with an established enterprise infrastructure environment. It does not establish that every custom engineering project or new network integration can be completed in one session.

Read the Fireblocks case study
Engineering that fits the platform

Sometimes the best custom feature is not writing a new feature at all.

Not every enterprise requirement needs new code. Some challenges can be solved through configuration, an existing capability, or an integration that is already supported by the platform.

Other requirements genuinely need engineering changes. The important step is distinguishing between them.

Magma's team can evaluate the customer's requested outcome against the current Smart Router architecture and propose an appropriate approach. That helps avoid unnecessary custom infrastructure where the existing product can already do the job.

The goal is the right operational result, not the largest amount of custom development.

Illustrative engineering assessment

New infrastructure requirement

Use an existing capability

Configure a supported routing, validation, or deployment feature to meet the customer's requirement.

Clear scope, clear responsibilities

The right engineering partnership starts with an agreed definition of done.

Custom blockchain infrastructure work varies from one customer to another. Adding a supported provider is different from integrating an unfamiliar protocol. A configuration change is different from developing a new Smart Router capability.

And work performed inside a customer-operated environment may require different access, validation, and delivery arrangements from a Magma-managed deployment.

For that reason, Enterprise engineering engagements are scoped according to the actual requirements.

Requirement

What does the business need?

Agreement

What will be delivered and accepted?

Engineering

How will it be implemented, tested, and handed over?

Scope and commercial terms are agreed before implementation.

What should be agreed

Technical scope
The networks, interfaces, endpoints, methods, and product behavior involved.
Deliverables
What will be configured, implemented, integrated, tested, or documented.
Acceptance criteria
How the customer and Magma will determine whether the agreed engineering work is complete.
Dependencies
Required endpoints, accounts, credentials, environment access, third-party support, and customer inputs.
Delivery arrangement
Estimated effort, milestones, reviews, and timeline after technical scoping.
Commercial and operational ownership
Engineering costs, any included allocation, rights to deliverables, maintenance, and ongoing support responsibilities.

Engineering services are available through appropriate Enterprise arrangements. The specific work, timeline, allocation, and commercial terms are agreed with the customer.

The right service for the right need

Not every engineering need is the same.

Magma offers different services around the blockchain connectivity layer. Understanding the difference helps customers choose the right engagement.

24/7 Technical Support

Respond to relevant issues affecting supported infrastructure and help operate the agreed managed environment.

"A provider or routing component is causing an incident in production."

Outcome: Technical investigation, operational support, and applicable mitigation under the Enterprise agreement.

Learn more

Dedicated Engineering

This page

Review, design, implement, and validate agreed customer-specific blockchain connectivity requirements.

"We need a new network, specialized integration, or capability that requires engineering work."

Outcome: A scoped technical deliverable with agreed acceptance criteria.

Onboarding

Configure and validate the initial supported routing environment so the customer can begin using Smart Router.

"We have decided to use Magma and need to connect our existing networks and providers."

Outcome: A configured environment ready for the agreed go-live review.

Learn more

Private Hosting

Provide an isolated, managed Smart Router deployment for an Enterprise customer.

"We need a dedicated routing deployment operated by Magma."

Outcome: A dedicated single-tenant routing environment under the applicable agreement.

Learn more
On the roadmap

An even closer engineering relationship for Enterprise customers.

We're continuing to develop how Enterprise customers work with Magma's engineering organization. The goal is a clearer, more consistent long-term collaboration model around the blockchain infrastructure they operate.

Planned service model

Named engineering contact

Explore assigning a named engineering contact to Enterprise accounts under applicable service arrangements, providing more continuity across technical discussions and ongoing infrastructure requirements.

Planned workflow improvement

Greater visibility into engineering requests

Improve the way customers can understand the scope, progress, and status of approved integration and customization work.

Planned service enhancements. Availability, scope, and commercial terms remain subject to agreement.

Frequently asked questions

Dedicated Engineering is an Enterprise service for scoping and implementing agreed blockchain RPC infrastructure requirements around Smart Router. Work may include new chain integrations, specialized provider connections, custom infrastructure behavior, and integrations with existing customer systems.

Custom features and integrations are part of Magma's Enterprise offering, but the exact included scope, engineering allocation, project costs, and delivery terms depend on the customer agreement. Do not assume unlimited custom development is included.

A named or full-time assigned engineer is not a universal standard commitment. Engineering staffing and account arrangements must be agreed for each engagement.

Magma can evaluate a new network's interfaces, provider availability, chain specification requirements, and integration feasibility. Compatible networks may be added through specifications or scoped engineering changes. The actual effort and feasibility depend on the network.

No. Smart Router uses chain specifications for supported network behavior, and some integrations can be implemented through existing configuration. Other networks or unusual interfaces may require additional engineering. The correct approach is established during technical review.

Yes, subject to compatible network interfaces, access requirements, and technical feasibility. Smart Router supports external RPC providers and customer-operated nodes, and Magma can scope additional integration work when needed.

Magma can assess customer-specific requirements involving routing, method handling, verification, and relevant platform behavior. Implementation depends on technical feasibility, product architecture, agreed scope, and commercial approval.

Yes, compatible private and customer-operated nodes can be part of a Smart Router deployment. Integration work may require suitable network connectivity, authentication, endpoint configuration, and validation according to the environment.

The Dedicated Engineering service described here is focused on Smart Router and related blockchain RPC connectivity infrastructure. It is not a general-purpose software outsourcing, smart contract development, wallet creation, or financial application development offering.

Pricing and engineering allocation depend on the approved scope and the Enterprise agreement. Requirements, deliverables, estimated effort, dependencies, ownership, and commercial terms are reviewed before work is committed.

Delivery time depends on the supported network or provider, interface complexity, access to endpoints, required functionality, testing needs, and customer dependencies. A specific estimate can be provided after technical scoping.

Delivery commitments, milestones, and dependencies are established in the agreed scope. This service page does not provide a universal turnaround guarantee.

Operational ownership, maintenance, documentation, support, and future compatibility responsibilities are defined in the engagement. The customer and Magma should agree on these responsibilities as part of the delivery process.

Code ownership, licensing, rights to use deliverables, and any inclusion in the core Smart Router product depend on the applicable agreement. Do not assume all custom work transfers exclusive ownership to the customer.

Validation can be included in the agreed engineering scope. The relevant tests and acceptance criteria depend on the network, provider, method, and deployment environment.

No. Onboarding focuses on configuring and validating the initial supported customer environment. Dedicated Engineering addresses additional or specialized requirements that need separately scoped technical work.

Dedicated Engineering and 24/7 Technical Support are different services. Incident response coverage depends on the Enterprise support arrangement and must not be assumed to be included in every engineering engagement.

Yes. Smart Router is designed to operate above compatible third-party providers and customer-operated nodes. Engineering work can be scoped around integrating the infrastructure your team already uses.

Yes. Smart Router supports 284 blockchain networks across multiple protocol families, including EVM and non-EVM ecosystems. Supported methods and interfaces vary by network.

Share your blockchain networks, existing providers, technical requirements, and the outcome you want to achieve. Magma can review the requirement and discuss an appropriate engineering scope.
Let's build the infrastructure you need

What's the blockchain integration your team keeps putting off?

A new network. A specialized RPC provider. A routing requirement. An integration with infrastructure you've already built.

Tell us what your application needs and what's preventing the current RPC environment from supporting it.

Our engineers can review the requirement, assess how it fits Smart Router, and discuss the scope of an appropriate solution.

Keep your product roadmap moving. Let Magma help build the blockchain connectivity behind it.