Skip to main content
DigitalOcean bills Droplets, volumes, load balancers, databases and spaces against one account, so a single connection captures the whole invoice. CostGraph reads DigitalOcean as FOCUS 1.2 records at a grain of invoice line item (product x resource), with per-project attribution.

​
Choose how the data reaches us

CostGraph pulls it

You supply a read-only token and we call DigitalOcean once a day. Nothing to run.

You push it

You send us FOCUS records over the API. Credentials never leave your infrastructure.

​
Let CostGraph pull

  1. Open Settings -> Integrations and pick DigitalOcean.
  2. Name the connection and pick the tenant these charges belong to.
  3. Create a Personal Access Token with read scope under Account -> API -> Tokens and paste it in.
  4. Select Connect.
The billing account label is optional: leave it empty and we resolve it from your account. A team gives its UUID and name; an account with no team uses the account UUID for both. Your account email is never used as a label, so no personal email reaches CostGraph. CostGraph verifies the token with a short fetch before saving, so a wrong value or a missing permission fails while you are still on the form.
Credentials are encrypted at rest and used only to read billing data. Revoke the token in DigitalOcean at any time and the connection stops; nothing else is affected.

​
Push it yourself

Send the charges to CostGraph as FOCUS records instead. Push FOCUS data covers the connection id, the focus:write key, and the request shape.

​
What CostGraph does with it

Records land as raw billing rows, are normalised into line items, and roll up into daily cost. From there DigitalOcean spend appears in Cost Overview and in anomaly detection alongside every other provider.