-
MeshCloud
Turn unspent Azure into
AI-ready IoT.
MeshCloud deploys in your Azure tenant. Your Azure consumption retires MACC, while you stand up the production-validated IoT cloud foundation you were going to need anyway.
Spend your Azure where it builds something.
MeshCloud deploys in your Azure tenant under our Enterprise Subscription. Your tenant runs the platform. Microsoft bills you directly for Azure consumption, and that consumption counts toward your Microsoft Azure Consumption Commitment. The retirement happens through the same Azure billing relationship you already have. No separate vehicle, no procurement complexity, no carve-outs.
Two things matter here:
First, the Azure spend is productive. You’re not burning commitment on workloads that don’t move the business. You’re standing up the production-validated IoT cloud foundation you’d be building anyway.Â
Second, the timeline works. MACC clocks don’t pause while you build foundation from scratch. MeshCloud gets devices connecting and data flowing in days, so commitment retires while you’re delivering business value.
MeshCloud is available through two deployment models. Our Enterprise Subscription runs in your Azure tenant, which means the Azure consumption is yours, the billing relationship with Microsoft is yours, and the MACC retirement is yours.
Enterprise Subscription
MeshCloud deploys in your Azure tenant on a subscription basis. You pay Microsoft directly for Azure consumption, and that consumption retires commitment. Subscription-shaped pricing for the MeshCloud platform itself. Best fit when MACC retirement is paired with OpEx economics.
Mesh Hosted SaaS
If MACC retirement isn’t on your roadmap, Mesh Hosted SaaS skips the Azure tenant setup entirely. We host and operate the platform in a private tenant so your team can focus on the connected product itself.
Microsoft Alignment
Sold with Microsoft, through the channels you already use.
MeshCloud is available through the Microsoft Azure Marketplace, which means you can transact through the same procurement channels you already use for Azure services.
Your Microsoft procurement team sees a familiar SKU. Your Azure billing relationship stays intact. The Marketplace path also streamlines the motion from evaluation to deployment, with no separate vendor onboarding and no parallel contracting workflow.
FAQs
How does MACC retirement actually work with MeshCloud?
MeshCloud deploys in your Azure tenant under our Enterprise Subscription. You pay Microsoft directly for Azure consumption: services like Azure IoT Hub, Azure Data Explorer, Cosmos DB, Event Hubs, Container Apps, and the supporting services your deployment uses. That consumption retires Microsoft Azure Consumption Commitment through your standard Azure billing relationship. The MeshCloud license fee is a separate agreement with Mesh and is not currently part of the MACC retirement vehicle.
Can we transact this through the Azure Marketplace?
Yes. MeshCloud is available through the Microsoft Azure Marketplace, which means your procurement team sees a familiar SKU through channels you already use. Your Azure billing relationship stays intact. The Marketplace path also streamlines the contracting motion, with no separate vendor onboarding.
What happens if our MACC expires before our deployment fully scales?
Your MACC clock and your MeshCloud deployment are independent. Once MACC is retired or expires, you continue paying Microsoft directly for Azure consumption under standard billing. The deployment doesn’t change, only the commitment framework around it does. If your timeline is tight, MeshCloud gets devices connecting and data flowing in days, so retirement happens against productive workloads from the start.
Can we align this with our procurement cycle?
Yes. Our Enterprise Subscription is structured to fit subscription and OpEx procurement cycles. It can transact through the Marketplace or direct, and lets MACC retirement happen on the same calendar as your Azure consumption. For capital and license-based purchase cycles, we also offer custom licensing options. Talk to sales to scope the shape that fits your fiscal year and approval workflow.
Ready to put your Azure commitment to work?
Tell us about your current MACC position, your IoT cloud objectives, and your procurement preferences. We’ll help you scope the deployment model that fits and align it with your existing Microsoft relationship.