Netlify cost tracking: plan, build minutes, bandwidth
See your Netlify plan fee next to the rest of your bill, plus the build minutes and bandwidth you've used so far this billing period.
What Burnstack tracks
- Your plan fee per team, estimated from Netlify's list prices (Netlify pricing) and marked est.
- Build minutes and bandwidth used so far in the billing period, with your plan's allowance, as usage counts. They aren't priced
- Exact charges, such as credit purchases or add-ons, when you import invoice lines as CSV; imported days replace the estimate
Alerts
- Stale data: Burnstack tells you when the token stops working, for example after it expires
- Vendor spend spike, on the estimate and imported lines only, so it rarely fires for Netlify
The key you'll need
A personal access token with an expiration date, from Netlify's User settings → Applications → Personal access tokens (Netlify docs). Netlify tokens can't be limited: a token can do everything your user can, including deploys and deleting sites. Burnstack only sends read requests with it. For a team that requires SSO, tick "Allow access to my SAML-based Netlify team".
Burnstack checks the key with Netlify, shows the account it belongs to when Netlify 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: Netlify
Need
- Key: Personal access token
- Plan: Any plan. Exact charges need invoice imports; the API has no billing data.
- Permissions: No scopes: the token can do what your user can (Burnstack only reads)
Create a personal access token with an expiration date. A Netlify token can't be limited to read-only: it can do anything your user can, though Burnstack only reads. Netlify's API has no billing data, so Burnstack estimates your plan fee from list prices (est.) and you can import invoice lines as CSV for exact totals. Bandwidth comes from an undocumented endpoint that may stop working; build minutes and bandwidth are shown as usage, unpriced.
Steps
- Open User settings → Applications → Personal access tokens.
- Click New access token and name it Burnstack.
- Pick an expiration (tick the SAML option only if your team uses SSO).
- Click Generate token, copy it and paste it into Burnstack.
Paste it
In Burnstack: Connectors → Netlify → Add key → paste → Validate & save. The key goes straight into your computer's keychain.
If it fails
- Netlify API error 401
- The token expired, or a password reset invalidated it. Create a new personal access token.
- This token can't see any Netlify teams
- For a team that requires SSO, create the token with 'Allow access to my SAML-based Netlify team' ticked.
Let your AI do the clicking
Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Netlify's key page and sets only the permissions above, then stops before the final button that creates the key.
Open https://app.netlify.com/user/applications#personal-access-tokens in my browser. Choose 'New access token' and enter 'Burnstack' as its name. Tick 'Allow access to my SAML-based Netlify team' only if my team uses SAML SSO; ask me if you're not sure. Set Expiration to 90 days (or the closest shorter option). Stop before clicking 'Generate token' (the final button that creates the token) and tell me it's ready. I'll click it, copy the token and paste it into Burnstack myself. Don't copy, read or paste the token, and don't grant broader access or change any other setting. If Netlify 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
- Estimated: Estimated from Netlify's usage at list prices, marked est. in Burnstack.
- History: Any range for the plan baseline; usage is a snapshot from each sync.
- Delay: Plan fees are estimated at each sync; build minutes and bandwidth are period-to-date snapshots.
Good to know
- Netlify's API has no invoice or charge endpoints (Netlify API reference), so every dollar figure is an estimate unless you import invoice lines.
- On a Pro team created before September 4, 2025, Burnstack assumes Legacy Pro (priced per member), because the API doesn't say which Pro plan a team is on. Legacy Pro also bills Git contributors the API doesn't list, so that estimate can be low.
- Build minutes and bandwidth are period-to-date totals, not daily usage. Bandwidth comes from an endpoint Netlify doesn't document, so it may stop working.
- Credit purchases and auto-recharge, usage packs, add-ons, taxes and Enterprise contracts only arrive through CSV import.
- Resetting your Netlify password invalidates every token; paste a new one after that.
One bill, not a dashboard per vendor
Burnstack puts Netlify 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, AWS, Datadog, Sentry, Cursor, PlanetScale, Azure, Google Cloud, MongoDB Atlas, Railway, Render, Heroku, Akamai (Linode), Vultr, Fastly, Runpod, xAI, Together AI, fal.ai, Runway, Upstash.
Netlify questions
Why can't Burnstack show my real Netlify bill?
Is a full-access Netlify token safe to use?
Start watching back.
Five minutes to connect your first vendor. Free for Mac, forever, and every byte stays yours.