Cost and savings
Seylo helps you spend less on Kubernetes without taking risks you did not choose to take. In the portal it is one page, FinOps → Cost & savings, with three tabs:
| Tab | What it answers | Changes your cluster? |
|---|---|---|
| Cost | What the cluster costs at list price, where the money goes, what each team, label or namespace spent, and every figure that is not priced — with what would price it. See cost and the price book and chargeback | No. It is read-only |
| Dashboards | Cost over days and weeks: by namespace and workload, idle, and what grew, from Seylo’s FinOps templates or your own. See cost dashboards | No |
| Savings | How much the cluster could save and where: one headline in dollars and four levers you tick - fewer nodes, rightsizing, spot, schedule - with the machines today against after. See Savings and the node reduction plan | No. What you send becomes an approval request, unless an admin switched on managed savings for the cluster |
What Seylo may change on its own - Nightshift’s fixes, the grants behind them and managed savings - is on Operate → Automation. It replaced the Autoscale tab in 0.4.9.
Old links still work. /cost opens Cost, and /autoscale and the old
Autoscale tab open Operate → Automation. /insights and the old
Usage tab open Savings: the usage
evidence that used to be a separate table now sits under each right-sizing
proposal. Some messages still name the old Cost & proposals tab; that is
the node reduction plan on Savings.
To make the figures match what you are actually invoiced, connect your Azure subscription as a cloud account: Seylo then prices your nodes from your own Azure bill, with no key. See make the figures match your invoice.
Seylo never invents a number
Section titled “Seylo never invents a number”Every figure on these tabs is either sourced or shown as a dash with the reason. Seylo does not fill a gap with an estimate, an average from a similar cluster, or a guess from a similar instance type.
- A node with no price on file is unpriced, and the reason says which:
no price on file for Standard_D4as_v5 in westeurope, for example. It is left out of every total, and the total says it is a floor. - Anything that is not priced is listed with why, what would price it, and — where you can fix it — the command or the control that does. See every “not priced”, and its fix.
- A workload with too little history gets no recommendation, and the message says how much history it has and how much it needs.
- A metric the cluster’s source cannot report — network I/O from metrics-server, say — is absent, not zero.
- On a namespace-scoped agent, anything that needs Nodes is reported as unavailable with the reason, never as zero.
The cost of this rule is that a young cluster, or one on a cloud Seylo cannot price, shows more dashes than numbers. That is deliberate: a savings figure is the number most likely to end up in a business case, and a confident wrong one does more harm than a blank.
Nothing changes without a decision
Section titled “Nothing changes without a decision”Propose-and-approve is the default. One approval is sufficient, and
self-approval is permitted: an approver or admin may approve their own
request. It is not two-person control. See
roles and permissions.
Every change goes through the same engine as any other change Seylo makes: the ownership check, a dry run, server-side apply and a read-back. A change to a workload that Helm, Argo CD or Flux owns is refused until someone acknowledges the owner by name — and an unattended change to one is never made at all.
Node savings come from your side, not from a cloud API
Section titled “Node savings come from your side, not from a cloud API”Seylo holds no cloud credentials for agent-managed clusters, and never calls a cloud API to resize a node pool. Right-sizing frees capacity inside the cluster; a node only disappears when your autoscaler — Cluster Autoscaler, Karpenter, or your cloud’s managed autoscaler — removes it, or when you change the pool yourself.
So the node part of a proposal is a recommendation: which nodes could go, what is pinning the rest, and what each blocker needs. Seylo does not remove nodes, and does not change node pool bounds. See the scale-down report.
Managed savings, if you switch it on, goes one step further, still without a cloud credential: with your permission it writes your own node autoscaler’s objects in the cluster (a Karpenter or AKS node auto-provisioning NodePool), and your autoscaler creates and removes the machines.
Right-sizing also lowers what you pay Seylo
Section titled “Right-sizing also lowers what you pay Seylo”Seylo’s platform fee is metered on the CPU your pods request in the namespaces it manages, not on node size. See plans and billing.
So an approved right-sizing that lowers CPU requests lowers your Seylo bill as well as your cloud bill — even before any node is removed, because the fee follows requests, not nodes.
Roles on these tabs
Section titled “Roles on these tabs”| Action | Role |
|---|---|
| Read cost, chargeback, savings, managed savings and grants | viewer |
| Send a right-sizing or file savings tasks for approval; submit items of the node reduction plan | releaser |
| Suspend or resume a grant, Pause all automation, Stop managing savings | releaser |
| Approve or reject any of the above | approver |
| Request a new grant; switch managed savings on, renew it, or restore the original values | admin |
| Refresh or upload prices; state a cluster’s AKS pricing tier | admin |
Stopping automation needs a lower role than starting it, on purpose: the ability to stop an automated system should never be scarcer than the ability to start one.
Whole-cluster figures. Node prices, idle cost, node bin-packing, unclaimed volumes, the billing integrations and spend outside the cluster are shown only to people who see the whole cluster. Someone limited to some namespaces sees the figures for those namespaces.
What Seylo does not do
Section titled “What Seylo does not do”- No invoice reconstruction by default. Figures are at public list prices unless you connect your Azure bill, upload your own rates or connect a billing integration, and some charges — disk transactions, snapshots, the shared load balancer’s rules — cannot be priced from what a cluster reports. Each is listed with its reason. See what the figures cover.
- No billing credential. Your Azure bill is read with the Reader role you grant Seylo’s app, with no key. A billing integration runs inside your cluster, with a Secret you create or an identity you grant. Seylo never receives it.
- No node removal and no node pool changes. See above.
Related
Section titled “Related”- How usage is collected
- Approvals — where a savings proposal goes
- Plans and billing — why right-sizing lowers your Seylo bill