# Snowflake cost attribution by ownership rule

> Give every Snowflake dollar an owner. Attribute cost to teams by warehouse or by query with ownership rules, then read each team's share and the spend no team owns.

Source: https://altimate.ai/product-highlights/snowflake-cost-alerts-by-team

[.md](https://altimate.ai/product-highlights/snowflake-cost-alerts-by-team.md) 

Copy as MD

Enterprise Platform

## Attribute Snowflake Cost to the Team That Owns It

Give every Snowflake dollar an owner. Attribute cost to teams by warehouse or by query with ownership rules, then read each team's share and the spend no team owns.

Pradnesh PatilJun 19, 2026Aug 20, 20264 min read

 Attribute Snowflake cost to the team that owns it 

TL;DR

-   **What it is.** Snowflake cost attribution that puts each team's name on its share of the bill. You match assets to a team with ownership rules, by warehouse or by query. It works on Snowflake and Databricks.
-   **Who it is for.** Data platform leads and engineering managers who answer for a team's cloud spend, not for one warehouse.
-   **What you get.** A per-team breakdown of the bill, the queries behind each team's number, and one figure for the spend no team owns yet.

## Attribute Snowflake Cost by Warehouse or by Query

Your bill is one number, but the work behind it belongs to different teams. Cost attribution puts each team's name on its share. Altimate does this two ways, and you pick the one that fits how your teams share compute.

-   **By warehouse.** Each team runs its own warehouses, and the cost of each follows whoever owns it. If your team uses five warehouses and mine uses ten, we each pay for ours, and no query tags are needed.
-   **By query.** Several teams share one warehouse. Most teams already tag their queries with an owner and an application, and attribution reads those tags, so one warehouse splits cleanly across the teams that use it.

| Method | Use it when | What it needs |
| --- | --- | --- |
| **By warehouse** | Each team has its own dedicated compute | Nothing extra, ownership follows the warehouse |
| **By query** | Several teams share one warehouse | The owner and application tags most teams already set |

Pick one and hold to it. Splitting by warehouse is simpler when compute is dedicated. Splitting by query is what you want when several teams share a warehouse and you need cost per project.

## Ownership Rules Decide Which Assets a Team Pays For

An ownership rule is a pattern that says which warehouses, queries or tables belong to a team. You write it once. Anything that matches it later, a warehouse someone spins up next month included, joins the team on its own. Nobody edits the rule again.

| A rule can match | Example |
| --- | --- |
| **A warehouse**, by name or tag | Every warehouse whose name starts `ANALYTICS_` |
| **A query**, by role, user or tag | Every query run under the dbt service role |
| **A table**, by schema or database | Every table in one team's schema |

You can stack several rules on one team. As you add each rule, Altimate shows the cost it would pull in, so you are never guessing what a rule catches. The rules group those assets and attribute their combined cost to the team.

 The ownership rule builder for a team, matching a warehouse by name, with a panel above it showing the cost this rule would attribute to the team before you save it. 

That combined cost is what the Team Spends page reports. Each team's total is the sum of what its ownership rules own, and nothing was tagged by hand to get there. Open a team and you see the individual queries attributed to it, each with its own cost. A spike then traces back to the query that caused it, not to a team in the abstract.

 A team's attributed queries, each row a single query with its cost, execution time and the warehouse it ran on, the drill-down behind that team's total on the Team Spends page. 

## See the Spend No Team Owns Yet

Two numbers tell you how complete your attribution is, and you read them together.

| Number | What it means | How you fix it |
| --- | --- | --- |
| **Unaccounted spend** | Bill that matched no ownership rule at all | Add rules until they cover every asset |
| **Uncategorized** | Bill that matched two teams at once | Resolve the rules that overlap |

Altimate never guesses a winner. When two teams claim the same asset it marks the asset Uncategorized, names both teams, and flags the team so you can settle it. You fix both numbers in the ownership rules, never in the bill. The target is a small Uncategorized figure, which means almost every dollar has a team that answers for it.

 The Team Spends dashboard, a stacked bar per day split by team, with total spend, active teams and unaccounted spend across the top and Uncategorized called out as its own band. 

 A team's Ownership section warning that its rules overlap other teams on a set of entities, with the affected teams flagged in the list until the overlap is resolved. 

Access rules are the other half of a team. They control what the team can see, not what it pays for, so attribution and visibility stay separate. The [Enterprise Platform overview](https://altimate.ai/platform) covers the rest.

### Talk to us about your warehouse

[Book a 30-min demo →](https://calendly.com/d/ctnv-rbc-yr3/altimate-ai-overview) 

## Frequently Asked Questions

What is cost attribution in Altimate?

Should I attribute by warehouse or by query?

What can an ownership rule match on?

Do I have to tag my queries for this to work?

What happens when two teams claim the same asset?

Why is my Uncategorized spend high?

How are access rules different from ownership rules?

Can I use this for chargeback?

On this page

-   Attribute Snowflake Cost by Warehouse or by Query 
-   Ownership Rules Decide Which Assets a Team Pays For 
-   See the Spend No Team Owns Yet 

## Related Resources

Enterprise Platform Databricks Cost Breakdown, from One Bill Down to One Warehouse

https://altimate.ai/product-highlights/databricks-cost-breakdown-workspace-sku-cluster

Enterprise Platform Root Cause Analysis for a dbt, Tableau, or Snowflake Workload Spike

https://altimate.ai/product-highlights/snowflake-workload-root-cause-analysis

Enterprise Platform Auto Tune Right-Sizes Snowflake Warehouses Without Slowing Queries

https://altimate.ai/product-highlights/snowflake-warehouse-auto-tune-right-sizing

Help Doc AI Cost Analysis (DataPilot)

https://help.altimate.ai/platform/summary/datapilot-analysis/
