Cloud Cost Explorer

Break down infrastructure spend by service, environment, region, team, and provider with cost anomalies and trends. This example brings Overview and Services together so engineering teams can find the next task without losing context.

It includes representative records such as Compute and Databases. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Cloud Cost Explorer
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Create budget

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Engineering and security teams need to create budget while keeping monthly spend, forecast and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Overview gives users an obvious place to start.
  • Supporting view: Services keeps the related context close.
  • Primary action: Create budget stays visible when people need it.
  • First signal: Monthly spend shows a useful value (184k).
  • Second signal: Forecast gives additional context (191k).
  • Sample record: Compute.
  • Next record: Databases.

States worth designing

  • No results for the selected range: say what changed, protect progress, and offer a clear next step.
  • Refreshing with old values visible: say what changed, protect progress, and offer a clear next step.
  • Metric source unavailable: say what changed, protect progress, and offer a clear next step.
  • Filter changed the interpretation: say what changed, protect progress, and offer a clear next step.
  • Export preparing: say what changed, protect progress, and offer a clear next step.
  • Restricted data hidden: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → Services → Create budget → Review outcome

Patterns used

Analytics, Overview, Services, contextual actions, error recovery

Why these choices work

Keep the time range and metric definition visible. Let people see which segment or filter produced the result, then explain missing or delayed data.

Pay attention to overview and services. People need to distinguish Compute from Databases. Keep monthly spend visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Create budget”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Infrastructure Overview, Database Monitor, Incident Timeline.

Start from this in Figr

Design a cloud cost explorer screen inside our existing product. Use our current components, tokens and content language. Include Overview and Services views, credible records like Compute, and a clear “Create budget” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr