Requests against use.
Per namespace: requested, limited and used cores, memory and GPUs — and the tenants requesting far above what they use.
Platform engineering and Kubernetes
For platform teams and providers that run Kubernetes for many teams and customers, on their own hosts or in a cloud account: Rymvard shows capacity per cluster, node pool, team and namespace — requests, limits and use — and names the teams that hold capacity they never use.
Read-only. New in version 0.28 — the screens show an illustrative example estate, not a customer.

A namespace requests what it might need and keeps it. The scheduler counts the request, the node sits idle, and the next team is told the cluster is full.
Per namespace: requested, limited and used cores, memory and GPUs — and the tenants requesting far above what they use.
Node pools whose namespace quotas promise more than their allocatable capacity can give.
Tag rules map namespace labels to customers and teams; a namespace without one is counted and named.
What Rymvard shows
Clusters with their distribution and freshness, node pools with allocatable, requested, used and quota — read from the API server and kube-state-metrics.

Kubernetes on your own hosts beside the ledger's servers, or in a customer's cloud account — counted against the capacity underneath.
GPUs requested against GPUs allocatable per node pool, beside the GPU estate on the GPU pages.
Where OpenShift runs on your hosts, its worker nodes count in the Red Hat subscription position.
A cluster read longer ago than its freshness limit shows unknown — never an empty pool.
Rymvard reads requests, limits and use. It never changes a cluster.
New in 0.28 · Workspaces
Platform teams open Rymvard on their own home — tenants requesting far above use, requested but unused cores, pools that cannot deliver their quotas and namespaces without an owner, with AI that explains every number. See the workspaces

Which teams have room — and which hold capacity they never use?
Screens from the running product on its example estate. Customer names appear only for planners and admins — findings never name a customer.
Across every estate
The customer registry resolves every name in the ledger — contracts, racks, cloud accounts, licences — to one customer with its aliases and business groups, and billing and energy statements count it once. Takeover without migration
Your clusters, read-only: every namespace with its owner, its request and its use.