Skip to content

Cost allocation & savings

Once cost data is flowing (see Cloud cost management), the next question is usually “whose spend is this?” - that’s what allocation answers. A separate, related screen lists opportunities to reduce spend rather than just attribute it.

Infrastructure → Cost Allocation (/gravity/costs/allocation) breaks down a month’s spend into buckets - by cost center, project, or team, whichever grouping you pick from the toggle at the top - and shows what each bucket cost and what percentage of total spend it represents.

Pick a month with the period field, then choose how to group:

Group byWhat it groups on
Cost centerYour allocation rules’ target tag key (defaults to cost-center)
ProjectSame mechanism, different tag key
TeamSame mechanism, different tag key

Each bucket in the breakdown shows its amount, its share of total spend, and the top services that contributed to it. You can export the current breakdown as CSV or a printable PDF.

Spend that doesn’t match any allocation rule shows up as its own Unallocated bucket, called out with a warning so it doesn’t get missed. If you see a large unallocated share, it usually means resources aren’t tagged with whatever key your allocation rules key off, or no rule matches them yet - see Managed resource inventory for how tagging and tag governance work across your resources.

The Allocation Rules tab is where you define how spend gets split. A rule has:

  • A name
  • A provider scope (a specific provider, or all of them)
  • An optional resource type filter (matched against the record’s service name - leave it blank to match everything)
  • A split algorithm: even (split equally across buckets), custom (you assign a percentage per bucket, must add up to 100%), or usage-weighted (currently processed the same as even)
  • The tag key used to group records (defaults to cost-center)
  • An effective-from date and an active/inactive toggle

Create, edit, or delete rules from this tab. Deleting a rule doesn’t delete any cost data - it just stops that rule from being applied to future breakdowns.

Savings - cost optimization recommendations

Section titled “Savings - cost optimization recommendations”

A separate screen, reachable directly at /gravity/costs/savings (it isn’t currently in the sidebar navigation), lists cost-optimization recommendations: right-sizing, idle-resource cleanup, reserved-instance opportunities, storage-tier changes, and egress optimization. Each recommendation shows the affected resource, its type, an estimated monthly saving, a confidence level, and its status (open, applied, snoozed, or dismissed). A summary banner totals your open potential savings and what you’ve already saved by applying past recommendations.

For an open recommendation you can:

  • Apply it - a confirmation dialog warns that this can trigger a real change to your cloud infrastructure (a resize or deletion), so confirm you understand the impact before proceeding
  • Snooze it for 90 days
  • Dismiss it