Repository navigation
fix(blog): Neon Free CU-hours are per project in the serverless Postgres guide - #8420
Conversation
…res guide "100 CU-hours across 100 projects" read as one shared pool. Neon gives each project its own 100 CU-hours, up to 100 projects. Verified on 2026-10-08 against https://neon.com/docs/introduction/plans. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. 2 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour. WalkthroughThe Neon free-tier description now states that each project receives 100 CU-hours. The surrounding text still describes a limit of up to 100 projects. ChangesNeon allowance description
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The change clarifies the Neon allowance wording, and the supplied context identifies no material issue preventing merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
What
In
serverless-postgres, the side-project bullet said Neon gives "100 CU-hours across 100 projects", which reads as one pool shared by all projects. Neon gives each project its own 100 CU-hours, up to 100 projects. The rest of the post (glance table, Neon section, FAQ) and the chooser card already say per project.Verified on 2026-10-08 against Neon's plans docs: "100 CU-hours/project", 100 projects.
Follow-up to #8390.
Checks
check-ai-signs.shandcheck-plain.share clean.check-staccato.pyreports three FAQ fragment openers that were already on main; none is on the changed line.🤖 Generated with Claude Code
Summary by CodeRabbit