The ledger must preserve audit history without billing a recovered workload twice.
Finance needs a defensible close, while customers need a bill that matches the runtime they experienced.
Who you’d be doing this for
“Our finance lead sent me two line items for the same training run, and I can’t show which one is real.”
Joanna Popov · ML Platform Engineer
Runs production training workloads for an enterprise AI team using Kubernetes GPU clusters.
What is at stake
Some recovered Kubernetes workloads appear to have been charged for the same GPU runtime twice. You must weigh a fast customer correction against an audit trail Finance can defend.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- customer credits vs. audit permanence
- automated recovery vs. billable-runtime certainty
- billing close speed vs. evidence verification
- fleet availability vs. manual exception handling
Why Crusoe
GPU compute billing depends on trustworthy links between Kubernetes workloads, Conductor remediation, and customer usage records.
Written with these in mind
Not your kind of problem? 76 more at Crusoe, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.