Rateplane
Built for cloud cost review workflows

How teams use Rateplane

Practical workflows for pricing research, billing connections, budget review, allocation, exports, and monthly cloud cost operations.

Useful across cloud cost stakeholders

FinOps
Platform engineering
Cloud operations
Finance
Procurement
Security
SRE
Infrastructure
Data platform
AI platform
Application teams
Leadership
3
Major clouds normalized
Catalog
Compute offers searchable
FOCUS
Export format supported
Public
Catalog access to start

Team workflows

Common operating patterns Rateplane is designed to support.

FO
FinOps owner
FinOps Team

Build a trusted cloud-rate reference before the bill arrives

Use the public catalog to compare AWS, Azure, GCP, OCI, Linode, and Vultr rates, then connect billing data when the team is ready to bring budgets, forecasts, and allocation into the same workspace.

Rate review — Compare instance families and regions before commitments
Budget context — Add account spend when the billing export is ready
Repeatable workflow — Save filters, comparisons, and exports for monthly review
“Start with a rate catalog the whole team can inspect, then layer in imported spend when governance is ready.”
EP
Evaluation pattern
FinOps and finance
Explore
EL
Engineering lead
Engineering Team

Give engineers a focused way to compare cost tradeoffs

Use saved comparisons, pricing filters, and provider pages during architecture reviews so instance choices are evaluated with cost, region, family, and purchase model visible.

Before build — Compare options before infrastructure is provisioned
Shared context — Give platform, app, and finance teams the same numbers
Saved decisions — Keep shortlists and exports tied to the review
“The goal is not another dashboard; it is a cleaner buying conversation before the architecture is locked in.”
EP
Evaluation pattern
Engineering and platform
Explore
FP
Finance partner
Platform Team

Turn cloud spend review into a finance-ready operating rhythm

Use budgets, allocation rules, FOCUS exports, chargeback reports, and account health checks to make cloud spend easier to explain during monthly business reviews.

Access model — Read-only billing setup before optimization workflows
Allocation — Map spend to teams, services, and business units
Exports — Send CSV, JSON, or FOCUS data downstream
“Finance needs traceable numbers, not screenshots from three cloud calculators.”
EP
Evaluation pattern
Finance and procurement
Explore

Enterprise evaluation questions

The questions buyers usually need answered before connecting billing data.

“Can the team compare rates without connecting production cloud accounts first?”
PR
Procurement review
Start with the public catalog, No credentials required
“What changes after billing accounts are connected?”
FR
FinOps review
Budgets, forecasts, allocation, Read-only billing data
“Can engineering export a shortlist for architecture and migration reviews?”
PL
Platform review
Saved comparisons and CSV/JSON exports, Shared decision records
“Does the product expose the source and freshness of pricing data?”
AR
Architecture review
Provider API context and freshness, Traceable catalog
“Can governance actions stay auditable before automation is enabled?”
SR
Security review
Audit events and approval paths, Controlled rollout
“Can finance consume data outside the app?”
RR
Reporting review
CSV, JSON, and FOCUS exports, Downstream reporting

Start with the catalog. Connect billing when ready.

Create a workspace to save filters, connect billing data, and review setup-dependent workflows.

Create workspaceView plans