Cost Optimization · AWS

Karpenter, set up so your EKS bill follows real demand.

Karpenter adds and removes servers in your EKS cluster automatically. We set it up properly, with Spot servers (spare AWS capacity sold at a discount) and a safe fallback, so you stop paying for servers that sit idle.

  • 200+ open-source Terraform modules
  • 24x7 support plans
  • Rated 5.0 on Clutch
karpenter.tfscaling
Karpenter logoKarpenter
Amazon EKS logoAmazon EKS
Amazon EC2 logoEC2 Spot
AWS logoAWS
Terraform logoTerraform
Helm logoHelm
Kubernetes logoKubernetes
Prometheus logoPrometheus

The challenge

Servers sized for the busiest day, paid for every day.

Teams try Karpenter or Spot to fix it, but a rushed setup brings new problems.

Half-empty servers

Most EKS clusters keep fixed groups of servers sized for the busiest day, so most of the time they sit half empty.

Apps reserve too much

Apps reserve far more CPU and memory than they use, so even an autoscaler keeps buying servers you don't need.

Spot surprises

AWS takes Spot servers back with a two-minute warning, and there is no fallback when Spot capacity runs out.

What we set up

Karpenter and Spot, done safely.

Installed from code, so your team can read it and change it.

Right-sized apps first

Karpenter only saves money if apps ask for the right amount. We measure real usage and right-size each app's CPU and memory requests (the amount it reserves) first.

Explore Cost Optimization →

Karpenter installed from code

Our open-source terraform-aws-karpenter module sets up its AWS permissions, server profile, and Helm install.

See terraform-aws-karpenter →

Spot first, safe fallback

We give Karpenter a wide mix of server types, with Spot first and On-Demand as a fallback when Spot runs out.

  • Spot
  • On-Demand fallback
  • Many server types

Spot warnings handled

When AWS sends its two-minute warning, apps move to another server before the old one goes away. Add-ons like the AWS Node Termination Handler are installed with Helm, from code.

Read: Karpenter and Spot on EKS →

Servers that follow demand

The cluster grows when traffic grows and shrinks when it drops, with guardrails that protect uptime.

Free waste calculator →

Built for Amazon EKS

Karpenter is most mature on AWS. Our setup and our open-source Karpenter module are built for Amazon EKS.

Amazon EKS consulting →

How we work with you

Four steps, done together with your team.

1

Agree a starting point

Today's monthly server spend, and how full your servers really are.

2

Right-size

We fix what each app asks for before anything else changes.

3

Test in dev

We roll out Karpenter in dev and test real Spot interruptions.

4

Roll out and compare

We move production apps over in small groups and compare the result with the starting point.

The result: a cluster that grows when traffic grows and shrinks when it drops, with guardrails that protect uptime, and a setup your team can read and change in code.

Open Source & Tools

Check our work first.

Proof

Capacity matched to demand.

Related Reading

Go deeper.

FAQs

Questions, Answered.

What is Karpenter, in simple terms?

Karpenter is a free, open-source tool that adds servers to your Kubernetes cluster when apps need room, and removes them when they are no longer needed. It also picks the server type and size that fit best.

How is Karpenter different from the Cluster Autoscaler?

The Cluster Autoscaler grows and shrinks fixed groups of servers you defined in advance. Karpenter looks at what is waiting to run and starts the right server type for it directly, which usually packs work more tightly and reacts faster.

Is Spot safe for production?

For many apps, yes. Apps that can restart safely, like web services and workers, run well on Spot when you allow many server types and keep On-Demand as a fallback. Databases and other apps that hold data usually stay on On-Demand.

How much will we save?

We don't promise a number before we look. Our free Kubernetes Waste Calculator gives a first estimate. In a project, we measure your real spend before we start and compare it with the result at the end.

Do we need Amazon EKS to use Karpenter?

Karpenter started on AWS and is most mature there. Our setup and our open-source Karpenter module are built for Amazon EKS.

Industries

Industries We Commonly Support

Cloud Infrastructure Assessment

See exactly where your cloud stands.

A senior engineer reviews your architecture, cost, security, and reliability, then sends back a prioritized findings report, the fixes that matter most, in order.

  • Architecture & scale
  • Cost & efficiency
  • Security & reliability
Book an Assessment

Complimentary · no obligation · no sales pressure

Work With Us

Paying for EKS servers that sit idle? Let's talk.

Tell us how your cluster scales today and we'll show you what a safe Karpenter and Spot setup looks like for your workloads.

Talk to an Expert