Allocations
Allocate every dollar. Tags optional.
Cloud Intelligence™ reads runtime traffic to put shared and untagged spend on the team, customer or feature that used it. Virtual tags turn the tags you already have into one clean set. Rules cover the rest, so nothing lands in Unallocated.
No retagging · No code changes · AWS, Google Cloud, Azure and more
three layers, one allocation
Tags are one input. Not the only one.
Use the tags you have, clean them up with virtual tags, and let Cloud Intelligence™ assign what tags can't reach: shared clusters, network and AI. Then allocation rules make sure every dollar has a home.
See your spend allocatedother tools need a tagging program
We don't.
Tagging programs take quarters, depend on every engineer, and still can't see inside a shared cluster. Allocations combine the tags you have, virtual tags and runtime attribution, so every dollar has an owner without a single ticket to engineering.
Finance
Chargeback without the caveats.
FinOps
100% allocated, not 43%.
Engineering
No tagging tickets.
Leadership
Cost by team you can trust.
built for real bills
Everything allocation needs
Virtual tags
Merge messy keys like owner, Owner and team-owner into one tag.
Runtime attribution
Shared and untagged spend assigned by actual usage.
Group allocations
Ordered rules split spend by team, product or environment.
Shared cost splitting
Spread support fees and shared charges across teams fairly.
Unallocated, tracked
See what's left unowned and why, before it reaches a report.
Used everywhere
Reports, budgets, alerts, anomalies and metrics share one logic.
no tagging project
How allocation works without tags
Install in 15 minutes.
A lightweight sensor via Helm, plus your billing data. No code or tag changes.
Clean up the tags you have.
Virtual tags merge every variant of a key into one, across all your clouds.
Allocate everything.
Rules and runtime attribution give every dollar an owner. Unallocated: $0.
SOC 2 Type 2, ISO 27001, FinOps Certified Platform.
Book a demoStart for free
Frequently asked
questions
Can I allocate cloud costs without tags?
Yes. Cloud Intelligence™ reads runtime traffic to assign spend to the team, customer, feature or AI agent that used it, including shared clusters and network that tags can't reach. Virtual tags and allocation rules cover the rest.
What are virtual tags?
Virtual tags merge the many variants of a tag key across your clouds, like owner, Owner, team-owner and owned_by, into one clean tag with normalized values. You get consistent allocation without retagging a single resource.
How do allocation rules work?
A group allocation is an ordered list of rules built from dimensions, labels, tags and virtual tags. Spend goes to the first rule it matches, and anything left lands in Unallocated, which you can track and close.
Can I split shared costs like support or egress?
Yes. Shared charges can be split across teams or projects with rules you define, and Cloud Intelligence™ splits shared infrastructure by measured usage.
What is cost allocation in the FinOps Framework?
The FinOps Foundation defines allocation as mapping cloud costs to the teams, products and business units that consume them, using metadata beyond tags to reach full coverage. It's the foundation for showback, chargeback, budgets and accountability.
Where can I use allocations?
In Cloud Analytics reports, budgets, alerts, cost anomaly detection, custom metrics and digests, so every view uses the same logic.
Tags are optional. Accountability isn't.
Every dollar with an owner, without a tagging project.