Managed service providers sit closer to their customers than almost anyone in technology. They run the infrastructure, patch the systems, answer the calls at two in the morning and carry the digital transformation projects nobody else wanted.
And yet, for most MSPs, the largest line in the customer’s technology spend — the cloud itself — flows to someone else.
Why manage someone else’s cloud when you could run your own?
That question used to have an easy answer: because building a cloud took years, a very large engineering team and a hyperscaler’s budget. That answer is out of date. With the right platform, an MSP can launch a cloud business of its own in 90 days.
The squeeze on managed services
The traditional MSP model — infrastructure management, helpdesk, monitoring, security and application support — still matters. But it is under three kinds of pressure.
Margins compress. As competition rises, customers treat managed services as a commodity and negotiate accordingly.
Dependency grows. Public cloud providers, hosting companies and software vendors set the prices, the service levels and much of the customer experience. The MSP carries the relationship without controlling the product.
Growth is linear. More revenue usually means more engineers. Managed services scale with headcount; platforms scale with automation.
That is the trade the industry has offered MSPs: stay close to the customer, and resell someone else’s cloud to them. It is usually called a partnership.
Customers want a local alternative
The timing favours MSPs. Organisations are frustrated with variable bills, data transfer charges and pricing structures they cannot forecast. Regulated sectors need data residency, compliance and local governance. And almost everyone values an expert who picks up the phone and already knows their environment.
MSPs already have that trust. What most lack is a cloud to sell with it.
What used to make it impossible
Launching a cloud once meant building everything: compute, storage and networking orchestration, a self-service portal, customer management, a billing engine, a marketplace, multi-tenancy and the automation to hold it together. That meant multi-million-dollar investment, large engineering teams, long development cycles and real operational risk. So cloud ownership stayed with hyperscalers and a handful of large providers.
What has changed is that the platform layer no longer has to be built.
What you can sell on your own cloud
Once the platform exists, the catalogue goes far beyond virtual machines:
- Infrastructure — compute, storage, networking and backup.
- Platform services — Kubernetes, containers, managed databases and object storage.
- Security — identity, web application firewalls, detection and response, compliance monitoring.
- Continuity — disaster recovery as a service.
- AI — GPU compute, AI workspaces and machine-learning environments.
- A marketplace — software and services from partners, sold under your brand.
Every one of those becomes recurring revenue rather than a project. And every additional service a customer runs on your platform makes the relationship stronger and the customer less likely to leave.
The 90-day launch
Ninety days is achievable because the hard parts already exist. The work is decisions, deployment and launch — not software development.
Weeks 1–2: Strategy. Choose the customer segments and industries you will lead with, the services you will offer, and how you will price and package them.
Weeks 3–6: Infrastructure. Deploy compute, storage, networking and security controls — on hardware you already own, in a facility you choose.
Weeks 6–8: Platform. Configure the customer portal, the catalogue, billing, marketplace services, monitoring and reporting. This is where your brand and your prices go in.
Weeks 8–10: Pilot. Onboard your first customers and validate service delivery, billing, operational workflows and support procedures.
Weeks 10–12: Commercial launch. Launch the go-to-market: campaigns, partner programmes and sales enablement.
Sovereign demand is your advantage
Government, banking, healthcare, education and critical infrastructure increasingly need data residency, compliance alignment, local support and operational transparency. Global providers struggle to offer all four at once. A local MSP with its own cloud can — and already has the relationships with the organisations that need it.
Own the cloud. Borrow the scale.
There is an obvious objection. A single MSP’s cloud can only offer what that MSP can build and run. Customers compare you with platforms that have thousands of services.
This is the problem Oasis Stack was built to solve. An MSP running an Oasis cloud keeps its own customers, prices and invoices, and — through the federation — can sell services that other independent Oasis clouds run, by explicit agreement, without handing over a single customer. Your catalogue grows beyond what you could build alone. Your customer relationship stays yours.
The commercial model follows the same principle. The platform is licensed at a flat fee per deployment, banded by scale, and federation is a flat participation fee. What you charge your customers stays entirely yours. And you choose how much of the platform you operate yourself, and how much the Oasis Stack team operates for you.
Build or buy?
Building internally means significant investment, long development cycles, continuous maintenance and a permanent engineering team. Starting from a cloud enablement platform means faster deployment, lower risk, lower cost and revenue from the first customers onwards. For most MSPs, the difference between launching in months and launching in years decides the business case on its own.
The next MSP is a cloud provider
Customers now expect self-service, cloud-native services, AI readiness, compliance and an integrated marketplace. MSPs that rely only on traditional managed services will find themselves further commoditised each year. MSPs that own a platform gain differentiation, recurring revenue and a business that grows faster than their headcount.
The barriers to entry have never been lower. Launching a cloud is no longer a multi-year programme. It is a 90-day decision. The only question left is who makes it first in your market.