Cloud Horizon Get the free audit

Getting started

Start with evidence, not a sales deck.

Cloud Horizon starts with a narrow, read-only look at the cloud bill. You choose whether to begin with a calculator, a 14-day audit, or the marketplace procurement path.

Start the free audit Use the free tools

Pick the path

Start with the free audit

Best when you already have a suspicious line item, a renewal coming up, or a finance question that needs evidence. We confirm by email, send the read-only access steps, and return a one-page report plus the raw findings.

Request audit

Use the calculators first

Best when you are validating one service before involving the team. NAT Gateway, data transfer, VPC endpoints, storage classes, compute, database, and commitment calculators are public and do not require an account.

Open tools

Prepare for procurement

Best when legal, finance, or marketplace purchase flow is already in motion. Review pricing, trust, and the Azure Marketplace readiness page before the buyer account is connected.

Marketplace path

Read-only access checklist

We ask for the smallest access surface that can answer the cost question. No write permissions are required for the free audit.

AWS

  • Management account or payer account contact
  • Cost and Usage Report or Cost Explorer access
  • Read-only IAM role for cost, account, and inventory metadata
  • Optional VPC Flow Logs export for NAT, endpoint, and data-transfer findings

Azure

  • Tenant and subscription list
  • Reader plus Cost Management Reader on the subscriptions in scope
  • Enrollment, MCA, or CSP billing context if available
  • Optional Lighthouse delegation for managed-service partner rollouts

GCP

  • Billing account and project list
  • Billing viewer access or exported billing table
  • Viewer access for resource inventory checks
  • Folder or organization scope if you want cross-project attribution

What to prepare

You do not need a finished FinOps process. These details are enough to make the first report useful.

  • Which cloud accounts or subscriptions are in scope
  • The person who owns the cloud bill
  • Any services that already look suspicious
  • Known renewals, reserved capacity, or savings-plan dates
  • Current tagging rules for team, app, environment, and cost center
  • A preferred reporting format for finance and engineering

The first 14 days

  1. Day 0

    Confirm scope

    We confirm the cloud accounts, the main concern, and the right contact for access. If you came from a calculator, we include that estimate in the first pass.

  2. Day 1

    Connect read-only access

    You deploy the role, service principal, or billing export with least privilege. We verify access and start ingestion without requesting write permissions.

  3. Day 3

    Baseline spend

    We build the monthly and daily baseline by service, account, subscription, tag, and commitment state. Obvious anomalies are reviewed by a human before they reach you.

  4. Day 7

    First findings

    We send the first short list: high-confidence waste, missing attribution, and the changes likely to pay back quickly.

  5. Day 14

    Report and next step

    You get a one-page summary, raw findings, and remediation notes. You can delete access, keep using the free tools, or convert to a paid plan.

Ready when you are

Send the audit request, then reply to the confirmation email with the accounts or subscriptions you want checked first.

Request the free audit Review trust notes