For FinOps Teams¶
Accountability for the cloud number, with the authority to move it.
Who This Is For¶
The person accountable for cloud spend. The hard part of the job is not seeing the overspend. It is that seeing it is all you can do: you raise it, chase it, and the fix depends on someone else finding the time. Reading the bill also puts you a month behind the decision that caused it.
RosettaHub checks the same budget at the moment a resource is created and while it runs, and blocks the account when the budget is reached.
The Budget Loop¶
| Stage | What happens | Edition |
|---|---|---|
| At launch | The account's quotas are checked: instance types, machine counts, volumes, regions and services. A launch outside them is refused at the cloud's own API | Govern |
| While it runs | Every running resource carries a live cost estimate from the cloud's pricing data, reconciled with billing reports and evaluated against the budget continuously | Observe |
| At the budget | New activity on the account is blocked, AI included. On Automate, running services are stopped too: instances stopped with volumes kept, storage untouched, data preserved wherever the service allows | Govern, Automate |
| When idle | Idle instances autostop and orphaned resources are cleaned up | Automate |
Alerts still exist. They stop being the only thing between you and an overrun.
Production accounts
Enforcement is per account. An account without the blocking and stopping scopes is monitored and alerted on, but never stopped. See Cost Management.
Budgets Are Delegated¶
Budgets flow down the organization hierarchy. Owners delegate part of their budget to sub-organizations and projects, with transfer rights for further delegation. Giving a team more room is a transfer, and an account disabled at its limit is re-enabled by transferring more budget.
The Account Decides Who Pays¶
Tag-based allocation depends on every engineer remembering to label a resource. The account boundary holds whether or not anyone cooperated.
| Capability | What it does |
|---|---|
| By person and by project | Cost rolls up both ways from the same data |
| Shared accounts split by weight | A login in two organizations is split between their cost centres in proportion |
| Reconciled, remainder named | Every run ties back to the invoice. Cost that reaches no cost centre is charged to an unallocated code, not dropped |
| Chargeback and showback | Different queries over the same data |
See Cost Allocation and Chargeback.
FOCUS Data in Your Own Account¶
Billing data is written to FOCUS 1.3, the FinOps Foundation open billing standard, in your own FinOps account. AWS and Azure spend arrive in the same columns, so a query written once works on both. You query it with SQL through your cloud's own engine, Athena on AWS. There is no copy in a vendor data lake.
AI and Model Spend¶
Bedrock usage is metered from invocation events and added to the account's live cost, within five minutes of the call. It draws down the same budget as compute and storage. When the budget is reached, AI access is cut within 15 minutes, together with everything else on the account. Which models a role may call is a permission. See AI Usage Tracking for what is and is not enforced today.
What Is Available¶
Live cost, budgets, quotas, allocation, FOCUS tables, Superset dashboards and savings recommendations (right-sizing, reservation opportunities, idle resources) are available today, across AWS, Azure, Google Cloud and Alibaba Cloud. Forecasting and anomaly detection are on the roadmap.
Start Read-Only¶
| Edition | What you get | |
|---|---|---|
| Observe | See it | Live cost estimates, allocation, savings recommendations and compliance scanning. No administrative access |
| Govern | Stop it | Budgets and quotas enforced at creation, and limits on regions, services and models. Still no administrative access |
| Automate | Fix it | Autostop, cleanup, remediation and account recycling. Administrative access, granted per account |
| Build | Build it | Automate plus RosettaCloud self-service |
Access is granted per account and withdrawn by removing the stack.
Getting Started¶
- Read RosettaOps Editions.
- Follow Onboarding to connect your management account.
- Set up cost centres as described in Cost Allocation and Chargeback.
For pricing, see rosettahub.com/site/pricing.
Related¶
- Cost Management
- Managing Cloud Accounts: budget actions
- Resource Management: idle safeguards
- For Scaleups
- For Managed Service Providers