Docs

Cost Analysis

What this screen is for

Cost Analysis shows what your clusters are costing, broken down so the number is actionable rather than merely alarming. It answers “where is the money going?” — Resource Optimization answers “what should we do about it?”

Before you start

To do this You need
Open the page access to at least one environment tier (env-by-branch.<env>.access)

A registered, valid cluster must exist. Cost is per cluster, so with none registered there is nothing to show.

Opening it

  1. Cost › Cost Analysis in the sidebar.

Direct URL: /ebb/cost-analysis

The interface

📸 Screenshot Placeholder: The Cost Analysis page. Mark: (1) the cluster selector, (2) the cost summary, (3) the breakdown.

# Control What it does When you’d use it
1 Cluster selector Chooses the cluster Always — figures are per cluster
2 Summary Total spend for the selection The headline
3 Breakdown Where that spend sits The part you can act on

Read the breakdown, not the total. A total tells you whether to worry; only the breakdown tells you where to look.

Walkthroughs

Find where spend is concentrated

  1. Cost › Cost Analysis, select the cluster.
  2. Read the breakdown from largest to smallest, and stop early. Cost is almost always dominated by a handful of items, and the long tail is not worth your afternoon.

Compare clusters

Switch the cluster selector. A dev cluster costing near a production cluster is usually the finding, not the total.

Scenario

The monthly bill jumped and nobody knows why.

  1. Cost › Cost Analysis, select the cluster that grew.
  2. Read the breakdown and identify the largest contributors.
  3. Check Deploy › Dev for ephemeral environments that were never let go. Dev environments carry a TTL precisely so they do not accumulate — extended TTLs are a common and invisible cost.
  4. Check Analytics for a change in deployment volume around the same time. More deployments can mean more parallel environments.
  5. Move to Resource Optimization, which turns this into specific recommendations rather than a number.
  6. If the increase came from a new environment, confirm it was meant to exist — see Settings › Infrastructure › Environments.

Step 3 first, because it is the cheapest thing to check and the most common cause.

When it doesn’t work

Symptom Cause How to check Fix
Cost is not in the sidebar You have no environment tier access Access Explorer Ask for access to a tier
No clusters to select None registered or valid Clusters Register and validate one
Figures look implausible Cost data depends on what the cluster reports The cluster Treat as directional; verify against your cloud bill
A cluster is missing Registered but not valid Clusters Validate it
Numbers changed with no deployments Often ephemeral environments accumulating Deploy › Dev Let TTLs expire

Next