With vs without an in-cluster agent
Pod-level allocation needs in-cluster metrics (Kubecost, OpenCost). Namespace-level allocation can often be done from provider billing exports plus Kubernetes labels alone — no agent required. The right answer depends on whether 'which pod' or 'which namespace' is the regular question.
Common allocation models
Per-request: split each node-pool's cost by aggregated CPU request fraction across namespaces. Per-node-pool ownership: pin pools to namespaces via taints. Per-namespace: dedicate pools to top namespaces, pool the rest into a shared bucket.
Who tovin.io is for
Frequently asked
Is Kubecost the only option?
No. OpenCost is the CNCF-backed open-source alternative. Provider billing + labels covers namespace-level without an agent.
Does DOKS support label-based allocation?
Yes. DOKS surfaces cluster and node-pool labels on the backing Droplets, which makes label-driven allocation work from DO billing alone.