Product
Virtual Tags: Cost Allocation Across Every Provider
One tag shows spend by team, product, or any other dimension across Cloud, SaaS, and AI. You pick the rules off your own bills, and past months come along.
- Published
- Read time
- 3 min
On this page
A virtual tag is a label LevelFour puts on your cost from rules you set, so you can see spend by team, product, or any other dimension across Cloud, SaaS, and AI. It reads your bills, so it reaches the spend provider tags miss.
Provider tags work one provider at a time. Each provider names things its own way, some bills carry no tags, and a tag you add today says nothing about last month. Showback and chargeback need one allocation across all of them, and a virtual tag gives you that. If AI is the bill you worry about first, read how to track AI costs by team.
What you can do with virtual tags
- See spend by team, product, customer, cost center, or any other dimension, across every provider you connect.
- Give an owner to spend with no tags, such as shared accounts, support fees and AI seats billed per person.
- Fix tags that disagree, so Data, data and data-prod read as one team.
- Split a shared cost between the teams that use it.
- Allocate past months too, up to 12 months back.
How a virtual tag works
A virtual tag has a name, such as Team, and values, such as Engineering or Data. Each value comes with rules that say which cost it claims: this AWS account, these people on an AI tool, this Kubernetes namespace. You pick what a rule matches from lists drawn from your own bills, so a rule names something that exists.
Rules run in order, and a cost takes the first value that claims it. Cost no rule claims stays in view as Unallocated, so you can see what is left.
| Spend | What a rule can match |
|---|---|
| Cloud bills | Accounts, services, regions, resources and the tags you already have |
| AI tools | Accounts, models and plans, and people where the tool bills them one by one |
| Data and observability platforms | Accounts, resources, and the plan or meter on each line |
| Kubernetes | Clusters, namespaces, workloads and pod labels |
The virtual tags guide lists what each provider reports.
Custom, predefined and related tags
- Custom tags are the ones your team defines, for the way your company splits cost.
- Predefined tags come ready: LevelFour keeps 19 in your organization, such as AI Spend, Marketplace Spend and the FOCUS fields. Duplicate one to make it yours.
- Related tags split one cost by several dimensions of a dataset, and you read them together.
Shared cost
Some costs belong to several teams, such as a support plan or an AI subscription. You can split them by percent, evenly, the way another tag already divides cost, or by the usage you send. On Kubernetes, LevelFour divides each node's bill across the workloads that ran on it, so a node counts once.
In the platform and over MCP
In the platform, you build a tag on the Tags page, preview what it would claim, and read the result in Breakdown and on Boards.
With an AI agent, creating or editing a tag takes one sentence. Over the LevelFour MCP server, an agent such as Claude or Cursor can generate a tag by category, change a rule, rename a value and try the result before saving, with the values on your own bills. The docs list each tool.
The API, the CLI and the SDKs work with the same tags.
Get started
The Virtual tags page shows the feature in the product, and the guide has the rule patterns.
Start with LevelFour and connect your first provider.
Frequently asked questions
What is a virtual tag?
A virtual tag is a label LevelFour puts on your cost from rules you set, beside the tags your providers report. You use it to group spend by team, product, or any other dimension. Virtual tags in the glossary.
How are virtual tags different from provider tags?
Provider tags sit on each resource, and each provider has its own. Virtual tags are rules that read the bill, so they reach untagged resources, shared costs and providers with no tags, and your resources keep the tags they have.
Which providers can a virtual tag read?
Any provider you connect: cloud bills, AI tools such as Claude Code or Cursor, observability and data platforms, and Kubernetes clusters running the LevelFour agent.
Can a virtual tag apply to past cost?
Yes. A new tag reaches back up to 12 months. LevelFour reprocesses those months in the background, and the tag's page shows the progress.
Can an AI agent create and edit virtual tags?
Yes. Over the LevelFour MCP server, an agent such as Claude or Cursor can create a tag, change its rules and rename its values, and preview the result before saving.
Try LevelFour free for 14 days
See what it saves on your cloud, SaaS, and AI bills. No credit card required.
Start free trial