CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/DevOps & SRE

πŸ› οΈ DevOps & SRE Β· Sankey

Monthly Cloud Cost Breakdown

Where a company's monthly cloud bill goes, by team and by service type, to spot the biggest savings opportunities.

More DevOps & SRE templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Compute is the largest share of the bill
  • Idle non-production environments are a clear saving
  • Data transfer is often missed in estimates

Prompt used

Sankey of a monthly cloud bill of $100,000: $45,000 compute, $20,000 databases, $15,000 storage, $10,000 data transfer, $10,000 other. Compute splits into production $28,000, staging $9,000 and idle dev environments $8,000. Databases split into production $15,000 and non-production $5,000.

Mermaid code
sankey-beta
Cloud bill,Compute,45000
Cloud bill,Databases,20000
Cloud bill,Storage,15000
Cloud bill,Data transfer,10000
Cloud bill,Other services,10000
Compute,Production compute,28000
Compute,Staging compute,9000
Compute,Idle dev environments,8000
Databases,Production databases,15000
Databases,Non-production databases,5000
Storage,Backups,9000
Storage,Application data,6000

Inside this diagram

A Sankey diagram with 13 nodes and 12 flows; the width of each band shows the amount.

Where it starts

  • Cloud bill: 100000

Where it ends up

  • Data transfer: 10000
  • Other services: 10000
  • Production compute: 28000
  • Staging compute: 9000
  • Idle dev environments: 8000
  • Production databases: 15000
  • Non-production databases: 5000
  • Backups: 9000
  • Application data: 6000

All flows

  • Cloud bill β†’ Compute: 45000
  • Cloud bill β†’ Databases: 20000
  • Cloud bill β†’ Storage: 15000
  • Cloud bill β†’ Data transfer: 10000
  • Cloud bill β†’ Other services: 10000
  • Compute β†’ Production compute: 28000
  • Compute β†’ Staging compute: 9000
  • Compute β†’ Idle dev environments: 8000
  • Databases β†’ Production databases: 15000
  • Databases β†’ Non-production databases: 5000
  • Storage β†’ Backups: 9000
  • Storage β†’ Application data: 6000

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

FlowchartDevOps & SRE

GitOps Deployment Flow

How a code change reaches production with GitOps: CI builds and tests, the image tag is written to a config repo, and Argo CD syncs the cluster to match Git.

C4 ArchitectureProDevOps & SRE

Observability Stack (Metrics, Logs, Traces)

A complete observability setup: OpenTelemetry collects metrics, logs and traces from services, which are stored separately and viewed together in Grafana with alerting.

State MachineDevOps & SRE

Incident Lifecycle

The stages of a production incident from the first alert to the postmortem, with severity escalation along the way.

SequenceDevOps & SRE

Incident Response Sequence

Who does what when production breaks: monitoring pages the on-call engineer, an incident channel is opened, customers are updated and the fix is rolled out.

DeploymentProDevOps & SRE

Blue-Green Deployment

A blue-green setup where a new version is deployed next to the live one and traffic is switched only after it passes checks, allowing instant rollback.

FlowchartDevOps & SRE

Infrastructure as Code Pipeline

How infrastructure changes are made safely with Terraform: plan on pull request, policy checks, approval, apply and drift detection.