KestrelInfrastructure

Managed Kubernetes control planes

You own the compute. We manage the state.

We run your Kubernetes control plane: API server, etcd, upgrades, backups, the pager. Your bare metal, GPUs and VMs join with one kubeadm join and stay where they are.

  • Upstream Kubernetes
  • Highly available across 3 zones
  • Per cluster pricing
# Create a control plane. It runs on our side.
~ $ curl -X POST $KESTREL_API/v1/clusters -d '{"name":"prod"}'
"endpoint": "prod-a8f9e2d4.cp.kestrelinfrastructure.com:6443"
# Join your servers, wherever they are.
root@node-01 # kubeadm join prod-a8f9e2d4.cp.kestrelinfrastructure.com:6443 --token k7x2pq.… --discovery-token-ca-cert-hash sha256:4c1e…
This node has joined the cluster.
root@gpu-01 # kubeadm join prod-a8f9e2d4.cp.kestrelinfrastructure.com:6443 --token k7x2pq.… --discovery-token-ca-cert-hash sha256:4c1e…
This node has joined the cluster.
root@vm-01 # kubeadm join prod-a8f9e2d4.cp.kestrelinfrastructure.com:6443 --token k7x2pq.… --discovery-token-ca-cert-hash sha256:4c1e…
This node has joined the cluster.
~ $ kubectl get nodes
NAME      STATUS   VERSION
node-01   Ready    v1.37.1
gpu-01    Ready    v1.37.1
vm-01     Ready    v1.37.1

What we run

We run the control plane. You run the nodes.

Kestrel is managed Kubernetes without the servers. The control plane lives on our infrastructure; your machines join it as worker nodes.

Managed by Kestrel

API server
One endpoint, encrypted under your cluster’s own CA.
etcd
Your cluster state. Snapshots every 5 minutes, kept off-cluster.
Scheduler and controllers
Placing pods and reconciling state.
Certificates
Issued and rotated for you.
Upgrades
One minor version at a time, when you choose.
Capacity
The control plane scales up as your cluster grows.

Managed by you

Worker nodes
Bare metal, GPU servers or VMs, anywhere with outbound internet.
The node OS
Linux, containerd or CRI-O, kubeadm and kubelet.
Workloads
Everything you deploy, plus storage and load balancing.
Access
RBAC and your own identity provider.

In every cluster

  • Upstream Kubernetes1.35, 1.36 and 1.37
  • NetworkingCilium, CoreDNS and Konnectivity, each optional
  • Outbound-only joinNo inbound ports on your network
  • Suspend and resumePause a cluster, keep its state
  • Console and APIScoped tokens for CI and Terraform
  • Activity logEvery change, who made it and when

Who it’s for

Which one are you?

I run my own servers

Keep the hardware. Lose the babysitting.

Servers in a colo, a GPU cloud or a closet. Point them at a Kestrel control plane and run them like a managed cluster.

  • Bare metal, GPUs and VMs in one cluster
  • A dead worker never takes the API down
  • Upgrades on your schedule
Request access

I sell servers

Sell managed Kubernetes on servers you already rent out.

For hosting, colo and bare metal providers. Offer Kubernetes without building a platform team. We run the control planes.

  • You keep the customer and the hardware revenue
  • Their servers stay on your network
  • Wholesale per cluster, with an API for your portal
Become a partner

I want a cluster to build on

A real Kubernetes API, free.

Join a VM, a cheap VPS or the box under your desk. Suspend it when you’re done.

  • Upstream kube-apiserver and etcd
  • Console or API, your choice
  • Goes to production in place, same endpoint
Get a dev cluster

Under the hood

What runs where.

A Standard cluster, drawn as it is. See how it scales, how it’s locked down, and what happens when something fails.

Pricing

Per cluster. Never per core.

Three tiers, one per control plane size. We don’t count your servers, cores or GPUs.

Development

For trying things and CI.

Free

one cluster

  • One API server, one etcd member
  • Suspend and resume any time
  • Move to Standard in place
  • No failover
Get a dev cluster

Most teams

Standard

For production.

$99

per cluster / month

  • Two API servers, etcd in three zones
  • Survives losing a zone
  • Off-cluster snapshots every 5 minutes
  • Email support, business hours
Request access

Performance

For large and bursty clusters.

$599

per cluster / month

  • Everything in Standard
  • Three API servers
  • 10× the control plane resources
  • 24/7 on-call included
Request access

24/7 on-call

An engineer answers your page around the clock. One price covers every Standard cluster in your organization. Included with Performance.

$200per organization / month

Compare tiers in detail
FeatureDevelopmentStandardPerformance
API servers123
etcd members13, in three zones3, in three zones
Survives losing a zoneNoYesYes
Control plane resourcesBaseBase, scales up10× base, scales up
etcd snapshotsEvery 5 minutesEvery 5 minutesEvery 5 minutes
SupportEmailEmail, business hoursEmail and 24/7 on-call
24/7 on-callNot availableAdd for $200 per org / monthIncluded
PriceFree$99 per cluster / month$599 per cluster / month

Hosting provider? Resell managed Kubernetes on your servers at wholesale prices.

Partner pricing

USD. Pay annually, get two months free. Volume pricing from ten clusters.

Compared

The big clouds bill you for every core you bring.

AWS, Google and Azure manage Kubernetes on your servers for a fee on every vCPU. Running a control plane is the same work at 16 cores or 192, so our price doesn’t move.

Your monthly bill, compared

20
vCPUs per server
AWS EKS Hybrid Nodes$9,417per month, billed per vCPU
Kestrel Standard$99per cluster, per month

That’s $9,118 a month you keep.

AWS figure: EKS Hybrid Nodes at published rates ($0.020 per vCPU-hour, tiered down to $0.006) plus $0.10 an hour per cluster, from aws.amazon.com/eks/pricing. AWS prices hosts over 32 vCPUs through sales, so a negotiated bill may be lower. Kestrel Standard is $99 per cluster per month, whatever the size.

Security

How your control plane is locked down.

A control plane holds the keys to everything on your servers. These are the controls today; the full set is available under NDA.

Single tenant

Your own API server, etcd and network segment. Nothing in the path is shared.

Your own CA, mutual TLS

A certificate authority per cluster. Every connection authenticated and encrypted.

Encrypted at rest

etcd on per-cluster keys, secrets envelope-encrypted, backups encrypted before they leave.

No inbound ports

Your servers connect out. Nothing to open in your firewall.

Your IdP, your RBAC

Bring your OIDC provider. Standard Kubernetes RBAC, under your control.

Narrow, logged access

Only on-call engineers, through a recorded break-glass path you can review.

Your audit logs

Every API call, retained and streamable to your own log store.

Patched fast, upgraded on request

Security fixes land within a set window. Version upgrades wait for you.

SOC 2 in preparation. Until then, we’ll walk your security team through it under NDA.

Request the security overview

Who runs it

Operators, not a reseller.

We ran managed Kubernetes control planes inside the large clouds for years. Kestrel is small on purpose: the engineers who built it are the ones on call.

Reliability

How your cluster stays up

Three zones, each with its own power and network. Lose one and the cluster keeps serving.

3 zones
etcd and the API server, spread across a region.
2 of 3
Lose a zone, keep reading and writing.
Backed up
Off-cluster. A missed snapshot pages us.
24/7
A person on call, not just an alert.

Regions

  • us-central1Iowa · three zones
    Live

Coming soon

  • US EastVirginia
  • EuropeNetherlands
  • Asia PacificSingapore

Need another region? Tell us. Early customers set the order.

Questions

Things people ask us.

Do you touch our workloads or data?

Your pods run on your servers and your data stays there. The control plane can reach your nodes for things like kubectl exec and logs, as any control plane does, so on our side that access is limited to on-call engineers and every session is recorded.

What do our servers need?

Linux with containerd or CRI-O, plus kubeadm and kubelet. They only need to reach your cluster’s endpoint on port 6443. Nothing has to reach in.

Why not run kubeadm ourselves?

You can, and the commands on your nodes would be the same. What you’d be signing up for is everything behind the endpoint: etcd across three zones, backups, certificates, upgrades and the pager. That’s the part we take on.

How is this different from EKS Hybrid Nodes or Azure Arc?

They bill for every vCPU you connect, and they work best if you already live in their cloud. We charge per cluster, and the only thing you adopt is upstream Kubernetes.

Is there a limit on servers?

We don’t count them. The control plane grows as your cluster does. If you’re running something very large or spiky, the Performance tier gives you more room from day one.

Do we need 24/7 on-call?

Only if an outage can’t wait until morning. Standard comes with email support in business hours, and the control plane recovers from most failures without anyone stepping in. If you want someone on call, it’s $200 a month for your whole organization.

We’re a hosting provider. How does partnering work?

You offer managed Kubernetes to your customers and we run the control planes behind it. The customer and the server revenue stay with you, and you pay us a wholesale price per cluster. It all works through our API, so it can live in your own portal.

Who at Kestrel can access our cluster?

Only our on-call engineers, through a break-glass process that’s recorded and open to your review. Nobody keeps standing admin credentials.

Early access

Tell us what you run.

An engineer reads every request and writes back, usually the same day.

What would you connect?
Roughly how many servers?

Or write topartnerships@kestrelinfrastructure.com