Database · Integration · New in 0.4.0

MongoDB Atlas cost tracking: daily cost per cluster and SKU

See what each Atlas cluster costs per day, by project and SKU, next to the rest of your stack, straight from the line items on your Atlas invoices.

What Burnstack tracks

  • Daily invoice line items in USD per project, cluster and SKU (instance hours, storage, data transfer and more), from Atlas's invoice API (MongoDB docs), with discounts taken off
  • The current billing cycle from Atlas's pending invoice (MongoDB docs), which grows as charges post, usually the next day
  • Credits and sales tax from each invoice, spread over its days on the organization; App Services apps and project-level charges such as backups on their project

Alerts

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

The key you'll need

An organization service account with only the Organization Billing Viewer role, the role Atlas's invoice endpoints require (MongoDB docs). An Organization Owner creates it under Organization → Identity & Access → Applications → Service Accounts. Paste ORG_ID:CLIENT_ID:CLIENT_SECRET; Atlas shows the secret once. MongoDB recommends service accounts over the older API keys (MongoDB docs), and Burnstack doesn't accept API keys.

Burnstack checks the key with MongoDB Atlas, shows the account it belongs to when MongoDB Atlas 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: MongoDB Atlas

About 5 minBilled

Need

  • Key: Organization ID and service account
  • Plan: Any organization; an Organization Owner creates the service account.
  • Permissions: Organization Billing Viewer

In your organization, go to Identity & Access → Applications → Add new → Service Account and give it only the Organization Billing Viewer role. Paste ORG_ID:CLIENT_ID:CLIENT_SECRET (the organization ID is under Organization Settings; the secret starts with mdb_sa_sk_). API keys aren't supported. Atlas only accepts API calls from addresses on the service account's API access list: add this computer's IP, or, for a laptop on changing networks, an organization owner can turn off "Require IP Access List for the Atlas Administration API" and leave the list empty. Costs are Atlas's daily invoice lines per project, cluster and SKU, in USD.

Steps

Open MongoDB Atlas's key page ↗

  1. In your organization, open Identity & Access → Applications → Add new Service Account.
  2. Name it Burnstack, set the Client Secret Expiration, and select only Organization Billing Viewer.
  3. Click Create and copy the client secret (mdb_sa_sk_…, shown once).
  4. Add this computer's IP to its API access list (Add Access List Entry → Use Current IP Address).
  5. Paste ORG_ID:CLIENT_ID:CLIENT_SECRET into Burnstack.

Paste it

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

If it fails

IP address … is not allowed to access this resource
Add this computer's IP to the service account's API access list, or have an Organization Owner turn off "Require IP Access List for the Atlas Administration API" and leave the list empty.
invalid_client
Check the client ID and secret, and that the secret hasn't expired.
needs the Organization Billing Viewer role
Give the service account Organization Billing Viewer under Identity & Access → Applications.
API keys aren't supported
Create a service account instead (ORG_ID:CLIENT_ID:CLIENT_SECRET).

Let your AI do the clicking

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

Open https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Faccess%2FserviceAccounts in my browser. Under Identity & Access → Applications choose 'Add new Service Account'. Name it 'Burnstack', description 'Read-only billing for Burnstack', and under Organization Permissions select only 'Organization Billing Viewer'. Tell me the organization ID and the client ID (mdb_sa_id_…); they aren't secret. Set Client Secret Expiration to 90 days (or the closest shorter option). Stop before clicking 'Create' (the final button that creates the client secret) and tell me it's ready. I'll click it, copy the client secret and paste it into Burnstack myself. Don't copy, read or paste the client secret, and don't grant broader access or change any other setting. After I say I've copied the secret, click 'Add Access List Entry', choose 'Use Current IP Address' and Save. If MongoDB Atlas 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 MongoDB Atlas charges it.
  • History: All invoices since the organization started.
  • Delay: Charges typically post the next day.

Good to know

  • IP access list: Atlas accepts API calls only from addresses on the service account's access list, and organizations created in the Atlas UI require one by default (MongoDB docs). Add this computer's public IP, or each network you work from. Or an Organization Owner can turn off "Require IP Access List for the Atlas Administration API" and leave the list empty; that's less locked down, though the account can still only read billing.
  • Amounts are read as US dollars: Atlas's API states every amount in US cents.
  • Linked (cross-organization) invoices aren't counted; connect each organization on its own.
  • Days are only as fine as Atlas's line items: support plans and other monthly charges show where Atlas dates them, often spread over the month.
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 MongoDB Atlas 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, Railway, Render, Heroku, Akamai (Linode), Vultr, Fastly, Runpod, xAI, Together AI, fal.ai, Runway, Upstash.

MongoDB Atlas questions

Why does Atlas say my IP address isn't allowed?
Your organization requires an IP access list for the Atlas Administration API, and this computer's address isn't on the service account's list. Add it in Atlas under the service account's API access list. Burnstack's error says which fix applies.
Can the service account change my clusters?
No. With only Organization Billing Viewer it can read the organization's invoices and billing, not your clusters, data or settings. Burnstack only reads with it.

Start watching back.

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