FinOps Co-Pilot ships with a guided onboarding checklist. You connect a cloud account with a provider-native trust model, verify the data you are about to rely on, then move through waste detection, pull request cost analysis, policy guardrails, and ChatOps approvals — in that order.
Cloud accounts connect through provider-native trust models. Everything downstream — findings, forecasts, policies, approvals — runs off that one normalized dataset.
Every step in the checklist produces something you can verify before moving on — no long implementation project, and no waiting on a vendor services team.
Start in your FinOps Co-Pilot instance and create the workspace your team will use for cloud cost operations.
Add AWS, Azure, or GCP using the provider-native trust model. AWS uses IAM AssumeRole; Azure and GCP credentials are stored encrypted.
Validate connectivity, freshness, and trust so you know exactly which accounts are healthy before relying on cost data.
Explore the platform immediately with demo data, or begin ingesting real spend and usage data from your connected providers.
See PR Cost Diff in action by reviewing Terraform changes before merge, with cost delta, policy, and budget signals in one place.
Launch a live scan to surface idle infrastructure, unattached storage, rightsizing opportunities, and high-confidence savings.
Establish advisory and blocking guardrails for tags, risky resource types, budget limits, and environment-specific cost rules.
Route approvals into Slack or Teams so engineering and finance reviewers can act on savings requests without leaving their workflow.
The highest-leverage step for most teams: catching an expensive resource while it is still a diff, not a running instance.
Every provider uses its own native trust model. Nothing depends on long-lived credentials pasted into a form.
IAM AssumeRole with an external ID. No static access keys are ever stored, and the role can be scoped to read-only until you enable remediation.
A Service Principal scoped to the subscriptions you choose, with credentials encrypted at rest and never exposed in logs or UI responses.
A Service Account JWT scoped to billing and asset inventory, feeding spend, usage, and Recommender signals into one workspace.
A lightweight Helm-deployed agent that maps cluster spend to namespaces, deployments, and teams without leaving the cluster.
Once you are set up, the same platform covers plan, observe, control, optimize, and report — replacing three to four disconnected tools.
Set budgets, policies, and governance rules before anything ships.
Budget guardrails · tag requirements · cost policies
See all cloud spend in real time across every account and team.
Multi-cloud dashboard · anomaly detection · attribution
Enforce policies at PR time, deploy time, and runtime.
Advisory · blocking · tag enforcement · budget limits
Detect waste, right-size resources, and negotiate commitments.
18+ detectors · AI remediation · Savings Plans
AI-generated insights, forecasts, and executive summaries.
Prophet forecasting · team scorecards · variance analysis
Detection is automated. Action is not. Every remediation passes a policy check and a human approval before it touches a resource.
Most cloud cost management platforms treat onboarding as a services engagement: a scoping call, a credentials workshop, and a data warehouse build before anyone sees a number. FinOps Co-Pilot is designed for self-serve rollout, so a platform engineer can connect an AWS, Azure, GCP, OCI, or Kubernetes environment and reach live findings the same afternoon.
The recommended path is to connect one account in read-only mode, confirm the ingested spend reconciles against your provider invoice, and only then enable remediation. Because every write action is approval-gated and protected-tag aware, widening scope is a deliberate decision rather than an implicit side effect of connecting an account.
The highest-leverage step for most engineering organizations is pull request cost analysis. Running Terraform cost estimates before merge turns cloud cost from a monthly finance conversation into a routine code review signal, which is where expensive infrastructure decisions are cheapest to reverse.
Cost findings only become savings when someone acts on them. Routing approvals into Slack or Teams — with role verification and an immutable audit trail — is what closes the loop between detection and realized savings.
All 11 operational capabilities across visibility, intelligence, governance, and automation.
View featuresWhere the savings come from, what teams typically recover, and how it compares to alternatives.
View ROI breakdownCredential handling, audit trails, RBAC, protected resources, and SOC 2 readiness.
View securityFree trial, no credit card, and a guided checklist that gets you to live findings in about 15 minutes.
