Granite Telecommunications has launched SIM360, a multi-carrier eUICC platform that puts profiles from all three major US mobile networks onto one physical SIM and lets enterprises manage them through a single control layer.

At first glance, that sounds like another “one SIM, many networks” proposition. It is not quite the same thing.

The important difference is that SIM360 is built around carrier-direct profiles rather than permanent roaming. It uses GSMA SGP.32 architecture, Thales eSIM technology and Granite’s orchestration layer to let customers activate, deactivate and switch carrier profiles remotely. For enterprise IoT and fixed wireless deployments, that moves the conversation from “which network did we buy?” to “which network should this device use now?”

READ MORE: Navigating Permanent Roaming for IoT: Challenges and Solutions

Three networks, one control layer

SIM360 is aimed at US domestic IoT and fixed wireless access deployments. Granite says the SIM comes preloaded with profiles from all three Tier-1 US operators, with usage managed through its Granite Enterprise Mobility Management platform.

Customers can select the primary carrier, change profiles remotely and manage devices and network usage through one interface. Billing is aggregated at the EID level rather than split into three carrier relationships.

READ MORE: Why Enterprises Need Orchestration, Not SIM Cards

Granite is positioning resilience as the bigger story. According to the company, SIM360 can automatically move a device to another carrier when the active network becomes unavailable because of an outage or coverage problem.

The timing matters. Granite’s FAQ says device-level failover takes around five to ten minutes. A deliberate change of primary carrier can take effect immediately after a reboot or automatically within 12 hours.

That is useful because “automatic failover” can otherwise mean almost anything. Five to ten minutes may be perfectly acceptable for kiosks, branch backup links, digital signage or many industrial deployments. It is less impressive where even a few minutes offline creates a serious operational problem.

Why SGP.32 matters

SGP.32 is what makes this model more interesting than traditional multi-network roaming.

The GSMA specification was designed for remote provisioning and management of IoT eUICCs, including devices with limited interfaces or constrained connectivity. It enables profiles to be securely downloaded and managed over the device lifecycle rather than tying a deployment permanently to the connectivity chosen at manufacture. The GSMA lists SGP.32 v1.3 as active in 2026.

READ MORE: Onomondo and Kigen Bring SGP.32 eSIM to IoT

Granite is also arriving as SGP.32 moves from standards work into commercial products. 1GLOBAL offers an eSIM IoT Manager built around remote profile control; Eseye is positioning SGP.32 inside its multi-operator orchestration platform; KORE and Kigen announced SGP.32 connectivity designed around local connectivity, failover and recovery; and floLIVE has added SGP.32 support alongside multi-IMSI models.

The broader direction is clear: enterprises increasingly want local connectivity, provider choice and one operational control plane.

Historically, getting all three has been awkward. Enterprises could contract several operators and accept fragmented billing and management, or buy global roaming connectivity and accept the commercial, regulatory or performance compromises that can accompany permanent roaming.

SIM360 tries to sit between those models.

The questions buyers should still ask

The launch answers more questions than many enterprise eSIM announcements do, but not all of them.

Before treating SIM360 as mature connectivity orchestration, buyers should ask:

• What exact conditions trigger automatic failover, and can enterprises define those policies themselves?
• What happens when connectivity is degraded but not fully down?
• How does a device recover if it cannot reach the orchestration layer?
• Which routers, gateways and IoT modules are certified today? Granite says many leading devices are supported, but does not publish a full list on the product page.
• Who controls the carrier profiles if the commercial relationship with Granite ends?
• Are there switching charges, minimum volumes or carrier-specific restrictions?
• What are the measured failover success rates across a production fleet?

There is also an important distinction between orchestration and instant switching. SGP.32 provides the architecture for remote profile management; it does not eliminate radio registration, profile enablement or device-side recovery time. Granite’s stated five-to-ten-minute failover window makes that visible.

Where Granite fits

The strongest part of SIM360 may be its commercial packaging rather than the SIM itself.

Granite is combining three direct US carrier relationships, one eUICC, one management platform and consolidated billing. For a retailer with thousands of locations, a distributed enterprise using fixed wireless backup, or a US logistics deployment, that could remove significant operational friction.

READ MORE: Eseye Integrates SGP.32 to Scale Global IoT Connectivity

It is less obviously designed for a company deploying low-power sensors across 30 countries or an OEM needing a broad portfolio of local profiles worldwide. Players such as 1GLOBAL, Eseye, KORE/Kigen and floLIVE approach SGP.32 from a more global IoT orchestration angle, with different combinations of bootstrap connectivity, local profiles, multi-IMSI and cross-border management.

That does not make one model better. It means the orchestration model has to fit the fleet.

Conclusion

SIM360 is interesting because it makes SGP.32 tangible.

The enterprise eSIM market is moving beyond the old promise of “one SIM that connects everywhere.” The more consequential question is who controls connectivity after deployment: the original operator, an IoT connectivity provider, an orchestration platform, or the enterprise itself.

Granite pushes more of that control toward the enterprise, but inside a deliberately US-focused package. That could suit organizations whose real problem is not global coverage but domestic carrier dependency.

The next competitive battleground will not be the number of networks printed on a coverage map. It will be switching speed, policy control, offline recovery, device interoperability and whether failover works reliably when the primary network disappears.

On those measures, SIM360 has a credible architecture and unusually useful switching details. What it does not yet have publicly is independent performance evidence, a detailed SLA, pricing or demonstrated fleet-scale failover data. For enterprise buyers, that is the gap worth watching.