Do we need a tagging policy first?

No. Agents show how spend is tagged today and suggest a policy from it. You approve the rules before anything changes.

Will agents buy Savings Plans for us?

No. Agents prepare renewal and purchase options from real usage. Commitments are bought by the people you name.

How is shared spend split?

By rules you approve, such as namespace, account or usage share. Every split shows the data behind it.

Does this replace Cost Explorer or Kubecost?

No. Agents read from them alongside CloudTrail and Terraform, then add the owner, the cause and the fix.

AWS Partner

SOC 2 Reports

Frontier Governancefor FinOps

Tagging, cost allocation and commitments kept current without a spreadsheet.

Cost allocation breaks the day a resource ships without a tag. Agents check tagging, budgets and savings commitments across every account each day, trace untagged spend to the team that launched it, and fix the tags in code. Your monthly showback is ready without a spreadsheet.

Book a Demo See how it works

Daily allocation checkowner found

Untagged spend in account ml-sandbox

Spend: $11,840 this month with no cost-center tag
Resources: 9 g5.2xlarge instances and 3 EBS volumes
Owner: Launched by the ML platform team, per CloudTrail
Cause: Terraform module ml-workers has no default_tags block
Fix: Pull request adds default_tags. Tags applied to running resources

Waiting for the ML platform lead to merge

[The work behind every cost report]

Your bill arrives every month.Who spent it takes another two weeks.

01The manual work

Allocate

Every month the FinOps lead exports the bill, guesses owners for untagged spend and chases teams for answers.

02The agent handoff

Showback ready

Frontier agents trace every untagged line to an owner, fix the tags in code and keep budgets and commitments current.

03Your team’s role

Decide

Own the tagging policy and the budgets. Approve commitment purchases and decide where spend should go.

[Where CloudThinker fits]

Your stack stays.Agents work inside it.

01Billing sources

Already in your clouds

AWS Cost and Usage ReportLine items, tags and commitments
Azure Cost ManagementCost exports and budgets
Google Cloud Billing exportBilling data in BigQuery
KubecostCluster spend by namespace
SnowflakeWarehouse and query spend

No change to your billing

02Ownership

Your system of record

TerraformTags defined in code
AWS OrganizationsAccounts and tag policies
Vantage and CloudHealthReports finance already reads
GitHub and GitLabWho owns each module

Source of truth stays put

03Governance

CloudThinker

AllocateSpend mapped to product and team
Fix tagsUntagged resources traced to an owner
WatchBudgets and forecasts per owner
PlanCommitment options with the math shown

Read-only by default

04Response

Spend with an owner

Pull requestsTag fixes in Terraform
SlackBudget alerts to the owning team
JiraSavings work tracked to done
Finance reportSpend by product line, every week

Purchases stay with people

Logos show common stacks. CloudThinker reads billing and ownership data through read-only access you approve.

[Example scenario]

Month end, 09:00. The board deck is due Friday.18% of spend has no owner.

A 200-engineer SaaS company with 34 AWS accounts, a $1.2M monthly bill, Terraform and Kubecost. Finance wants spend by product line this week.

09:00
Monthly close startsSignal
The Cost and Usage Report lands. 18% of spend has no cost-center tag.
09:04
Agent traces every lineAgent
Matches untagged resources to CloudTrail creators, Terraform modules and Kubernetes namespaces.
09:12
Finds the root causesAgent
Most of the gap comes from 4 Terraform modules with no default tags and 2 shared EKS clusters split by namespace only.
09:20
Fixes and a commitment checkAgent
Opens 4 pull requests for tags, maps namespaces to cost centers, and flags a Savings Plan that expires in 21 days.
11:45
FinOps lead approvesYour team
Approves the namespace mapping and asks for a renewal option with a smaller hourly commitment.
11:58
Showback publishedAgent
Untagged spend down to 2%. Spend by product line posted, renewal options attached for finance.

#finops4 messages

AWS Cost and Usage Report09:00
September CUR available. $214,600 (18%) has no cost-center tag.
CloudThinker09:20
Traced 96% of untagged spend to owners. Causes: 4 Terraform modules with no default_tags, 2 shared EKS clusters. Opened 4 pull requests. Also: Compute Savings Plan sp-0a91 expires in 21 days.
FinOps lead11:45
Mapping approved. Show me a renewal at a lower hourly commitment.
CloudThinker11:58
Untagged spend now 2%. Showback by product line posted to the finance folder. Two renewal options attached, based on 90 days of usage.

untagged spend in one morning: 18% → 2%
Terraform modules fixed at the source: 4
notice before a commitment expired: 21 days

An illustrative example. Team, systems and times are representative, not a specific customer.

[Frontier governance agents]

Every dollar has an owner.Every commitment has a plan.

Agents keep the boring half of FinOps current every day, so tags, budgets and commitments stay right and your team spends its time on the decisions only people can make.

Fix tagging at the source: Untagged resources traced to the module or pipeline that made them, fixed in code and backfilled on what is running.
Allocate shared spend: Shared clusters, data transfer and support split by namespace, account or usage, using rules you approve.
Keep budgets honest: Budgets per team and product checked daily, with the change behind any overrun attached.
Plan commitments: Savings Plans and Reserved Instances tracked to expiry, with renewal options based on real usage.

[What changes]

Same team. Same tools.Far less of the work by hand.

Moment	Today	With frontier agents
Untagged spend	Guessed at month end	Traced to an owner the day it appears
Showback	Two weeks of spreadsheets	Published on day one of the close
Tagging policy	A wiki page teams forget	Enforced in Terraform with pull requests
Commitments	Noticed after they expire	Renewal options weeks ahead, from real usage
FinOps team time	Chasing owners	Working with teams on what to spend

[Integrations]

Connects to the rest of your stack.Read-only to start.

AWS Cost and Usage Report
AWS Cost Explorer
AWS Budgets
AWS Organizations
AWS CloudTrail
Kubecost
Vantage
CloudHealth
Snowflake
Terraform
GitHub
GitLab
Slack

[Adoption path]

One pilot.Then company-wide.

The rollout follows the four phases of the AWS Cloud Adoption Framework, so it fits the plan your cloud team already runs.

01Envision
Start with last month
Connect the Cost and Usage Report read-only. Agents trace last month’s untagged spend and show what they find.
02Align
Agree the allocation rules
Set the tagging policy, the cost centers and how shared spend is split. Write down who approves commitments.
03Launch
Roll out to every account
Add every account and module on the same rules, with tag fixes arriving as pull requests.
04Scale
Make the close automatic
Showback, budgets and renewal options are ready on day one of every month.

[Customer proof]

F88.Results on the record.

A Vietnamese consumer-finance company with 800+ branches made cost optimization continuous as it grew a read-only pilot into a governed hybrid-cloud operating model.

Read the case study

lower AWS spend: 30%
of daily operations automated: 80%

[AWS guidance]

Built the way AWS says to run it.Reviews start from a known reference.

[Trust and control]

Agents do the work.Your team keeps control.

You approve every change: Agents propose. Nothing touches production until someone on your team says yes, and you set that rule per system.
Every action on the record: Each step is logged, attributed and reversible, ready for your auditors.
Certified for enterprise: SOC 2 Type II and ISO 42001, with reports in our trust center.
Runs where you need it: In our cloud, through AWS Marketplace, or inside your own account.

[Questions]

What teams askbefore they start.

Do we need a tagging policy first?: No. Agents show how spend is tagged today and suggest a policy from it. You approve the rules before anything changes.
Will agents buy Savings Plans for us?: No. Agents prepare renewal and purchase options from real usage. Commitments are bought by the people you name.
How is shared spend split?: By rules you approve, such as namespace, account or usage share. Every split shows the data behind it.
Does this replace Cost Explorer or Kubecost?: No. Agents read from them alongside CloudTrail and Terraform, then add the owner, the cause and the fix.

[Go deeper]