Who pays for the cloud? Split the bill by team.

Enter your monthly spend by service, give each team a share, and see exactly what every team owes — monthly and yearly — with what-if growth sliders and a downloadable summary. Your numbers never leave this device.

  • Your spend figures never leave the device
  • Per-team monthly + annual totals
  • What-if growth sliders
  • Downloadable summary

Split your cloud bill

Try a preset:

1 · Monthly spend by service

Take the figures from your provider's billing console. Amounts are in US dollars per month.

2 · Shared platform cost

The slice of the bill nobody owns directly — shared clusters, platform tooling, unattributed egress. It is split across teams in proportion to their shares.

%

3 · Teams and their shares

Rename teams, drag the sliders or type a percentage. Up to 8 teams.

4 · What-if growth

Model a change per service — a new workload, a cleanup, a price move. Your entered spend never changes.

Total / month$0.00
Total / year$0.00
Projected / month$0.00
Projected / year$0.00
Change+0% vs today

Allocation by team

TeamShareDirect / moShared / moTotal / moTotal / yrProjected / mo

Spend by service

ServiceToday / moShare of billGrowthProjected / mo
Enter your monthly spend per service to see the split. Planning model only — it splits the numbers you enter. It never pulls live provider pricing.

Privacy you can verify, not just trust

Cloud bills are sensitive — they reveal headcount, architecture and negotiating position. This simulator can't leak them: your spend figures and team names are processed entirely in your browser. Your data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no account, no cloud connection, and no server to send a bill to. Don't take our word for it:

New cross-origin requests during use: 0
  1. Press F12 to open developer tools, then the Network tab.
  2. Change a spend figure or a team share above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no spend figure ever leaves your device.
  3. Extra credit: disconnect your internet after this page loads — the simulator still works.

How to split a cloud bill across teams

One cloud account, one bill, five teams — and a finance meeting asking who spent what. The provider's console stops at the service: it can tell you compute cost $4,200, but not that the Platform team ran 35% of it. This tool closes that last step, in your browser, with numbers you control.

  1. Enter the bill by service. Copy the monthly totals from your provider's billing console — compute, storage, database, network/egress and anything else — into step 1. The tool never fetches pricing itself, so the split is only as good as the figures you enter.
  2. Set the shared platform slice. Some spend belongs to nobody: shared clusters, platform tooling, egress nobody can attribute. Put it in step 2 as a percentage, and the tool hands it out in proportion to each team's direct share, so every dollar is attributed exactly once.
  3. Give each team a share. Rename the teams, set percentages by slider or by typing. Shares that do not add to 100% are scaled proportionally and flagged; one click normalises them to a clean 100%.
  4. Model what-if growth. Slide compute up 20% for a new workload, or storage down 10% after a cleanup, and watch the projected monthly and annual totals — per team and per service — update instantly.
  5. Download the summary. A plain-text file with the service breakdown, the per-team totals, the shared-cost split and the projection — ready to paste into a budget review, an email or a ticket.

What makes this simulator different

The pages that top the results for this search are provider pricing calculators — they estimate what a workload would cost from instance counts and storage sizes — or enterprise FinOps platforms that need an account, a billing connection and a sales call. The guides that explain allocation are just that: guides, with the maths left to you. This page is the only free, fully client-side tool we found that starts from the bill you already have and answers the question finance actually asks — who pays what — with a shared-cost rule, per-team monthly and annual totals, what-if growth sliders and a downloadable summary, and a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload a bill to.

When is simulating the right choice — and when is it the wrong one?

Simulating is right when you need a defensible split for a budget review, a showback report, or a chargeback conversation — and when the real bill already exists in your provider's console. It is the wrong choice for estimating what a new workload will cost before it exists (use a provider pricing calculator for that), and for settling an argument about who caused a spike (that needs tagged resources and usage metrics, which this tool deliberately never asks for). If your shares are guesses, say so in the meeting — a split built on guesses is a planning aid, not evidence.

Honest limitations

Planning model, not a bill

Every figure here comes from numbers you type in. The tool never pulls live provider pricing and never reads an invoice — verify against your billing console before committing numbers.

Shares are your judgement

The split is only as defensible as the percentages behind it. If two teams genuinely share a service, the percentage you assign is a judgement call — document the reasoning alongside the summary.

Growth is linear

The what-if sliders scale each service by a flat percentage. Real growth is rarely linear — reserved-instance discounts, volume tiers and committed-use pricing all bend the curve.

Currency is US dollars

All amounts are entered and shown in USD. If your bill is in another currency, convert it first — the tool does not fetch exchange rates.

No usage metrics

The tool splits by the percentages you set, not by measured usage. For a usage-driven split, export CPU-hours, storage GB or request counts from your monitoring and turn them into percentages first.

It never changes your bill

This tool only models and reports. It cannot change tags, budgets or billing in any cloud account — to act on the split, apply it in your provider's console or your finance system.

Frequently asked questions

Does this tool pull live prices from AWS, Azure or Google Cloud?

No. This is an allocation and planning model, not a billing tool. It never connects to a cloud account and never fetches live provider pricing — every dollar figure is one you type in, and the results are only as good as those inputs. Take the totals from your provider's billing console (for example AWS Cost Explorer, Azure Cost Management or GCP Billing) and paste them in here to split them across teams. Verify the split against the same console before committing numbers.

Do my spend figures leave my device?

No. Your spend figures and team names are processed entirely in your browser — your data never leaves the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the simulator. The downloadable summary is built in your browser too.

How is shared platform cost divided between teams?

Shared platform cost is the slice of the bill nobody owns directly — shared clusters, platform tooling, or egress nobody can attribute. You set it as a percentage of the total bill, and the tool distributes it across teams in proportion to their direct shares: a team with 40% of the direct spend carries 40% of the shared pool. That is the step-down rule FinOps guides recommend, and it keeps every dollar attributed exactly once.

What happens if my team shares do not add up to 100%?

The tool scales your shares proportionally, so the split always covers the whole bill — a team with 40 out of 80 entered points gets half the bill. A warning names the actual total so you can see what happened. Press 'Normalize shares to 100%' to rewrite the team shares to a clean 100% split, or edit the numbers directly. If you enter no shares at all, the bill is split equally between teams and the tool says so.

How do the what-if growth sliders work?

Each slider grows or shrinks one service's spend — for example, compute up 20% if a new workload lands, or storage down 10% after a cleanup. The projected monthly and annual totals, every team's projected share, and the per-service table all update instantly. The sliders never change your entered spend: reset them to 0% and you are back to today's bill.

What is the difference between showback and chargeback?

Showback reports each team's share of the bill so teams can see what they cost, but no money moves. Chargeback actually bills the cost back to each team's budget or cost centre. Both need the same first step — a defensible split of the bill — which is what this tool produces. Use the downloadable summary as the starting point for either conversation, and agree the shared-cost rule with finance before you charge anyone.

Can I download or share the results?

Yes. Press 'Download summary' and the tool builds a plain-text file in your browser with the spend by service, the per-team monthly and annual totals, the shared-cost split, and the what-if projection. Nothing is uploaded to make it — the file is generated on your device, so you can paste it into a budget review, an email, or a ticket.

What does this tool NOT do?

It does not estimate what your cloud bill should be, fetch live provider pricing, read a real invoice, or connect to any cloud account — it only splits the numbers you enter. It is a planning model, so a wrong input produces a wrong split: check your figures against your provider's billing console first. It also cannot settle arguments about who caused a spike; for that you need tagged resources and usage metrics, which this tool deliberately never asks for.