FinOps Intelligence Dashboard

🏷️

Poor Tagging & Cost Attribution

Missing or inconsistent tags make it impossible to allocate costs to projects, teams, or environments — rendering chargeback and executive reporting unreliable.

Untagged Resources

2,847

▲ 12% this week

Unallocated Cost

$341K

▲ 8% vs last month

Tag Coverage

47%

── Target: 95%

Chargeback Ready

31%

▲ 4% this month

Teams Affected

14

── Across 4 clouds

☁️ AWS — 1,240 untagged

☁️ Azure — 890 untagged

☁️ GCP — 512 untagged

☁️ OCI — 205 untagged

Tag Coverage by Cloud

% resources tagged

Unallocated Cost Trend

Last 6 months

Top Untagged Resource Types

by cost impact

Resource Type	Cloud	Count	Monthly Cost	Coverage
EC2 Instances	AWS	438	$82,400	28%
Virtual Machines	Azure	312	$61,200	41%
EBS Volumes	AWS	890	$34,600	55%
Compute Instances	GCP	274	$28,900	62%
RDS Instances	AWS	142	$19,800	74%

Active Alerts

Tagging issues

438 EC2 instances missing cost-center tag

AWS us-east-1 — $82,400/mo unallocated

2h ago

No tagging policy enforced in Azure

312 VMs across 8 resource groups affected

6h ago

GCP project-level labels incomplete

No environment or owner label on 68% of projects

1d ago

OCI compartment structure misaligned

Business unit mapping incomplete for Q1 billing

2d ago

💻

Overprovisioned Compute

VM sizes too large with always-on dev/test environments. Low CPU/memory utilization below 20% represents the #1 FinOps savings lever — typically 20–40% waste.

Waste Estimate

$680K

▲ Annually

Avg CPU Utilization

14%

── Target: 60%+

Always-On Dev VMs

824

▲ Running 24/7

Rightsizing Savings

$218K

▼ If implemented

RI Waste

$94K

▲ Underused RIs

CPU Utilization Distribution

All VMs across clouds

Waste by Cloud Provider

Monthly $

Top Rightsizing Candidates

Sorted by savings potential

Instance ID	Cloud	Current Size	Recommended	CPU Avg	Monthly Savings	Environment
i-0a4b8f1c2d3e	AWS	m5.4xlarge	m5.xlarge	7%	$1,240	Dev
vm-prod-db-042	Azure	Standard_D16s_v3	Standard_D4s_v3	11%	$980	Prod
instance-gcp-78	GCP	n1-standard-16	n1-standard-4	18%	$744	Test
oci-shape-001	OCI	VM.Standard2.16	VM.Standard2.4	9%	$620	Dev

🌐

No Environment Governance

No separation of dev/test/prod environments, resources running nights and weekends, no lifecycle management — creating security risk, cost leakage, and audit nightmares.

Dev VMs Running Nights

412

▲ 58% waste hours

Weekend Compute Cost

$48K

▲ /month avoidable

Environments Tracked

3/8

── Needs 8/8

Single-Account AWS

1

▲ All in one account

Compute Hours by Env Type (Weekly)

Cloud Account/Project Strategy

Cloud-Specific Environment Problems

☁️

AWS — Poor Account Strategy

Single AWS account for all environments. No account-level blast radius containment. All workloads share billing, IAM, and service limits.

☁️

Azure — Resource Group Misuse

Resource groups used as flat containers rather than environment scopes. No policy inheritance hierarchy. Cost reports span all environments indiscriminately.

☁️

GCP — Everything in One Project

All services deployed into a single GCP project. No project-per-environment separation. IAM over-permissioned and budget quotas not enforced per stage.

☁️

OCI — Flat Compartment Model

Compartment hierarchy doesn't mirror business structure. No child compartments for env isolation. Security and cost policies applied inconsistently.

💰

Lack of Budget Controls & Alerts

No budgets configured, alerts not tied to cost owners — a reactive posture that leads to surprise invoices and CFO escalations.

Teams Without Budget

11/14

▲ 79% uncovered

Last Surprise Invoice

$124K

── 3 weeks ago

Alert Response Rate

12%

── Target: 90%

Forecast Accuracy

±31%

── Target: ±10%

Actual vs Budget by Team

Budget Tool Adoption by Cloud

Recent Budget Breach Alerts

Platform team exceeded budget by 187%

AWS — $48,200 actual vs $16,800 budget. No alert configured.

Today

Data Engineering approaching 90% threshold

GCP BigQuery spend: $31,400 of $35,000 budget

1h ago

Azure Dev subscription has no budget set

12 resource groups, $22,100 spent this month with no ceiling

3d ago

📦

No Reserved Capacity / Commitment Strategy

On-demand usage only with no Savings Plans, Reserved Instances, or Committed Use Discounts — resulting in 10–30% unnecessary cloud spend.

On-Demand Overspend

$310K

▲ Annually avoidable

RI Utilization

42%

── Target: 85%+

Savings Plan Coverage

18%

── Target: 70%

Potential Savings

28%

▼ If fully optimized

On-Demand vs Reserved Usage

Commitment Strategy by Cloud

👤

Shadow IT & Uncontrolled Resource Creation

Engineers spinning up resources freely without IAM guardrails or approval workflows — creating hundreds of orphaned disks, unattached public IPs, and snapshots never deleted.

Orphaned Resources

3,412

▲ Unowned

Unattached Disks Cost

$28K

▲ /month wasted

Idle Public IPs

847

▲ $0.005/hr each

Undeleted Snapshots

12,441

▲ 4.2TB of storage

Orphaned Resource Types

Shadow IT Remediation Timeline

IAM audit completed

Jan 2026 · Found 2,400 over-permissioned roles

Orphaned resource scan deployed

Feb 2026 · Identified 3,412 unowned resources

Approval workflow rollout

Mar 2026 · In progress — 40% teams onboarded

Auto-cleanup policies

Q2 2026 · Scheduled — Terraform + Lambda

Full governance model deployed

Q3 2026 · All clouds covered

🏢

No FinOps Operating Model

Organizational — not technical. No cost ownership per team, no showback/chargeback, no unit economics KPIs, and no monthly cloud review process.

Teams with Cost Owner

2/14

▲ 86% no ownership

Showback Coverage

0%

── Not implemented

Monthly Reviews Held

0

── Last 6 months

Unit Cost Tracked

0/8

── No KPIs defined

Missing Capabilities

Cloud Financial Accountability

No engineer owns cost line items

Engineering-Finance Collaboration

No shared dashboards or reviews

Executive Visibility

No C-suite cloud cost dashboard

FinOps Maturity Model

Recommended KPIs

KPI	Current	Target
Cost per API call	Unknown	$0.0012
Cost per user/mo	Unknown	$4.20
Unit cost trend	Not tracked	-5%/qtr
RI coverage	18%	70%
Tag compliance	47%	95%

☁️

Multi-Cloud Complexity

Different discount models, billing exports, no normalized cost schema, and inconsistent tagging taxonomies make cross-cloud optimization nearly impossible.

Billing Schemas

4

▲ All incompatible

Tagging Taxonomies

4

▲ Not normalized

Unified Dashboard

None

── Not yet built

Anomalies Detected

47

▲ This month

Total Spend by Cloud (Monthly)

Billing Export Complexity

Cloud	Export Format	Normalized	Status
AWS	CUR (massive CSV)	No	Partial
GCP	BigQuery export	No	Not started
Azure	Cost Management API	No	Not started
OCI	Usage API	No	Not started

📈

Poor Forecasting & Budgeting

No predictive modeling, no seasonality analysis, no cost anomaly detection — leaving teams blindsided by 30%+ cost spikes with no proactive action.

Forecast Error Rate

±31%

▲ Last quarter

Undetected Anomalies

23

▲ This month

Avg Cost Spike

+28%

▲ When they occur

Seasonal Patterns

0

── Not modeled

Actual vs Forecast Cost (12 Months)

Prophet-style time-series

🤖

Time-Series Forecasting

Prophet-based models per service, per cloud. Seasonality detection. Trend projection with confidence intervals.

📊

Unit Cost Tracking

Cost per user, per API call, per transaction. Tracked over time. Alerts when unit cost drifts from baseline.

🚨

Anomaly Detection

ML-driven spike detection. Alert within hours not weeks. Root cause attribution per service tag.

🤖

No Governance Automation (Policy as Code)

Manual governance with no Terraform guardrails, no auto-shutdown policies, and no tagging enforcement at deployment time — all governance is manual and reactive.

Manual Governance Tasks

340

▲ /month performed

Policies Automated

4%

── Target: 80%+

Time Spent on Governance

120h

▲ /month engineering

Auto-Shutdown Policies

0

── None deployed

Automation Implementation Roadmap

Terraform modules audited

Jan 2026 · 48 modules reviewed, 0 guardrails found

Tag enforcement via OPA/Sentinel

Mar 2026 · In progress — AWS + Azure piloting

Auto-shutdown Lambda policies

Q2 2026 — Dev envs shut down nights/weekends

Cloud Service Control Policies (SCPs)

Q2 2026 — AWS Organizations SCPs, Azure Policy

Full Policy-as-Code pipeline

Q3 2026 — All clouds, CI/CD integrated

Governance Automation Coverage