Recurring
On-prem Kubernetes
A production cluster designed, built and handed over, then kept current. Upgrades, patching and version currency are part of the engagement, not a follow-on you have to negotiate.
On-prem KubernetesConsulting
We operate a platform. We'll help you operate yours.
An outside read of a system you've outgrown, infrastructure built and kept current, or an estate nobody left instructions for. Some of this is about hardware; some of it is about an application on somebody else's cloud.
Who this is for
Teams who aren't handing it to a vendor.
This side of what we do is independent of the managed platform. Plenty of these engagements end with infrastructure we have no involvement in running, and that's a fine outcome. The expertise is the product here, not a route into a subscription.
A review in particular doesn't require you to run your own infrastructure at all. Most are of applications sitting on a hyperscaler, where the question is what it costs, what breaks next, and what you'd be able to see when it does.
- You want an outside read of a system before it gets bigger
- Costs are growing faster than usage and nobody's sure why
- You have your own hardware, or want to
- A data-residency rule rules out the obvious options
- You've inherited an estate nobody left instructions for
Engagements
Four ways to start.
Recurring
Ongoing support
For clusters you already run. We learn the estate, then take on break-fix, patching, upgrades and on-call, or embed alongside your team for capacity planning and incident review.
Ongoing supportFixed scope
Architecture & capacity review
An end-to-end read of your application or service: architecture, capacity, cost, scalability, security and instrumentation. Report, capacity model, and a prioritised list of fixes we can deliver.
Architecture & capacity reviewFixed scope
Cloud to bare metal
Moving off metered infrastructure without a rewrite: assessment, target design, cutover plan and a run-in period, including an honest account of what shouldn't move.
Cloud to bare metalHow an engagement starts
Three steps, and you know the price.
- 01
Scoping call
A conversation about what exists, what hurts, and what you're actually trying to reach. No charge, and no obligation to go further.
- 02
Written proposal
Scope, deliverables, timeline and price, in writing. If we think the engagement is the wrong shape, this is where we say so.
- 03
Fixed scope, custom quote
Every engagement is priced individually. There's no rate card, because there's no standard job. What's fixed is the scope, so the number doesn't move under you.
Why us
We do this every day for our own customers.
We run a multi-tenant Kubernetes platform in production, on dedicated hardware, serving paying customers who notice when it's down. The people who'd work on your engagement are the people who carry that pager.
It's a different proposition to a consultancy that assembled a practice to sell engagements, not because they can't be good, but because we find out about our own advice at three in the morning.
Or don't build it at all
If the answer turns out to be "buy it"
Some of these conversations end with a team deciding they didn't want to run a search cluster after all. If that's you, our managed service is the same expertise with none of the handover.
Start with a conversation.
Tell us what you're running and what's hurting. If we're not the right people we'll say so on the call, not after the proposal.