Cloud hosting · Integration · New in 0.9.0

Vultr cost tracking: invoice items and pending charges

See what each Vultr instance and service costs over the days it covers, plus this month's charges so far, next to the rest of your stack.

What Burnstack tracks

  • Each invoice item in USD, spread evenly over its start and end dates, one line per item description, such as Cloud Compute (web-1) (Vultr docs)
  • This month's pending charges, spread from each charge's start to today. They're charges Vultr has already accrued, so they count as billed, and they stop counting once an invoice covers those days
  • Every invoice on the first sync

Alerts

  • Vendor spend spike: a day above 2.5× Vultr's 14-day median

The key you'll need

The API key of a user with only the Billing permission. A Vultr key can do whatever its user can, so add a user under Account → Users with only Billing and API access, sign in as that user and copy its key under Account → API. If your account has an API access control list, add this computer's IP address (Vultr docs). Key health warns you if the key's user can do more than read billing.

Burnstack checks the key with Vultr, shows the account it belongs to when Vultr lets the key see it, and stores it in your computer's keychain (macOS Keychain or Windows Credential Manager). It only reads billing and usage.

Connect it: Vultr

About 4 minBilled

Need

  • Key: API key of a billing-only user
  • Plan: Any account; the key's user needs the Billing permission.
  • Permissions: User permissions: Billing only API access enabled

Vultr API keys can do whatever their user can, so add a user with only the Billing permission and API access (Account → Users), sign in as that user and copy its API key under Account → API. If your account has an API access control list, add this computer's IP address. Burnstack reads your invoice items, spread over the dates each covers, and this month's pending charges up to today.

Steps not yet verified

Open Vultr's key page ↗ not yet verified

  1. As the account owner, open Account → Users and add a user named Burnstack.
  2. Give it only the Billing permission and turn on API access.
  3. Sign in as that user, open Account → API and click Enable API.
  4. Copy the API key and paste it into Burnstack.
  5. If you use API Access Control, add this computer's IP address.

Paste it

In Burnstack: Connectors → Vultr → Add key → paste → Validate & save. The key goes straight into your computer's keychain.

If it fails

Vultr API error 401
The key was regenerated or mistyped, or API access is off for its user. Copy the key again under Account → API.
Vultr API error 403 not yet verified
The key's user needs the Billing permission, and an API access control list must include this computer's IP address.

Let your AI do the clicking not yet verified

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Vultr's key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://my.vultr.com/settings/#settingsapi in my browser. Open Account → Users and choose 'Add User'. Enter 'Burnstack' as the name, tick only the Billing permission and turn on API access. Leave the password for me to set. Vultr has no expiry setting for this key, so skip that. Stop before clicking 'Add User' (the final button that creates the key) and tell me it's ready. I'll click it, copy the key and paste it into Burnstack myself. Don't copy, read or paste the key, and don't grant broader access or change any other setting. After I've added the user, tell me to sign in as it and copy its API key under Account → API. If Vultr asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Billed: Billed cost, as Vultr charges it.
  • History: All invoices.
  • Delay: Invoices after each month closes; this month from pending charges so far.

Good to know

  • With an API access control list, Vultr refuses the key from any address that isn't on it, so add each network you sync from.
  • Pending charges are a running total: between daily syncs a day's share can shift as charges accrue; the next daily sweep spreads them again.
  • Items with the same description share one line.
Burnstack Connectors, Add cost source tab: a search box, category filters and one card per vendor with its key steps

One bill, not a dashboard per vendor

Burnstack puts Vultr next to the rest of your spend and lets you group it by product with applications. Other integrations: Vercel, Neon, Supabase, OpenAI, Anthropic, GitHub, OpenRouter, DigitalOcean, Twilio, Stripe fees, Cloudflare, Netlify, AWS, Datadog, Sentry, Cursor, PlanetScale, Azure, Google Cloud, MongoDB Atlas, Railway, Render, Heroku, Akamai (Linode), Fastly, Runpod, xAI, Together AI, fal.ai, Runway, Upstash.

Vultr questions

Why a separate Vultr user for Burnstack?
Vultr API keys belong to a user and can do everything that user can. A user with only the Billing permission gives Burnstack a key that can read billing and nothing else.
Are Vultr's pending charges an estimate?
No. They're the charges Vultr has accrued so far this month. Burnstack spreads them up to today, and the invoice items take over once the month is invoiced.

Start watching back.

Five minutes to connect your first vendor. Free for Mac, forever, and every byte stays yours.