Cloud Scal3
FinOps Center gives your Product Owners, FinOps Leaders, and CFO office complete ownership of every AWS dollar and every AI workload, through structured business process, not engineering dependency. It is the only CFM platform that includes a purpose-built AI FinOps Agent. Deployed on AWS inside your Customer Cloud Estate.
Most teams discover AI spend after the bill arrives. FinOps Center governs it before the first token. Customers come to FinOps Center for AI Cost Governance, and get their complete CFM process in the same platform.
Product Owner submits a Business Request with declared value and budget. FinOps Lead approves the model, platform, accounts, and regions. No token runs without a named business case and an approved owner.
Learn more →Cloud Engineer receives pre-written CLI commands and a CloudFormation template. IAM role deployed. ModelApprovalScope created. Developer Handoff issued to the Product Owner to claim.
Learn more →Product Owner claims the AI workload. Token estimates set against a confirmed budget. Weekly AI Spend Cards generated: actuals vs estimate by model, token type, and region.
Learn more →Nightly pipeline surfaces unattributed spend, out-of-scope models, and unclaimed roles. FinOps Lead actions each gap inline with a timestamp, rationale, and audit trail for Finance.
Learn more →AI Governance Maturity scored across four dimensions on a Crawl/Walk/Run scale. Investment Prospect ratings surface Underwater and Unbacked workloads for FinOps Lead action.
Learn more →Executives see the full AI portfolio: every workload sized by planned cost, colored by how its declared value compares. Strong Prospect to Unbacked. One screen. The complete picture of what AI is funded to produce.
Learn more →AI workloads live inside your broader AWS environment. So FinOps Center brings your complete CFM governance with it: financial hierarchy, account allocation, workload resource claiming, budget tracking, Spend Card approvals, AWS Programs, Cost Optimization, and Month Close. One platform. One place to own all of it.
AWS organises your infrastructure. FinOps Center organises your spending. Map your AWS accounts, AI workloads, and resources to the financial hierarchy your business already operates: Business Unit, Department, Portfolio, and Product. Every AI model, every Bedrock invocation, every CFM cost uses your business language, not AWS account IDs or service codes.
Every AI model must be approved and claimed before the first token. Product Owners claim Bedrock models, AgentCore runtimes, and AWS resources directly to their workloads. Once claimed, 100% of that spend is owned by that team from the claim date forward. When Finance asks who is responsible for last month's AI bill, there is always a name and a business case attached.
In the era of AI, the CFO office cannot wait for quarterly reviews to understand what the organization is spending on models. FinOps Center surfaces the right information to the right person at the right level, in real time. A Product Owner sees their workload. A FinOps Leader sees every AI model, every gap, every pending approval. Every decision is a business process step with an owner, a timestamp, and an audit trail.
From login to action in a Linked Account: the complete flow across all three products, inside your Customer Cloud Estate.
Product Owner · FinOps Leader · Cloud Engineer · more
JWT token issued — carries role + hierarchy scope
Business process UI — spend cards, scoreboard, resource claiming, MAP tasks, budget reviews. No AWS console needed.
Embedded QuickChat opens. Lives inside a Quick Space — role-scoped resource container. User token passes to MCP.
One per role — Cost Management, AI Cost, Container, SP, Marketplace
User-Based RLS enforced — user sees only their allocation scope
CUR2 data JOINED with FinOps Center user allocation table
When CUR lands in S3, Lambda triggers the Athena query refresh → SPICE refreshes → Topics update. New users provisioned in FinOps Center will have the Agent Bill experience after the next CUR-triggered refresh.
Security token from QuickChat passed to MCP
OAuth 2.0 user-scoped auth · validates token · routes to tools
AppSync GraphQL → DynamoDB → Lambda — 16 governed actions
Any action requiring access to Linked Accounts
Setup follows CID Guide steps 1 + 2 — no CID required
FinOps Center + Agent Bill installed here via AWS Marketplace CloudFormation
CloudScal3 Tools policies deployed via Control Tower → cross-account IAM roles created
All data processing and business logic runs inside your Delegated Admin Account · nothing leaves your AWS environment
Your Product Owners, FinOps Leaders, and Department Managers work in purpose-built interfaces: not AWS Cost Explorer, not raw CUR data, not engineering tooling.
Weekly spend periods routed to the Product Owner for review. Accept if the numbers match expectations — dispute if something looks wrong. No AWS console access required.
Letter-grade CFM Scoreboard with three weighted dimensions. Unrealised savings surfaced as accumulated loss with a one-click bulk-approve action. Recommendation pipeline from Pending → Approved → Implemented.
Why is our AI spend so high this week?
Your AI spend is up 4× this week. The Bedrock model for HR Portal switched from Claude Haiku to Claude Sonnet — cost per request increased from $0.012 to $0.048.
Embedded in FinOps Center via Amazon QuickSuite. Role-scoped answers grounded in your CUR data. Ask about spend, budgets, MAP credits, or Savings Plans — in plain English.
FinOps Center grades your AWS environment across waste elimination, commitment strategy, and resource modernization, adjusted for the effort each recommendation requires. An improving grade is visible proof of progress. A declining grade is an early warning before the next bill lands.
See how the Report Card worksA governed path from business request to running AI workload, before the first token. Product Owners describe the workload and set a budget. The FinOps Lead selects the platform, assigns the model, and approves. Cloud Engineers receive pre-written CLI commands and execute. Agent Bill demystifies the spend in plain language for every stakeholder. Covers Amazon Bedrock, AWS Marketplace Models, and Claude Platform.
See AI Cost GovernanceEvery model must be approved for a specific region, a specific set of actions, and a specific workload before the first API call. The Business Request workflow enforces this: governance precedes consumption by design. The FinOps Lead owns the model catalog. No workload uses a model that has not been approved and scoped.
See Workload OnboardingToken consumption can spike overnight. FinOps Center generates a Spend Card for every claimed AI workload every week: actuals vs the FinOps Lead's confirmed estimate, broken down by model, token type, and region. Product Owners accept or dispute. Portfolio Owners approve the rollup. Finance gets a chargeback-ready record every week, not every quarter.
See AI ScorecardMeasures AI governance across four dimensions: Workload Attribution, Model Governance, Estimate Coverage, and Process Efficiency, each rated on a Not Started / Crawl / Walk / Run scale aligned to the FinOps Foundation framework. Every dimension shows current tier, the next advancement move, and what closing the gap is worth in attributed dollars.
See AI Governance MaturitySix gap scenarios detected and surfaced inline: from AI spend with no IAM principal in CUR, to dedicated roles with no Product Owner claim, to models invoked outside their approved scope. Every gap has an inline FinOps Lead action. Every action carries a timestamp, rationale, and the identity of the person who made it. Finance gets an audit trail, not a snapshot.
See Allocation GapsNo other CFM platform includes what FinOps Center ships with by default: a purpose-built AI FinOps Agent connected to your governance processes. Ask why an AI workload spiked, action an Allocation Gap, approve a Business Request, all in plain English, without leaving FinOps Center. Agent Bill is not an add-on. It is part of the product.
Meet Agent BillYour AWS spend mapped to your business structure. Business Unit, Department, Portfolio, and Product. Every allocation, budget, and report uses labels your business teams already understand, not AWS technical identifiers.
See Onboarding & AllocationAssign AWS accounts to financial budgets by percentage. Shared accounts split fairly between teams. Dedicated accounts attributed 100%. Every account accounted for from day one.
See Onboarding & AllocationProduct Owners claim any AWS resource with an ARN to their workload in FinOps Center. EC2 servers, RDS databases, S3 buckets, and Bedrock AI models. Once claimed, cost follows ownership automatically, every day.
See Onboarding & AllocationSchedule the approved annual budget across the year by workload-component estimate. Annual and period budgets tracked against actuals in real time: Current Period spend, Current Month spend, available budget, and trend, surfaced at the right level for each role in your business.
See Planning & SchedulingTwo Portfolio Owner approval gates: estimate size before spend is committed, and recurring spend before each period is accepted. No AWS cost is owned without a named business approver. Cloud Spend Cards route weekly actuals to Product Owners for review. The full approval audit trail replaces ad hoc engineering requests with structured governance.
See Spend GovernanceMAP, Credits, and Savings Plans owned by the business, with execution routed to engineering or automated via Cloud Scal3 Tools. MAP-eligible workloads designated by Product Owners. Tagging tasks routed to Cloud Engineers. Credit utilisation and Savings Plan coverage tracked for FinOps Leaders. The full program lifecycle owned by the business, not buried in engineering.
See AWS ProgramsA letter-grade CFM Scoreboard across waste elimination, commitment strategy, and resource modernization, adjusted for the effort each recommendation requires. Unrealised savings surfaced as accumulated loss with a one-click bulk-approve action. An improving grade is visible proof of progress. A declining grade is an early warning before the next bill lands.
See Cost OptimizationApprove spend before the bill is owned, then export business-approved accrual data in the format your system of record requires: CSV for FP&A, structured export for AP and ERP. The FinOps Lead closes the month with a complete allocation record. Finance receives a file that reflects every business decision made during the period, not just the AWS invoice.
See Month Close & AccrualAsk why a workload exceeded budget, which department is driving spend, how MAP credits are tracking, or whether a Savings Plan approval is pending. Agent Bill knows your FinOps Center hierarchy, your budgets, your workloads, and your history, and responds with context scoped to your role. Embedded in FinOps Center and available on Amazon Quick Desktop. No other CFM platform includes this.
Meet Agent BillIncluded with FinOps Center · Agent BillEvery other CFM tool has a chat box bolted on. FinOps Center ships with Agent Bill: an AI agent that knows your governance hierarchy, your workload estimates, your model approvals, and your pending business decisions. It does not just answer questions. It takes governed action.
BR-0042 approved.
2 ModelApprovalScope records created
2 Cloud Engineer tasks generated, SLA 5 days
Each task includes CLI commands and CloudFormation template
One conversation. Four governance steps. Zero AWS console.
Every person sees the information relevant to them. Every workflow matches what that role actually does.
Owns the complete financial picture. Sets governance policy, approves savings recommendations, manages MAP contracts, allocates credits, and tracks org-wide spending against targets.
Owns their workload's AWS resources and spending. Claims resources, creates estimates, reviews and accepts Cloud Spend Cards, and designates workloads as MAP or AI workloads.
Owns the two approval gates: estimate size before spend is committed, and recurring spend before each period is accepted. Every budget decision in the hierarchy flows through this role before it is committed.
Works through structured task queues: MAP tagging, Bedrock inference profile setup, and tag drift remediation. Routed by the platform, not by ad hoc engineering requests.
Sees their department's total spending across all portfolios and products. Tracks budget vs actual. Understands trends without needing AWS access.
FinOps Center is a Deployed on AWS solution. It installs directly into your AWS environment via AWS Marketplace and runs entirely within your Customer Cloud Estate. There is no shared multi-tenant infrastructure. No data is transmitted to third-party systems. No external SaaS dependency sits between your business teams and your AWS spending.
Installed via AWS Marketplace and CloudFormation directly into your environment. No shared multi-tenant infrastructure. No data hops to a vendor cloud. Your allocations, approvals, budgets, and workload configurations are stored in your own DynamoDB tables.
Identity governed by your existing Amazon Cognito user pools. Authorization through your own AWS AppSync layer. Agent Bill's conversational AI runs through your own AgentCore runtime, using the same security controls you already trust. No new auth model to audit.
Every allocation, approval, budget, and report lives in your account. This is cloud financial management that respects the same data governance standards your business applies to everything else in your AWS environment.
FinOps Center is the See layer of the suite. Pair it with Agent Bill (Ask) and Cloud Scal3 Tools (Act) for the complete loop: govern, ask, and act, all AWS-native, all in your account.
The control plane. Spend governance, Cost Saving Report Card, AI MAP lifecycle, and role-scoped financial data across every team.
Learn more →Ask
The conversational layer. Bedrock AgentCore + Amazon Quick, with role-scoped answers grounded in your AWS data.
Learn more →Act
The execution layer. Non-technical teams buy Savings Plans, apply MAP tags, and stop non-prod resources within Control Tower guardrails.
Learn more →Available on AWS Marketplace. Annual plans save up to 20% vs monthly.
All plans available on AWS Marketplace. Annual pricing billed upfront.
FinOps Center deploys in minutes from the AWS Marketplace. Your first 10 accounts are free.