Skip to content

Perspectives

Perspectives map your cloud resources and spend to business entities — teams, products, environments, cost centers, and applications — so you can analyze and allocate cost in terms your business understands.

When to use Perspectives

  • You want Cost Explorer filters that match your organization structure (team, product, environment) rather than cloud accounts.
  • You need to assign budget ownership to a team or product, not just an AWS account.
  • You want anomaly detection scoped to a specific application or environment.
  • You want to give a team lead access only to their team's cost data.

Open Perspectives

Go to Organization > Perspectives from product navigation.

Beta feature

Perspectives is currently marked Beta. Core functionality is available, but some advanced features may change.

Create a Perspective

  1. Click the create action.
  2. Choose a category — for example, Team, Product, Environment, or Cost Center.
  3. Add conditions that identify matching resources:
    • Filter by provider, service, region, account, tags, resource groups, or other supported fields.
    • Conditions are evaluated as AND — all conditions must match.
  4. (Optional) Link Unit Economics metrics to this Perspective.
  5. Enter the Perspective name and assign an owner.
  6. Configure budget or advanced options if shown.
  7. Review the generated preview — confirm the matched resources look correct.
  8. Save.

Manage Perspectives

  • Edit — update the conditions, name, or owner.
  • Hierarchy Map — view and manage relationships between Perspectives. Use fullscreen for larger estates.
  • Perspective Anomalies — detect unusual spend changes within this Perspective's scope.
  • Clone — duplicate a Perspective as a starting point for a related scope.

Use Perspectives across CloudVerse AI

Once created, Perspectives are available as filters and groupings in:

  • Cost Explorer — group or filter by Perspective
  • Budgets — scope a budget to a Perspective
  • Anomaly Detection — monitor anomalies within a Perspective scope
  • Chargeback & Allocation — allocate costs based on Perspective rules
  • Users & Roles — assign a Dynamic Perspective scope to limit user visibility

Best practices

  • Assign an owner to every Perspective — it should be clear who is accountable for that scope.
  • Make Perspective boundaries as mutually exclusive as possible to avoid double-counting.
  • Preview matched resources before saving — a misconfigured condition can silently miss resources.
  • Recheck Perspective coverage after tag changes, account additions, or org restructures.
  • Start with a few key scopes (main teams, environments) before expanding to granular Perspectives.