Cloud Horizons
Open navigation

Assisted beta audit

Cloud Horizons turns cloud bill spikes into owner-ready answers.

During the assisted beta, we connect one AWS, Azure, GCP, or StackIT scope with read-only access and capture the first provider-sync proof before treating finance reporting as live.

Get my 14-day audit Test one workflow

Free 2-month trial. No card required.

4 clouds

read-only sources

AWS, Azure, GCP, and StackIT stay the source of truth

14 days

beta audit window

First provider sync with a written finding list at the end

1 page

finance summary

Forecast drift, top exposure, owners, and the next decision

Scoped

access setup

IAM role, Azure service principal, GCP service account, or StackIT token

Free 14 days, read-only access, one-page anomaly report at the end.

Live: AWS · Azure · GCP · StackIT

scanning

Cloud cost review

This month, by provider — with the spike explained

Live product surface read-only access

Agent question

What changed in our cloud bill this week, and who owns it?

trace cost.summary grouped by provider, service, and owner tag

trace inventory.list filtered by linked account, project, or subscription

trace anomalies.recent with source API path and review status attached

Connected providers

Azure read-only AWS read-only GCP read-only StackIT read-only

Sample figures shown for illustration. Customer values are never shown on the public site.

Provider-native access

Real data, real providers. Real logos, real APIs, no browser scraping. Cloud Horizons normalizes the data while each provider remains the source of truth.

Covers AWS, Azure, GCP, and StackIT AWS Microsoft Azure Google Cloud STACKIT

Audit packet

What the first 14 days produce.

The audit is a short decision packet for finance, FinOps, and platform owners who need to know what changed, who owns it, and what to do next.

Start audit request See setup steps

Day 1

Read-only connection map

Access scope

Exact AWS IAM role, Azure service principal, GCP service account, or StackIT token scope. No agents, no write access, no Terraform change required.

Days 2-7

Anomaly trace

Owner path

Daily deltas grouped by cloud, service, account, region, project, owner tag, and likely cause so the first review starts with evidence.

Day 14

Finance summary and engineer appendix

Decision packet

A short CFO-ready summary plus engineering notes with dollar impact, confidence, remediation options, and what to check in the provider bill.

After review

Feedback-linked product fixes

Launch gate

Pilot sessions close with trust, clarity, speed, and requested-fix feedback. Launch evidence only counts completed real-customer sessions.

Monday morning workflow

From bill surprise to assigned fix before the invoice closes.

The first job is to replace the slow path from billing export to accountable next action. Each finding starts with dollars, owner, source data, and the decision waiting on the team.

Before

A month-end cloud bill jumps and the team has to export CSVs before anyone knows where to look.

After Cloud Horizons

Cloud Horizons opens with the service, region, account, owner tag, daily delta, and likely cause already grouped.

Before

Finance asks whether a spike is one-off usage, missing commitments, or a broken workload.

After Cloud Horizons

The answer separates anomaly, attribution, forecast drift, and remediation so the next action is visible in one pass.

Before

An AI agent can read docs but cannot safely inspect the billing data behind a claim.

After Cloud Horizons

MCP tools expose scoped Azure, GCP, AWS, and StackIT cost context with read-only provider access and traceable outputs.

Readiness ledger

What can be tested today, and what is still gated.

Cloud Horizons is live for assisted beta audits. The public site shows deployment status, Azure Marketplace activation, AI discovery files, customer sessions, and the live-provider evidence still gated before a general rollout.

Open Marketplace flow Check status

Cloud Horizons readiness

Cloud Horizons readiness

What is real, what is blocked, what gets tested next
Live

Customer-facing product pages

Homepage, pricing, pilot, feedback, MCP docs, trust, tools, and Marketplace activation are built and indexed.

Indexed surface

Check

Marketplace backend

Live readiness loads from production APIs on page view.

Live API

Manual

Partner Center preview

The remaining blocker is the browser-only Supplemental Content save, then preview publish and purchase evidence.

UI gate

Open

Customer proof

The customer loop only counts linked feedback from completed sessions, so sample rows cannot make the launch look ready.

Needs customer session

AI-readable cloud operations

MCP surfaces search engines and agents can understand.

Cloud Horizons turns provider APIs into precise tool surfaces, so an engineer or AI agent can ask one cost question and get the same structured answer across Azure, GCP, and AWS.

Azure

azure.cost

Cost Management, Resource Graph, Advisor, Monitor, Service Health, APIM, and Application Gateway data exposed through one agent-safe tool surface. Review MCP docs

GCP

gcp.cost

Cloud Billing, Compute Engine, Cloud SQL, GKE, Cloud Storage, and Monitoring data with project-scoped service account access. Review MCP docs

AWS

aws.cost

Cost Explorer, EC2, RDS, S3, Lambda, CloudWatch, and CloudFront queries for teams that need cost context outside provider portals. Review MCP docs

StackIT

stackit.cost

Project-scoped cost, inventory, OpenStack compute, and S3-compatible storage context for EU sovereignty and DACH workloads. Review MCP docs

How it works

Three steps from signup to first beta audit report. Read-only setup, first provider sync, one-page summary. No upsell call at the end.

01

Connect

10-minute read-only setup. AWS IAM role, Azure service principal, GCP service account, StackIT project token. No agents, no infrastructure changes.

02

See

Assisted beta provider sync, attribution by team and service, and forecast review. The first useful insight lands after access is verified.

03

Act

Remediation playbooks per anomaly type. Lifecycle actions on VMs, AVD pools, and EA commitments with cost preview before you click apply.

What you actually see

What you actually see

Three generated sample views, in this order. Anomalies first, because that is the question on the call this week. Attribution second, so you know who to ask. Forecast third, because next month is already happening.

Cost-change review

Cloud Horizons opens a finding only after source context is attached.

Evidence before alert read-only

+$4,260 / wk

Azure egress · NW-Prod-Payments

  • Provider / account Azure · northwind-prod
  • Service / region Egress · westeurope ↔ northeurope
  • Owner tag platform-payments@northwind

Illustrative sample — no live tenant data.

Cross-cloud attribution

Billing and inventory records are grouped by ownership fields already present in each provider.

Tags, labels, subscriptions read-only

$96,930 / mo

Grouped by owner tag

  • platform-payments $41,820
  • data-platform $28,460
  • ml-research $14,210
  • Untagged (needs owner) $12,440

Illustrative sample — no live tenant data.

Run-rate check

Run-rate and budget questions keep their source, assumption, and review status together.

Budget source required read-only

$96,930

Month to date

  • Last full month $91,720
  • Committed (savings plans) $22,000 / mo
  • Budget source Finance FY26 sheet

Illustrative sample — no live tenant data.

Stunning aerial view of cumulus clouds from above, showcasing fluffy cloud formations.

Across every cloud you touch

AWS, Azure, GCP, and StackIT in one normalized view.

Same anomaly format, same owner attribution, same forecast model. Per-cloud nuance preserved, cross-cloud comparison made possible.

Built for the teams that own the cloud bill

Four buyer profiles we have shaped Cloud Horizons around. Most customers sit in two of these at the same time.

Finance leaders

CFO and VP Finance at companies where cloud is now in the top three line items and procurement wants a number on a pricing page.

Platform engineers

Single platform engineer responsible for AWS plus Azure plus a GCP project they inherited. The "I do not have a FinOps team" archetype.

Managed-service partners

Microsoft and AWS partners managing dozens of customer tenants. Lighthouse and AWS Organizations as the access primitive.

EU sovereignty teams

DACH-region IT leaders evaluating StackIT and other sovereign clouds because the regulator asked. We cover Schwarz Group cloud out of the box.

Customer-tested workflow

Bring one real workflow. We turn the friction into the next fixes.

The customer pilot is for current customers and friendly teams who can test Cloud Horizons against a real AWS, Azure, GCP, StackIT, or MCP question. Every session ends with a short scorecard and a product follow-up.

Join the pilot Review MCP docs

Workflow

Which cloud-cost task should be faster than spreadsheets or billing exports?

Trust

Where does the answer need more source detail, math, or provider context?

Adoption

What would make the team use Cloud Horizons again next week?

Vibrant close-up of a computer screen displaying color-coded programming code.

Built by

Spot Cloud B.V., the team behind Cloud Horizons and Spot Suite

We build and operate cloud platform software full time. We built Cloud Horizons because we got tired of writing the same anomaly detection scripts for every workload we touched.

Pricing

Three tiers, banded by your monthly cloud spend. Cancel any time.

See full pricing

Starter

$149 /mo

Up to $100K monthly cloud spend

  • AWS + Azure
  • Reviewed anomaly findings
  • Tag and account attribution
  • Email + Slack delivery

Growth

$399 /mo

Annual prepay saves 15%

Up to $500K monthly cloud spend

  • Everything in Starter
  • GCP support
  • Forecasts and budget tracking
  • Remediation playbooks
  • Quarterly review with our team

Business

from $999 /mo

Above $500K monthly spend

  • Everything in Growth
  • Multi-org and multi-account
  • SSO, audit log, custom roles
  • Dedicated infra engineer

From the blog

Practical cloud cost writing, linked from the product.

Use the blog to validate how Cloud Horizons thinks about anomalies, attribution, MCP surfaces, and the cloud line items teams keep missing.

Read all posts

Common questions

Four short answers before a security review.

Use these to check whether Cloud Horizons fits your cloud mix, access model, and MCP plans.

What is Cloud Horizons? +

Cloud Horizons is an assisted beta surface for one answer across AWS, Azure, GCP, and StackIT billing plus ownership attribution, forecast signals, and MCP after connected data is verified.

Does Cloud Horizons support MCP for Azure and GCP? +

Yes. Cloud Horizons publishes an MCP configuration and exposes provider-aware tools for Azure Cost Management, GCP Billing, AWS Cost Explorer, and StackIT cost and inventory data.

Do I need to deploy agents or change Terraform? +

No. The default setup is read-only and uses the same cloud access primitives teams already use: AWS IAM roles, Azure service principals, GCP service accounts, and StackIT project tokens.

Can customers test Cloud Horizons now? +

Yes. Current customers and friendly pilot teams can join the customer pilot to test real AWS, Azure, GCP, StackIT, and MCP workflows, then share feedback on trust, clarity, and adoption blockers.

Request a free audit

Three fields. We confirm by email and offer a slot for the free 14-day audit.

Or email hello@spot-suite.com directly. We reply within one business day.