We're a team of about 15 engineers and our cloud compute bill keeps going up but we can't tell who's driving it. How do development environment platforms usually handle per-user quotas and cost tracking so we can see where the spend is coming from?

“For example, GitHub Codespaces provides organization-level controls for machine types, idle timeouts and retention periods.”

“- Restricting available machine sizes.”

“- Setting maximum idle timeouts.”

“- Controlling how long stopped environments are retained.”

“- Managing prebuild-related storage costs.”

“This is particularly useful if you want to prevent expensive configurations rather than simply report their costs after the fact.”

“Its quota system supports: - Per-user budgets.”

“- Group-based quota allowances.”

“- Cost estimates associated with workspace templates.”

“- Blocking new workspace launches when a user exceeds their budget.”

“One particularly interesting detail is that Coder allows different costs for running and stopped resources.”

“This is a useful model for distinguishing compute costs from persistent infrastructure costs.”

“provides organization-level compute pools and sandbox resource limits.”

“It also uses resource-based billing, with CPU, memory and disk consumption accounted for separately.”

“This is useful when you want to understand the actual resource consumption of individual development sandboxes.”