Multi-cloud cost visibility, built in Canada

Xplorr exists because managing AWS, Azure, and GCP costs shouldn't require three dashboards, a spreadsheet, and a dedicated FinOps hire. We built what we couldn't find.

Our mission

Cloud costs are one of the biggest operational expenses for modern engineering teams, yet most teams still discover budget overruns from a monthly invoice, not a real-time alert.

We believe every team should know where their cloud money is going, in real time, without needing a data warehouse, a BI tool, or a dedicated FinOps engineer.

Xplorr gives engineering and finance a shared language for cloud costs. Less friction. More visibility. Fewer end-of-month surprises.

Read only
Access to your cloud accounts
5
Providers, including OpenAI and Anthropic
FOCUS
Billing exports read in the open standard format
Free
Plan for 1 cloud account, no credit card

What we believe

Transparency

Cloud costs should be visible to everyone on your team, not locked inside a billing console that only one person knows how to navigate.

Speed

Full cloud cost visibility you set up yourself, not after a three-week onboarding with a solutions engineer.

Security

We never ask for permissions to create, modify, or delete resources. Read-only access is a hard architectural constraint, not a policy promise.

Privacy

Your billing data is stored and processed exclusively in Canada. We made this a founding principle, not an afterthought.

Who builds Xplorr

Xplorr was founded by Harmanjyot Kaur, who is based in the Greater Toronto Area and is also CEO of CloudDrove, the cloud and DevOps engineering partner that builds Xplorr.

CloudDrove has spent years running cloud platforms for other engineering teams, which is where the multi-cloud billing problem Xplorr solves came from. That work is also why the product is built read only, around your own cloud accounts, rather than asking you to move your billing data somewhere else.

Where we've been

Q2 2025

Founded

Xplorr was founded after our team spent years dealing with multi-cloud billing chaos at previous companies. We knew the problem and decided to solve it.

Q1 2026

Private beta on AWS

The platform was built and the first cohort of engineering teams connected their AWS accounts, reviewing their spend in one place instead of three consoles.

Q1 2026

Azure and GCP

Microsoft Azure and Google Cloud support, so spend across all three clouds is normalised into one set of cost views rather than compared by hand.

Q1 2026

Agents, integrations and enterprise security

A Slack bot with 18 tools, an MCP server with 28 tools, daily digests and weekly AI summaries, with a Microsoft Teams bot in development. Alongside them WebAuthn passkeys, TOTP 2FA with mandatory enforcement, scheduled reports, tagging policy enforcement and the platform admin panel.

Q3 2026

Kubernetes, commitments and carbon

Kubernetes cost allocation down to the namespace and workload, commitment and reservation coverage, invoice reconciliation, MSP rebilling and carbon emissions reporting.

Q3 2026

Beyond the cloud bill

Cost sources that never appear on a cloud invoice: OpenAI, Anthropic, Datadog, Snowflake, Databricks, and GitHub with Actions minutes by runner OS and the included allowance you have already consumed.

October 2026

Self serve signup and paid plans

Anyone can sign up on the Free plan, upgrade to Growth at USD 49 per organization per month, or talk to us about Enterprise. Organizations from the private beta keep their plan.

Want to learn more?

Questions, partnerships, or just want to talk cloud cost strategy? We read every email.