Integrations3 min read
CostGraph launches support for Depot
CostGraph now imports Depot container-build, GitHub Actions runner, storage, and sandbox usage, so CI spend sits next to cloud and infrastructure costs, with cache minutes saved visible alongside minutes billed.
By CostGraph Team
ChatGPTLast week we shipped a bunch of integrations specifically for cloud providers. This week we are turning our attention to CI.
Continuous integration and deployment is a core part of how we build and ship software. Today we are announcing support for Depot.
Depot offers remote Docker builds on a shared layer cache, managed GitHub Actions runners, cache and registry storage, and agent sandboxes. Teams put it in front of CI to make builds faster. CostGraph now imports that usage and shows it alongside cloud, Kubernetes, and the rest of your infrastructure.
Each product lands as its own service, so the build-versus-runner-versus-storage mix is visible instead of one opaque CI bill:
- Container builds. Remote Docker builds, billed by the minute, broken out per project. CostGraph also keeps the acceleration signal: minutes the layer cache saved versus minutes actually billed. High saved-to-billed means the cache is earning its keep. Low saved with high billed is cold-cache waste.
- GitHub Actions runners. Managed runners for existing workflows, billed by runner minute, per repository.
- Storage. Cache and registry storage, billed per GB-month.
- Agent sandboxes. Ephemeral compute for coding agents, billed by the minute.
Depot support is available on all CostGraph plans. To connect an account, open Settings -> Integrations, select Depot, and provide an organization API token.
Why are we doing this
The cost of developing software is growing across the board. The sudden increase in velocity has caused not only the world's largest source code hosting platform to go down, but even parts of the lifecycle you might not have noticed.
For us, it was also to answer the question, "since when did we start paying this much for CI?"
If this sounds interesting, get started for free or book a demo today
Frequently Asked Questions
CostGraph now supports importing and visualizing Depot usage and cost.
Customers can view Depot container-build, GitHub Actions runner, storage, and sandbox spend alongside their cloud, Kubernetes, and other infrastructure costs within CostGraph.
The Depot integration is available to customers on all CostGraph plans.
CostGraph connects to Depot using an organization API token. It reads usage history once a day, then normalizes billed minutes and stored GB into the same FOCUS-based cost model used for other providers.
Each charge is one record per product line, per project or repository, over the pull window.
CostGraph requires a Depot organization token, created under Organization -> Settings -> API Tokens.
CostGraph only uses it to read usage history. Organization tokens can also create builds in Depot, so treat them as a secret. Revoke the token in Depot at any time and the connection stops.
Depot costs include the product (container builds, GitHub Actions runners, storage, or sandboxes), the project or repository, billed minutes or stored GB, and, for container builds, minutes saved by the layer cache.
This makes it possible to see which CI surface is driving spend, and whether the cache is actually accelerating builds.
Depot’s usage API reports billed minutes and stored GB, not dollars. CostGraph reconstructs cost from those quantities using Depot’s published rates (container builds at $0.04/min, GitHub Actions at $0.004/min, sandboxes at $0.01/min, storage at $0.20/GB-month), or rates you set on the connection if your organization is on negotiated pricing.
Plan-included minutes are not subtracted. The exact billed dollars live on the Depot invoice. Set the rate overrides on the connection if you need the figure to match your contract.
Not in this launch. Depot’s usage dashboard also tracks Depot CI minutes, billed per vCPU-second. CostGraph currently maps container builds, GitHub Actions runners, cache storage, and agent sandboxes.
CostGraph checks for updated Depot usage once a day.
CostGraph shows minutes saved next to minutes billed for container builds, plus cache size and build count when that information is available. That is usually enough to see whether acceleration is paying for itself.
Rightsizing-style recommendations, the kind we generate for VMs and managed databases, are not part of this launch.