Tracking project spend
The Admin → Projects page is where attribution pays off. Pick a project on the left and its full cost picture appears on the right — what it’s burning right now, what it’s cost all-time, and where that money went.
Any org member can open this page. Admins can also add, rename, and archive projects from it; members see a read-only spend view.
The project selector
Section titled “The project selector”The left column lists every live project. Each row shows the project name plus a quick summary — its instance count and current hourly burn — so you can spot the expensive ones at a glance. Click a project to load its detail panel.
Admins get a + New project control at the bottom of the list.
The detail panel
Section titled “The detail panel”Selecting a project shows three headline figures:
| Stat | What it means |
|---|---|
| Current burn | The project’s live cost rate right now — compute plus storage — in $/hr, with an approximate $/day underneath. This is the rate the project is accruing at this instant, not a bill. |
| Total spent | Cumulative, all-time charged cost attributed to the project (compute + storage). This matches what’s actually been billed or metered. |
| Compute / storage | The cumulative total split into its compute and storage halves, so you can see which side dominates. |
Instance and storage drill-down
Section titled “Instance and storage drill-down”Below the stats, the Instances section lists every instance currently attributed to the project — name, state, specs, host, and per-instance hourly cost — followed by the project’s storage bucket and its warm-storage cost, if it has one. It’s the same drill-down view admins get for org members, scoped to this project.
How the numbers are computed
Section titled “How the numbers are computed”- Current burn is summed live from the project’s running instances and its bucket’s current warm-storage rate.
- Total spent is summed from the project’s billing records. Every compute and storage billing interval carries a snapshot of the project it was attributed to at the time, so totals are exact and survive a project rename, archival, or bucket deletion. (This is also why re-assigning an instance never disturbs past totals.)
Because each project’s records are indexed by project, these lookups stay fast even with hundreds of thousands of billing intervals on the books.
Billing a project directly — coming soon
Section titled “Billing a project directly — coming soon”Today, projects attribute spend within your existing org bill. Two pass-through options are on the way, and you’ll see them on each project’s detail panel:
- Generate invoice — invoice a project’s costs directly to a client.
- Generate prepay link — share a link that funds prepaid credits earmarked for a specific project.
Both are visible but disabled for now, already scoped to the selected project — when they ship, the money stays attributed to that project end to end.