Skip to main content

Saved views

AvailableReviewed 24 August 2026

CloudHealth Perspectives are lenses (Environment, Team, Cost Center) with groups (production, checkout, finance). They drive reports, policies, recommendations and chargeback.

FinomateAI splits that into:

  1. Saved views (this page) — reopen the same Cost Explorer scope.
  2. Cost categories — allocate provider cost to products, teams and shared platforms.

Use both with Cost Explorer. A view without a category is a bookmark. A category without a view is a chargeback table nobody opens.

Saved views list with weekly FinOps review and team-scoped views
Sample organisation using illustrative billing data.

Why you would create views​

The same CloudHealth reasons apply:

StakeholderLens they need
FinanceCost centre or product line
FinOpsEnvironment (prod vs non-prod)
EngineeringApplication or team
LeadershipOrganisation-wide All-clouds view

Without a named view, every weekly review rebuilds filters. With a view, the meeting opens on the agreed slice.

Types of view​

ViewTypical filtersOwner
Weekly FinOpsAll clouds, last 30 days, group by serviceFinOps
Production onlyEnvironment or account list that is prodPlatform
Checkout platformProduct tag or linked accountsProduct engineering
Data productsDedicated account / subscriptionData platform

CloudHealth distinguishes dynamic groups (tag values create groups automatically) from static groups (you add groups by hand). The intended FinomateAI category rules follow the same split — see Cost categories.

Workflow​

  1. Open Cost Explorer and set provider, range and group-by.
  2. Select Save view.
  3. Name it for the meeting or team.
  4. Assign an owner who will maintain it.
  5. Share it with FinOps and the owning engineering group.
  6. Open the view next week instead of rebuilding filters.
Save view form with name, owner, scope and share list
A view without an owner dies the first time filters drift.

Fields​

FieldPurpose
NameWhat the review is called
OwnerWho maintains it
ScopeProvider, range, group-by, tags
Share withTeams who will open it, not “everyone”

Best practices (same as CloudHealth Perspectives)​

  • Start with a small set of lenses: Environment, Product, Owner, Cost centre.
  • Tags are case-sensitive. Prod, prod and Production are three groups unless you merge them.
  • Do not put an asset in two groups inside the same lens. An asset can belong to Environment=production and Product=checkout.
  • Review unallocated until finance accepts the remainder. Hiding it is how chargeback goes wrong.

See Compared with CloudHealth for the full mapping.