Skip to main content
Version: v1.0.0

Cost Groups

The Cost Groups page lets users logically group resources and view costs in a way that aligns with business structure.
Instead of looking at raw infrastructure, costs can be organized by teams, projects, or environments.

Why Cost Groups?​

Cloud bills are often fragmented across clusters, namespaces, VMs, and storage.
Cost Groups help:

  • Create custom groupings of resources
  • Track spend against departments, cost centers, or projects
  • Enable chargeback/showback for financial accountability

Creating a Cost Group​

  1. Click “Create Group”
  2. Select the resources to include:
    • Kubernetes clusters, namespaces
  3. Give the group a name (e.g., "Database Team – Production")

Group Insights​

Once created, the following will be visible:

  • 📊 Total cost of the group
  • 🔎 Breakdown by resource type (cluster, namespace)
  • 📈 Historical trend chart to track growth over time (daily trend graph)
  • 🎛️ filters (date range resource type) to refine the view and focus on specific periods or resource categories for deeper analysis

Common Use Cases​

  • Department View → Finance, Engineering, Marketing
  • Environment View → Production, Staging, Development
  • Project View → App Launch, Migration Project, R&D

🎯 Tip: Cost Groups turn raw data into business-aligned insights that executives and managers can actually act on.

Advanced Cost Group Features​

Tagging and Labels​

Cost Groups can automatically include resources based on:

  • Kubernetes Labels → team=frontend, env=production
  • Cloud Tags → AWS/Azure/GCP resource tags
  • Custom Attributes → Business-specific categorizations

Group Hierarchies​

Create nested cost groups for complex organizations:

Company Total
├── Engineering Division
│   ├── Frontend Team
│   ├── Backend Team
│   └── DevOps Team
└── Product Division
    ├── Marketing Team
    └── Analytics Team

Cost Group Analytics​

Each group provides detailed insights:

  • Cost Trends → Historical spending patterns
  • Resource Efficiency → Utilization vs cost metrics