About us
Built by engineers, not salespeople
ZeroTwo Cloud started in Birmingham in 2019. The name comes from a technical convention — 02 was the placeholder hostname in a rack we kept going back to. It stuck.
Where this started
The problem with how managed services used to work
Before ZeroTwo Cloud existed, our founders were working as cloud engineers at a mid-size MSP. The billing model was familiar — per hour, per ticket, per incident. Every time something broke, the client paid twice: once in downtime, once in the invoice that followed.
It created an odd dynamic. There was no particular financial incentive to prevent fires, only to respond to them. Clients who asked a lot of questions got expensive. The relationship was adversarial in ways nobody talked about openly.
In 2019, Nathan Ellery and Priscilla Eze-Okafor decided to try building something where the incentives actually aligned with the client. A flat monthly fee covering everything — so the only way to make the model work financially was to run environments that don't break.
How we work
What flat-rate actually means in practice
When someone calls us at 2am, we don't think about whether this qualifies as an emergency support event under clause 4.3 of a contract. We just fix it. That's what the flat fee covers.
It also means we invest time upfront in making environments robust — monitoring, backups, sensible alerting thresholds — because that investment pays off for us directly. A client who never has an incident is a profitable client. A client who has three incidents a month is not, regardless of what the SLA technically says.
We're not a huge company. As of 2026 we have eleven people: engineers, an operations lead, and one person who handles onboarding and account management. We don't have a sales team. Most of our work comes from referrals, which is probably the most honest signal about whether the model is working.
The team
The people who actually run things
Two of us write most of the public-facing content. Both have been doing cloud infrastructure work for longer than they'd like to admit.
Nathan Ellery
Co-founder, Infrastructure Lead
Nathan spent eight years as a senior cloud engineer at two London-based managed service providers before co-founding ZeroTwo Cloud in 2019. His background is in large-scale AWS environments — primarily financial services workloads where uptime requirements leave no room for ambiguity.
He writes for Field Notes on cost control, incident management, and infrastructure architecture decisions. His posts tend to be technical and to the point.
LinkedInPriscilla Adu Karikari
Co-founder, Operations and DevOps
Priscilla's background is in DevOps and platform engineering, with particular focus on CI/CD pipeline design and Kubernetes cluster management. Before ZeroTwo Cloud she led the platform team at a Birmingham-based SaaS company through a move from on-premise to hybrid cloud.
She covers migration strategy, DevOps tooling, and the organisational side of moving workloads to the cloud — the decisions that don't have obvious right answers.
LinkedInTalk to us about your infrastructure
No sales process, no discovery call that's actually a pitch. Tell us what you're running and we'll give you an honest assessment.
Get in touch