Neon
What Plutus imports
Section titled “What Plutus imports”- Compute, storage, snapshot, instant-restore, and data-transfer usage by project (estimated)
Connecting
Section titled “Connecting”Method: API Key
- Go to console.neon.tech, select your organisation, then go to Settings > API keys.
- Click Create new API key. Create an organisation-scoped key, not a personal one — a personal key only sees projects you own, not the whole org.
- Copy the key. Neon only shows it once. Paste it into the API Key field in Plutus.
- On the same Settings page, copy your Organisation ID (it starts with
org-) and paste it into the Organisation ID field in Plutus. This is required — Neon’s consumption endpoint is org-scoped. - Optionally, set custom Compute Rate per CU-hour, Storage Rate per GB-month, or Data Transfer Rate per GB. Leave these blank to use Neon’s published plan rates (Launch $0.106/CU-hour, Scale $0.222/CU-hour; $0.35/GB-month storage; $0 data transfer). Set them only if you’re on a negotiated Enterprise rate or a contract that bills transfer.
- Save the connection. Plutus calls Neon’s Consumption API to pull daily usage per project and prices it against the rates above.
Neon’s Consumption API only serves the last 60 days of daily usage, so the first sync backfills at most 60 days. Longer history builds up from there as subsequent syncs run.
Neon exposes usage, not dollars — there is no invoice API available to integrations — so cost is estimated from consumption against published per-unit pricing rather than actual invoiced spend. The estimate does not net off your plan’s included allowances or any committed-use discount, so it reads high against a small bill.