All Blogs
The Shift to Modularity: How Web3 Infrastructure is Being Reshaped
April 30, 2025

The Shift to Modularity: How Web3 Infrastructure is Being Reshaped

The Web3 ecosystem is entering a new phase. As the industry matures, we are seeing a clear trend: a move away from one-size-fits-all platforms toward specialized providers, each focused on delivering excellence in a specific layer of the stack.

Today, different players are recognized as leaders across different infrastructure layers — from key management, to blockchain data, to business services such as staking, on-ramp and more. This evolution is driven by increased competition, rising customer expertise, and a growing expectation for best-in-class service. Organizations building in Web3 no longer seek generalized solutions. They seek partners that deliver depth, reliability, and control at each critical layer.

The Modular Stack: A Strategic Shift

This specialization has led to a broader architectural shift: modular infrastructure design. Rather than relying on a single vendor for multiple infrastructure components, teams are integrating specialized providers into their technology stack — ensuring each layer meets the highest standards.

This approach offers several strategic advantages, including:

  • Flexibility: Swap, upgrade, or integrate providers without redesigning core systems.
  • Operational resilience: Minimize vendor lock-in and associated risks.
  • Product agility: Expand functionality and support new features without being constrained by a single provider’s roadmap.

For Web3 companies, modularity directly enables faster innovation and greater strategic control over their products.

Key Management in a Modular Stack

Key management is a foundational layer of any Web3 infrastructure stack. Historically, it has often been embedded into one-size-fits-all platforms, limiting control and flexibility.
At Sodot, we believe that key management should be independent, modular, and fully controlled by the organization itself.

Our self-hosted MPC key management infrastructure is built for this modular future:

  • Full operational control over private keys, signing workflows, and governance policies
  • Seamless integration into any tech stack, abstracting away the need to understand cryptography
  • Customizability to adapt to specific business, compliance, or security requirements

Organizations that integrate Sodot can treat their key management layer as a fully-owned component, one that evolves alongside their product and business needs.

Supporting New Chains: A Case Study in Modularity

 One of the most critical business areas is the support of new chains according to business needs.

A practical example of this modular approach is demonstrated in our recent multichain support demo with Adamik. By combining Sodot’s key management infrastructure with Adamik’s blockchain API services, a custody platform or wallet can:

  • Manage cryptographic operations securely and independently with Sodot
  • Access 60+ blockchains via Adamik’s unified API
  • Choose and update chain support dynamically, without dependency on external wallet providers

This architecture ensures that teams maintain full product control, are free to scale across ecosystems, and are not restricted by the priorities or timelines of external vendors.

View the full demo here

Conclusion

As Web3 evolves and becomes more mature and competitive, the standards demanded by customers increase sharply. 
Companies adopting a modular approach — selecting the best provider for each layer — are better positioned for long-term resilience, agility, and growth.
At Sodot, we are proud to power the key management layer for companies building with this philosophy: modular, independent, and fully in control of their critical infrastructure.

About Sodot

Sodot is an MPC key management infrastructure company built by a seasoned team of applied cryptographers and security experts. Sodot MPC infrastructure is designed for building custodial and self-custodial solutions, with full operational control and minimum dependencies.