Containers
Kubernetes costs, allocated and explained
EKS natively (AWS Split Cost Allocation with Kubernetes labels, no agent, or AWS-managed usage metrics), GKE natively (GKE cost allocation labels, no agent), and AKS or other clusters through a Kubecost or OpenCost export
How Costory connects to Kubernetes
Costory ingests Kubernetes through EKS natively (AWS Split Cost Allocation with Kubernetes labels, no agent, or AWS-managed usage metrics), GKE natively (GKE cost allocation labels, no agent), and AKS or other clusters through a Kubecost or OpenCost export. Kubernetes spend is normalized into the same cost model as your other providers and allocated with cluster, namespace, label, team; idle/waste ratio per node pool.
Questions you can ask
“What does each namespace cost per week on our EKS clusters?”
“What is our Kubernetes waste ratio by node pool?”
“Schedule a weekly report of Kubernetes cost per namespace.”
Good to know
Cluster cost is shared; namespace allocation needs usage metrics, not just node tags.
Official tooling
Kubernetes also has its own tooling: Kubecost MCP (read-only, v3.3+). Costory adds cross-provider allocation and event context on top. Compare options.
Use Kubernetes with your AI assistant
Setup guide: Kubernetes in the Costory docs.
Playbooks
Playbooks that use Kubernetes
What the Costory agent can watch, investigate and report on for you, with this in the loop.
All playbooks
Costory notices
Every Monday at 9:00, for each team.
Weekly showback per team, posted in each team's Slack channel
Every engineering team gets its own weekly cost report in its own Slack channel, scoped to the services it owns.
See the playbook
Costory notices
Daily, as Datadog usage and the EKS bill refresh.
Dynamic cost reallocation for EKS using Datadog usage
Split shared EKS cluster costs across teams in proportion to what each team's workloads actually use, measured in Datadog.
See the playbook
Costory notices
Every day, for every cluster and namespace.
Kubernetes cost allocation by namespace, team and workload
Break EKS, GKE and AKS costs down by cluster, namespace and workload, and roll them up to teams.
See the playbook
Costory notices
A new account, project or cluster appears in billing.
Split production and non-production costs automatically
Allocate every cost line to prod, staging, dev or sandbox using account names, projects, clusters and labels.
See the playbook
Costory notices
Idle capacity in a node pool stays above your threshold.
Find over-requested Kubernetes workloads and right-size requests
Measure the gap between requested and available CPU and memory, convert it to cost, and get request changes per deployment.
See the playbook
Costory notices
A tenant's infrastructure cost grows faster than its plan.
Cost per tenant for multi-tenant SaaS
Allocate shared infrastructure to tenants using labels, namespaces or usage metrics, and track infrastructure cost per client.
See the playbook
Connect in under 30 minutes. Get your first optimization recommendation the next day.
30-day free trial. Copilot, €250/month, or Copilot Pro, €1,000/month, billed annually.
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Setup
About 30 minutes
Data residency
EU
Access
Read-only on your cloud