The useful path

Start by treating the provider invoice as source data, not the final report. Normalize resources into canonical project names, preserve the original provider fields, and keep unallocated spend visible.

  • Map DO project names to canonical projects.
  • Use tags such as project:acme-prod where available.
  • Keep invoice line-item detail available for audit.

Working example

A simple rule can convert a DigitalOcean tag into a canonical key: if a resource has tag project:acme-prod, assign it to project=acme-prod. If no tag exists, fall back to account or resource-name rules, then leave the rest unallocated.

Who tovin.io is for

SREs & Platform Engineering leads Solo founders Finance & ops

Frequently asked

Can DigitalOcean spend be allocated per customer?

Yes, when customers map cleanly to projects, tags, or naming rules.

Should the DO token be write-capable?

No. Cost monitoring should use read-only access wherever possible.