I find and eliminate hidden cost in EKS deployments — compute, observability, egress — and implement the fixes myself. Free infrastructure audit. No commitment, no slide decks.
For Series B–D SaaS teams running Kubernetes on AWS.
If you're spending real money on EKS, at least one of these is almost certainly running right now.
Most clusters run near 35% utilization while paying for 100%. Without Karpenter and proper autoscaling, mid-scale EKS deployments commonly carry idle capacity worth real money every month.
Often $5–50K/moHealth-check logs, debug noise, and redundant traces ship to Datadog at full price. Teams typically waste 30–50% of observability spend on logs nobody reads.
Typically 30–50% of spendEvery byte between availability zones is billable. Without topology-aware routing, an internal service mesh can silently generate thousands — sometimes far more at scale — in transfer fees.
$10–30K/mo at scaleEvery audit runs the same way. Here's exactly what I do.
Where the money actually goes, broken down by workload.
Provisioned vs. real usage — measured at p95, not misleading averages.
Compute, observability, network — each with a confidence range, not a single guess.
Ranked by dollars recoverable vs. effort to capture them.
The initial scoping conversation needs no infrastructure access — just your current spend profile and architecture context.
A short call to map your architecture and spend profile. No access required at this stage.
Under NDA, with read-only, least-privilege access you can revoke in seconds, I run a structured hands-on review across compute, observability, and network — and deliver a findings report. No write access, no production changes.
If the numbers justify it, I implement the fixes in coordination with your team — Karpenter, log-pipeline cleanup, topology routing. Terraform and YAML, not PowerPoint. Typical result: 20–35% reduction in Kubernetes infrastructure costs within ~90 days; actual results vary by environment and show up in your audit.
Right-sized nodes, Karpenter + spot automation, VPA tuning.
Typical: 20–30% of compute spendLog-pipeline filtering, retention tuning, instrumentation cleanup.
Typical: 30–50% of Datadog costTopology-aware routing, NAT Gateway optimization, egress reduction.
Typical: 20–50% of transfer costRanges are typical opportunities and vary by setup. Your audit shows your specific numbers.
It's not a pitch disguised as a review. You get a written findings summary either way. If I don't find meaningful, recoverable waste, I'll tell you that directly on the call — and we part ways with no invoice and no obligation. I only take on work I'm confident will pay for itself.
K8s Cost Ops is a specialized practice focused on one thing: finding and eliminating hidden cost in Kubernetes infrastructure.
I've spent 7 years building and operating production Kubernetes at enterprise scale — high-compliance, high-stakes environments where a misconfigured node group or an unfiltered log pipeline quietly burns tens of thousands a month before anyone notices.
I don't consult from the sidelines. I write the Terraform, tune the Karpenter configs, and clean the Datadog pipelines. You get engineering execution, not a report you have to act on yourself.
2-business-day turnaround. NDA first. Read-only access, revocable anytime. No obligation.
Prefer to talk first? Book a 15-min call →