Cloud that fits how you actually work.
Some workloads belong in public cloud. Some belong on a UK-sovereign platform you can pick up the phone about. Most estates need both — designed deliberately, run quietly, paid for predictably.
- Live in the UK
- UK-sovereign
- Multi-cloud
- ISO 27001
Most cloud estates didn't get designed — they got chosen. A SaaS over here, a public-cloud lift over there, a forgotten on-prem hypervisor that's still load-bearing. The shape works until the bill, the regulator, or the latency stops it working.
We built our own cloud so you don't have to compromise yours.
Our cloud, on our network, in our data centres.
Built on Nutanix, protected by Fortinet, run over the M-Tech core network and hosted across cross-resilient UK data centres. UK-sovereign by design — your data, your jurisdiction, your support team.
- Nutanix
- Fortinet
- UK-sovereign
Cross-resilient UK
- Microsoft Azure
- Amazon Web Services
- Google Cloud
Any region you need
- Core network
- Carrier peering
- Customer edge
One estate, end-to-end
What you can run on it
Virtual machines
Nutanix AHV under the hood — sized to fit, scaled when you need them, snapshotted properly so the rollback button actually works.
Containers
Docker and Kubernetes hosting alongside the VMs and databases they talk to. Production workloads, not just experiments.
Storage & backup
File and object storage on the platform — and a tested, immutable backup target for your on-prem and SaaS estates.
DR as a Service
Failover destination for whatever has to keep running. Active or warm, your call — recovery is tested, not just configured.
How you consume it
Colo
Your tin in our racks, on our network, behind our firewalls. Hands and eyes when you need them.
Self-service
Portal in betaYou run the workloads via API and CLI — soon, our own portal — while we run the platform underneath.
Co-managed
You keep change control where it matters; we handle the platform heavy lifting and the on-call.
Fully managed
We run it end-to-end. You consume capacity and outcomes — proactive maintenance, monthly reviews, sized to fit.
Why this beats just going to a hyperscaler.
UK-sovereign by design
Data, support, operations, engineers — all UK. mtech.cloud is in scope of our ISO 27001 and Cyber Essentials Plus certifications.
Predictable pricing
No egress shock. No surprise consumption bill at month-end. We quote what you'll pay and we hit it.
A real conversation
The same engineers who built it run it. You don't queue behind a chatbot for the answers.
- Microsoft Solutions Partner
- AWS Partner
- Google Cloud Partner
- ISO 27001
- Cyber Essentials Plus
Microsoft Azure. AWS. Google Cloud. Same discipline, your bill.
We design, build and run public-cloud estates the same way we run our own — with cost discipline, sensible governance, and a way out if you ever want one.
Solutions Partner
Partner
Partner
Build & run
Landing zones, networking, identity, governance. Done properly the first time, supported afterwards.
Bill your way
Through us as CSP, or on your own EA / direct relationship — your call. We can sit on either side of the bill.
Move workloads
Migrations between clouds, on-prem to cloud, and repatriation back to mtech.cloud where it makes sense.
We partnered with M-Tech to lift-and-shift our remaining servers into their secure UK data centres. Fast, professional, painless and affordable. They configured the VLANs on our network and executed the migration during evening hours. Zero downtime. Our staff and students were completely unaware of the change.
Questions we hear every week.
Can you take over an existing Azure or AWS estate?
Where is mtech.cloud hosted?
Do I have to use mtech.cloud, or can you run my Azure / AWS / GCP for me?
Can I keep my existing CSP relationship if you take over Azure?
How does pricing work on mtech.cloud?
Can I move from public cloud back to mtech.cloud?
Tell us what you're trying to do.
Whatever the shape of your team or your stack — multi-site, lean on IT, or somewhere in the middle — we'll listen first, ask the right questions, and tell you honestly how we'd approach it.
