Recon is not built yet.

It is meant to answer one question about a Kubernetes cluster — which namespace, team or service is responsible for the bill. Right now it is a prototype on a laptop, nothing you can install.

This page exists to find out whether you have that problem badly enough to want it solved. If you do, say so and you will hear from us when there is something real to try.

Tell us you have this problem

Status · in development · no install

kubectl can’t tell you what things cost.

You know the AWS bill is growing and you know the cluster is a large part of it. What you cannot get from a cluster is the split — which namespace, which team, which service.

So the conversation stops at the total. Requests get set once and never revisited, idle pods bill at the same rate as busy ones, and cross-AZ traffic shows up as a single line nobody can trace back to a service. None of that is a monitoring problem — it is an attribution problem, and it is the one Recon is being built for.

What Recon is being built to do.

Not a feature list — a list of intentions. Every item below is unbuilt. If one of them is the thing you actually need, that is worth telling us, because it changes what gets built first.

  • Cost per namespace, deployment and pod

    Planned

    The question kubectl cannot answer: which namespace is responsible for the line on the invoice. Recon will map resource usage onto real cloud pricing and attribute it.

  • Idle and over-provisioned resources

    Planned

    A pod that requests four CPUs and uses a fraction of one costs the same as a busy one. Recon will flag the gap between what is requested and what is used.

  • Right-sizing you can act on

    Planned

    Not a chart to interpret — a concrete request change you can apply. Turning the flag into a suggestion is the harder half, and it is not built.

  • Network cost attribution

    Planned

    Cross-AZ and cross-region traffic is billed but rarely attributed. Recon will trace it back to the services generating it.

These four work today.

Recon is the long way round to answering the cost question. In the meantime these calculators are free, need no signup, and run in the browser.

NAT Gateway Calculator

AWS NAT Gateway costs per hour and per GB, by region.

EKS Pricing Calculator

Estimate AWS EKS costs with EC2 or Fargate compute.

K8s Cost Estimator

Compare monthly cluster costs across EKS, GKE and AKS.

Container Size Calculator

Right-size CPU and memory requests for Kubernetes pods.

Do you have this problem?

There is nothing to sign up for and nothing to try. Leave an address and you will hear from us once Recon does something useful — or sooner, to ask what your cluster actually costs you.

No spam. You will hear from us when there is news, and not otherwise.