L1 · Your teams
The day-to-day, with CloudHost’s training behind it.
- Day-to-day requests and customer queries
- Basic operations and user administration
- Backed by CloudHost training, documentation, runbooks and operating procedures
Solutions · Engage
Run it yourself.
Or have it run for you.
Owning a cloud should not mean building a hyperscaler’s operations team first. You choose how much of the platform the Oasis Stack team operates. Whoever runs it, the customers, the pricing and the margin stay yours.
Your business, alwaysSupport in three layersFour ways to engage
You own the business
Customers, pricing, billing and the relationship stay yours in every model.
We back the platform
Operations, lifecycle, escalation and capacity planning, as much as you want of it.
Built to hand over
Training, documentation and runbooks, so your teams can take on more over time.
One platform either way
The same software whether you run it or CloudHost does.
Why it exists
Most providers will run your cloud, as long as they keep your customer.
Operating a cloud is expensive to staff, so the usual offer is to hand it over: the provider runs the platform and, in the end, owns the relationship. Here the split is by layer, not by ownership. You decide how much of the platform the Oasis Stack team operates, and the business is yours in every case.
Support in three layers
Start beside us. Take on more when you are ready.
The aim is a team that can run its own cloud. CloudHost takes the layers you do not want to staff yet.
L2 · CloudHost
The platform problems your teams escalate.
- Advanced troubleshooting
- Platform health and performance issues
- Service escalations and platform optimisation
L3 · CloudHost
The engineering behind the platform.
- Platform engineering and product support
- Platform updates and root-cause analysis
- Architecture guidance
How the layers move
The split is agreed at Design, set out in the support contract, and revisited as your team grows. Reliability & operations
- The goal is a team that can run its own cloud
- Knowledge transfer is part of every handover
- A layer can move to your team when it is ready
What CloudHost does
From the first design to the thousandth customer.
Four kinds of work, taken on as a whole or piece by piece.
Setup
Architect, deploy and migrate.
- Solution architecture, cloud design workshops and capacity planning
- Multi-tenant, sovereign and national cloud design
- Installation, security and high-availability configuration, DR design and platform validation
- Infrastructure, application and database migration, with go-live support
Platform operations
The service areas the Oasis Stack team operates for you.
- Compute: VM operations, capacity and performance
- Storage and network: capacity, replication, VPC, VPN and load balancing
- Database: managed engines, monitoring and backup validation
- Security, compliance, marketplace and billing operations
Governance
Service quality kept up, not just kept running.
- Health, capacity, security and service reviews
- Operational audits and performance benchmarking
- Capacity, security, operational and compliance risk management
- Quarterly reviews, roadmap planning and optimisation recommendations
Enterprise and sovereign support
For deployments that need people close by.
- A dedicated technical account manager and quarterly architecture reviews
- Government and national cloud operations guidance and regulatory alignment
- Resident engineers, site visits, platform audits and health assessments
- Architecture, security and compliance workshops
What you hold at handover: architecture documentation, a deployment runbook, a security baseline, an operational handover and a knowledge-transfer programme.
Ways to engage
Four ways to work with us, three levels of cover.
Scope is agreed per deployment. Prices are not published; they follow the model and the level you choose.
Shared managed services
A CloudHost operations team that also serves other deployments.
Dedicated managed services
A team assigned to your deployment alone.
White-label managed services
Operations delivered under your brand, to your customers.
Federated partner services
For operators in the federation, to the standards every federated cloud shares.
Foundation
For smaller deployments: L2 and L3 support, platform updates and monthly reviews.
Professional
For growing cloud providers: Foundation, plus capacity planning, security reviews and quarterly architecture reviews.
Enterprise
For sovereign and national clouds: a dedicated account manager and architects, onsite services, executive governance reviews and roadmap planning.
Operating model
Decide how much you run.
The split is agreed at Design, and it can change as your team grows.