The real cost of self-managing SGP.32

SGP.32 is the next evolution of eSIM standards, specifically designed to enable Remote SIM Provisioning (RSP) for the Internet of Things (IoT) at a massive scale. But while enterprises are excited at the promise of unprecedented flexibility, SIM supplier independence, and the potential to activate thousands to millions of new connections without the friction of traditional operator lock-in, the advent of SGP.32 creates a significant tension, as more control over the SIM lifecycle necessitates a higher level of internal responsibility for the underlying technical and commercial orchestration.

Fundamentally, enterprise network managers need to consider how much their time is worth, when exploring the ramifications of a self-managed IoT initiative leveraging SGP.32, versus managed service eSIM orchestration, which integrates backend, frontend, and network systems into a single platform, with the entire lifecycle of the SIM managed by a specialist provider.

What does SGP.32 promise?

The GSMA's eSIM for IoT Technical Specification, otherwise known as SGP.32, marks the next evolution in eSIM technology, and is seen as a panacea for deploying and managing IoT devices at scale with greater flexibility, security, and efficiency. 

SGP.32 is an RSP standard purpose-built for IoT, designed to make it easier to remotely manage IoT device connections, particularly on constrained endpoints. Where the legacy SGP.02 (M2M) standard, relied on a push model controlled by mobile network operators (MNOs), often requiring complex integrations and bilateral agreements between carriers, SGP.32 introduces an enterprise-driven ‘pull’ model. This utilises an IoT Profile Assistant (IPA) on the device to initiate connectivity changes, effectively allowing an enterprise to switch connectivity providers ‘at the push of a button’. 

To enable this, connectivity providers are adopting the specialist eSIM Orchestrator (eSO) role, emerging alongside SGP.32, to manage profile lifecycle, network selection, compliance, and unified billing. But while SGP.32 defines how profiles are delivered, resilience is not built into the specification alone. Uptime, network fallback behaviour, multi-network continuity and operational guardrails remain critical to success in real-world IoT environments, typically placing considerable strain on an enterprise’s capabilities. 

What is the reality of self-managing an SGP.32 ecosystem?

SGP.32 is a standard, not a solution. Managing a large-scale IoT initiative leveraging SGP.32 requires more than just a technical understanding; it requires the construction of a complete infrastructure, which in some cases requires MNO-grade capabilities. 

Building and maintaining these capabilities in-house at an enterprise level involves significant capital investment and a development timeline that can stretch between 18 to 24 months before the first device is even deployed. So, perceived cost savings from running the process in house can quickly be swallowed by hidden operational expenses. 

Self-management operational readiness checklist:

Infrastructure ownership: Building or licensing a Subscription Manager Data Preparation (SM-DP+) platform to securely store and deliver encrypted eSIM profiles

eIM - proxy management: Implementing an eSIM IoT Manager (eIM) to act as a proxy for managing deployments centrally

Complex integration handling: Establishing back-end integrations between donor and recipient platforms that the standard itself does not automatically handle

Security frameworks: Hardening every endpoint against intrusion and ensuring secure, encrypted protocols for all over-the-air (OTA) updates

Regional compliance: Managing Know Your Customer (KYC) requirements and data sovereignty laws in every country of operation to avoid forced disconnections and permanent roaming hiccups

Commercial overhead: Negotiating and maintaining individual contracts, support agreements, and multiple bills with every MNO in the fleet

Where your time goes when managing large-scale IoT

In a self-managed enterprise IoT environment, even one leveraging the advanced capabilities of SGP.32, engineering and IT resources can easily be consumed by the relentless hidden workload of daily operations: 

• Day-to-day resource overheads: Your team’s time is lost to onboarding new profiles, managing fragmented connectivity partners, and manually troubleshooting SIM profile download failures. If a profile switch fails in the field, your staff—not the carrier or MNO—must handle the recovery to avoid orphaning the device
• Ongoing technical debt: Time must be continuously allocated for firmware updates, security patching, and rigorous interoperability testing to keep pace with evolving GSMA standards and regional regulations
• Skills and technology investment: Building or buying, and managing complex technologies like SM-DP+, SM-DS, eIM, integration layers, and security frameworks introduce the significant operational complexity of maintaining this infrastructure in-house
• The scaling trap: A process that works smoothly for 10,000 IoT devices becomes exponentially harder at one million units, where architectural limitations can trigger the need for a costly re-architecture of your entire middleware stack, increasing the burden for large-scale initiatives

Ultimately, time is a finite resource in enterprises and every hour spent managing cellular infrastructure is an hour stolen from innovation and your core business goals. 

The managed service alternative 

The emergence of SGP.32 represents a transformative milestone in large-scale IoT deployments, serving as a powerful strategic enabler for deploying and managing billions of new connections with unprecedented flexibility, security, and efficiency. 

But, to fully harness the potential of this enabler without succumbing to the ‘DIY delusion’ of self-management, enterprises are increasingly adopting eSIM orchestration (eSO)—an advanced capability within a Connectivity Management Platform (CMP) that abstracts the considerable technical complexity into a seamless, high-performance managed service.

By leveraging SGP.32 as part of a managed service offering, organizations can shift their focus from infrastructure management to their core business objectives, enjoying the following benefits:

Operational efficiency and resilience

A managed service replaces the burden of handling individual components, such as SM-DP+, SM-SR, and eIM, with a streamlined process managed by experts. This delivery model ensures:

• A single point of accountability: One platform, one contract, and one partner provide 100% global connectivity
• Superior uptime: Advanced switching logic and automated failover ensure maximum device availability
• Self-healing resilience: Managed services integrate proactive monitoring and heartbeat checks to automatically resolve issues before they impact the business

Unified global visibility

A fully managed IoT initiative leveraging SGP.32 benefits from a single pane of glass view of the entire IoT estate. This centralized portal offers:

• Real-time insights: Deep visibility into device health, network usage, and location data worldwide
• Simplified financials: Enterprises receive a single global bill even for international deployments, eliminating the need to reconcile fragmented invoices from multiple carriers
• Regulatory peace of mind: Specialist providers manage complex local regulations, such as permanent roaming bans in Brazil or India and data sovereignty requirements, ensuring devices remain compliant and online

Strategic flexibility

Working with a specialist provider like Eseye allows enterprises to avoid the hidden costs associated with building and maintaining an in-house platform. Instead, a managed service provides:

• Favourable commercial rates: Specialist third parties possess the scale and relationships to negotiate favorable connectivity rates that individual enterprises would struggle to achieve and manage on their own
• Future-proof connectivity: Managed services offer a clear migration path from legacy standards like SGP.02 to SGP.32 and even future specifications like SGP.41/42, ensuring long-term investment protection
• Expert 24/7 support: Access to a dedicated team of specialists for troubleshooting, optimization, and rapid deployment ensures that projects scale faster and more reliably

As analysts from Transforma Insights recommend, the most effective way to transition to SGP.32 is by partnering with established providers who can handle the "heavy lifting" of MNO management and full SIM lifecycle orchestration. This managed approach transforms a complex technical standard into a turnkey business solution, enabling enterprises to scale their IoT initiatives with total confidence.

How much is your time worth when it comes to enterprise IoT?

The most expensive asset in any enterprise IoT project is not the hardware or the data—it is the time and resources of your team. When performing a ‘build versus buy’ calculation, decision-makers must evaluate whether global connectivity management is a strategic priority or an operational burden that hinders growth,

Managed eSIM orchestration allows you to reclaim your time, accelerating your speed to market and ensuring outcomes are met without the ‘DIY delusion’. SGP.32 is indeed a powerful strategic enabler, but it is not a solution on its own. Its true value is only unlocked when the complexity is absorbed by an entity with knowledge and understanding, leaving you free to focus on your core business.

Eseye’s SGP.32 eSIM and Platform Solution gives enterprises unified control and choice across all RSP models (SGP.02, SGP.22, and SGP.32) from a single interface for more practical, resilient global IoT connectivity management. While Eseye’s Infinity platform embodies this role, providing a single pane of glass for orchestration, analytics, and control across global deployments.