
Your Neon Postgres storage, compute hours, and branch activity on your iPhone home screen, updated on demand.
Neon's Free and Launch plans cap storage and compute hours each billing period. The Project Usage module surfaces both numbers in a home screen widget: current storage in MB and compute-hours consumed since your billing period reset. When that compute-hours number climbs mid-month, you see it before an overage hits. Storage, active time, written data, and data transfer are all exposed as point values that reset with each billing cycle.
The Organization module sums storage and compute time across every project in a Neon organization, giving a single aggregate number without opening the Neon console. For engineering leads on Scale-plan orgs, total active time and total compute hours answer the "where is team usage trending?" question from the lock screen.
The Branch Usage module goes the other direction: pick a project, then pick a branch, and track compute time, written data, and age for that branch alone. Long-lived staging and preview-production branches are the usual suspects for unexpected compute spend. Age in days is shown alongside compute hours, so you can spot branches that have been running longer than their purpose warrants.
PulseKit fetches metrics when you pull to refresh or open a widget. It reads from Neon's management API, not from a live Postgres connection, so no compute endpoint is started or woken during a fetch. Connect with a Personal API key to see all projects across your account, or use an Organization API key scoped to the member role if you prefer tighter access control.
Generate a Neon API key at console.neon.tech/app/settings/api-keys. The simplest option is a Personal API key, which covers every project on your account. Name it (e.g. "PulseKit") and copy the value here. For tighter scoping, use an Organization API key with the member role instead. PulseKit reads only; it never modifies or deletes Neon resources.
Security
Your Neon API key is sealed on this device with AES-256-GCM before it ever leaves your iPhone. Only your device holds the unwrap secret, stored in the iOS Keychain. The PulseKit backend wraps that already-encrypted payload again with its STORAGE_SECRET and writes the double-envelope blob to Postgres, so the server never sees your plaintext key at rest. Each fetch request includes a one-time unwrap secret that decrypts the inner envelope only long enough to call Neon. The key is scoped to this device, can be revoked from PulseKit at any time, and is never written to logs.
Pick the metrics you care about and pin them as widgets.
Track storage, compute, branches, and write throughput for a single project
Track aggregated usage across every project in a Neon organization
Track compute, write, and age for a specific branch within a project
Numbers shown are illustrative — your widgets show your live data.
You are running one or two side projects on Neon's Free or Launch plan and the main question each month is whether storage or compute hours will breach the plan cap. Pin a Project Usage widget to your home screen and the two numbers that answer that question are visible without opening a browser.
Your team operates multiple Neon projects across a Scale-plan org. The Organization widget gives a daily read on total compute and storage across the whole org, while Branch Usage widgets pinned to staging and preview-production branches flag runaway compute before it shows up on the invoice.
You create feature branches for each pull request and want to know which ones are still burning compute after the PR merges. The Branch Usage module shows compute time and branch age for any branch you select, making it straightforward to identify and clean up branches that have outlasted their purpose.
No. PulseKit reads project, branch, and organization metrics from Neon's management API, which operates independently of compute endpoints. Fetching storage, compute hours, or branch data does not start or wake a suspended endpoint. This is consistent with Neon's documentation on consumption metric reads.
All three modules work on Neon's Free plan and above. Project Usage, Organization, and Branch Usage all read billing-period consumption metrics available on every plan. Consumption history charts are not included in this integration, so there is no Scale-plan requirement.
Yes. Add one Project Usage widget per project you want to track and pin each to your home screen or Today View. The Organization module complements this with a single aggregated number across all projects in an org, useful when you want a total view rather than per-project detail.
The Branch Usage module tracks compute time in hours, active time in hours, written data in MB, and branch age in days for a specific branch you select. It is intended for long-lived branches such as staging or preview-production environments, where unexpected compute spend is easiest to miss.
Generate an API key at console.neon.tech/app/settings/api-keys, name it (e.g. PulseKit), and paste it into the PulseKit connection screen. A Personal API key covers all projects on your account. For narrower scope, create an Organization API key with the member role under your org's API Keys settings.
Yes. An Organization API key with the member role provides read access to all projects within that organization and works with all three modules. It offers tighter scope than a Personal key, which covers every project across your entire Neon account. Either key type works with PulseKit's read-only access pattern.
PulseKit fetches Neon metrics on demand each time you refresh a widget. Values reflect Neon's billing-period totals at the moment of the request, so storage and compute figures are current as of your last refresh. There is no background polling between refreshes.

Install PulseKit, paste your credentials, pick a widget.