Neon Automated Database Usage Alerts
On a regular schedule, WebRun opens the Neon console, reads compute hours used and storage size across every project and branch, saves a dated usage snapshot to Google Drive, and texts you through Twilio only when a project is nearing its plan limit.
How do I get alerted when a Neon database is nearing its plan limit?
WebRun checks every Neon project on a regular schedule, reading compute hours used and storage size across every branch. It saves a usage snapshot to Google Drive and texts you through Twilio only when a project is nearing its plan limit, so a serverless Postgres database never gets throttled without warning.
- Compute and storage limits get flagged before throttling happens
- Every project gets a regular usage check
- A running usage history builds up in Drive automatically
Built for Backend engineering teams · indie developers · startup CTOs · platform engineers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
console.neon.techin a real browser with your saved login - no setup, no API keys. -
1
Neon - check compute and storage usage
WebRun opens Neon to check compute and storage usage. - Open the Neon console and review every project
- Read compute hours used and storage size for each branch
- Flag anything approaching its plan limit
Done when Every project has a current compute and storage reading.
-
2
Google Drive - save the usage snapshot
WebRun opens Google Drive to save the usage snapshot. - Save the usage snapshot as a dated file in your shared Drive folder
- Keep prior snapshots for a running history
Done when This run's snapshot is saved to Drive.
-
3
Twilio - text on nearing plan limit
WebRun opens Twilio to text on nearing plan limit. - If a project is nearing its plan limit, text you directly through Twilio
- Name the project and the metric that's close
- Stay quiet when every project has headroom
Done when You get a text only when a project is genuinely close to its limit.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it upgrade my plan or change a database setting on its own?
No. WebRun only reads usage data and saves a snapshot. Upgrading a plan or changing a database setting always stays a manual step in Neon.
What counts as nearing a plan limit?
A project's compute hours or storage size getting close to the ceiling on its current plan, flagged early enough to upgrade before anything gets throttled.
Does it check every project and branch?
Yes. It reviews every project and its branches under the account each run, not just your primary database.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.