1
Pick the tag
Choose the tag key that represents your cost owner — typically `team`. Resources without that tag fall into the 'unallocated' bucket.
one allocation dimension
Cost Allocation by Team
A flexible allocation engine that maps tags, accounts, projects, namespaces and shared services into team-level cost — including a transparent, auditable shared-cost split.
- Multi-dimensional rules
- Auditable shared split
- Showback dashboards
lumicost.com — cost-allocation
By the numbers
Cost Allocation by Teamin 4 numbers
triggers a governance warning
0%
unallocated threshold
top by cost, per team
0
resources per drill-down
a tenant-chosen tag (e.g. team)
0
allocation dimension
warning fires above the threshold
0
cost left in 'unallocated' silently
How it works
Three steps. No agents. No surprises.
2
Surface the breakdown
GET /cost-allocation/by-team returns each team's total, percentage and resource count, plus governance warnings when unallocated cost crosses 30%.
totals · % · count
3
Drill down
/by-team/{team}/resources returns the top 10 resources for the team with their individual cost — enough to start a focused conversation.
top 10 by cost
What's inside
A flexible allocation engine that maps tags, accounts, projects, namespaces and shared services into team-level cost — including a transparent, auditable shared-cost split.
01
Allocation rules, not magic
Define rules in plain language: 'this account → this team', 'this tag value → this BU', 'this K8s label maps to this cost centre'. Rules are versioned, signed and previewable before they go live.
02
Shared cost, transparent split
Shared services (logging, networking, security) are split by your chosen driver — headcount, spend share, traffic — and the split formula is visible to every consuming team.
03
Chargeback or showback — your call
Run as showback (visibility only) until the org is ready, then flip to chargeback with a monthly CSV that ERPs and accounting systems accept.
Capabilities
Everything you need on day one.
- Tag-based team breakdown
- Per-team total · % · count
- Unallocated bucket surfaced
- 30% governance threshold
- Drill-down: top 10 resources/team
- Updates every analysis run
- Pairs with Tag Intelligence
- API access via API key
Before vs after Lumicost
Night and day.
Without Lumicost
- 'Whose RDS is this?' takes 3 days of Slack
- Unallocated cost slips by quietly
- 'Who's the most expensive team?' — no answer
With Lumicost
- Owner shown via the team tag
- Governance warning above 30%
- Per-team breakdown ranked by cost
Where teams use it
Three ways teams put it to work.
Engineering OPEX accountability
Every engineering manager sees a real-time view of their team's burn — and the % they own of shared services.
Product P&L
Roll team cost up to product, then down to gross-margin per customer cohort.
M&A integration
Re-allocate the acquired co's footprint into your existing team taxonomy on day 30.
From the field
“Cost allocation is only honest if the leftovers are visible. The 'unallocated' bucket is a feature, not a bug.”
Plays nice with your stack
AWSGCPAzureOracle CloudKubernetesTerraformPulumiSlackJiraLinearGitHubGitLabDatadogSplunkOpenTelemetryPagerDutyNetSuiteSAPAWSGCPAzureOracle CloudKubernetesTerraformPulumiSlackJiraLinearGitHubGitLabDatadogSplunkOpenTelemetryPagerDutyNetSuiteSAP
FAQ
Frequently asked questions
What about untagged resources?
They land in a quarantine bucket with ML-suggested owners; you can also fall back to a configurable shared-cost split until tagged.
Can the rules change retroactively?
Yes, with full audit trail. The original allocation snapshot is preserved alongside the new one.
Keep exploring
Try it free.
Connect read-only credentials. First insights in 24 hours. No credit card.
90 seconds · read-only credentials · no credit card