Blog: Serverless Postgres, the definitive guide (hub + interactive decision tree)

[vanrensbird]

What

New evergreen hub post at /blog/serverless-postgres: the category guide for serverless Postgres, anchoring the hub-and-spoke cluster (comparison and migration spokes follow separately). Reviewed and approved by Martin on localhost.

• Profiles the five most-shortlisted providers (Prisma Postgres, Neon, Supabase, Aurora Serverless v2, PlanetScale) with verified prices and behaviors
• The rest of the field: Xata, Nile, the Tembo pivot, DigitalOcean/Render/Heroku/Railway, and the non-Aurora hyperscaler options, sorted honestly into serverless vs managed
• The three-pricing-models framing with a worked cost-crossover example (30M queries/month: ~$89 operations billing vs ~$77 always-on Neon CU)
• Interactive decision tree (DecisionTree + ServerlessPostgresChooser): schema-diagram-style cards on a dotted canvas, answers fan into up to two candidate cards with dashed connectors, sibling answers are mutually exclusive, clicked rows stay pinned in the viewport. The complete tree also ships as server-rendered text (visible details block), so crawlers and AI engines read every branch. Prisma cards carry a subtle accent; competitor recommendations are real (Neon, PlanetScale, Aurora, and Supabase each win branches)
• Six FAQ accordions, answer-first lead, canonical links, updated bundled-backend guidance including Prisma Postgres + Compute (public beta stated)

Provenance

Researched via a 105-agent deep-research run (24 claims verified 3-0 against primary sources) plus targeted primary-source sweeps for Supabase, Aurora auto-pause, PlanetScale, and ten additional providers. Then six rounds of adversarial review per the new Step 10 process (#8044): 51 findings found and fixed across rounds, including two flatly wrong claims and a steered decision-tree branch, closing on zero-finding verification rounds. Every price and behavior cites the vendor's live page as of July 2026; vendor claims (including ours) are labeled as such.

Open item

No hero image yet: heroImagePath is intentionally absent and can land as a follow-up (input welcome from design).

Measurement

Five Promptwatch prompts tracking the target queries were created before publication for a clean before/after citation baseline.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • Added a new blog post on serverless PostgreSQL explaining how billing units and idle behavior affect provider choice, with side-by-side comparisons and a workload chooser.
  • Introduced an interactive decision-tree UI with expandable questions, visual connectors, a “collapse all” option, and a plain-text fallback for non-interactive rendering.
• Documentation
  • Enabled the new serverless PostgreSQL chooser to be embedded directly within blog MDX content.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jul 10, 2026 3:19pm
docs	Ready	Preview, Comment	Jul 10, 2026 3:19pm
eclipse	Ready	Preview, Comment	Jul 10, 2026 3:19pm
site	Ready	Preview, Comment	Jul 10, 2026 3:19pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: bf95662b-2854-4989-8ae6-01f6e4011d93

📥 Commits

Reviewing files that changed from the base of the PR and between 5637d80 and b4db6dc.

⛔ Files ignored due to path filters (2)

• apps/blog/public/serverless-postgres/imgs/hero.svg is excluded by !**/*.svg
• apps/blog/public/serverless-postgres/imgs/meta.png is excluded by !**/*.png

📒 Files selected for processing (1)

• apps/blog/content/blog/serverless-postgres/index.mdx

---

Walkthrough

Adds a serverless Postgres guide with provider comparisons, pricing and idle-behavior guidance, an interactive chooser, a reusable client-side decision-tree component with SVG connectors and text fallback, and MDX registry wiring.

Changes

Serverless Postgres Guide and Chooser

Layer / File(s)	Summary
DecisionTree component core apps/blog/src/components/DecisionTree.tsx	Adds exported decision-tree types and a client component with expansion state, DOM-measured SVG connectors, branch rendering, collapse controls, and a text-only fallback.
ServerlessPostgresChooser decision data and wiring apps/blog/src/components/ServerlessPostgresChooser.tsx, apps/blog/src/mdx-components.tsx	Defines the provider-selection graph, renders it through DecisionTree, and registers the chooser in the MDX component map.
Serverless Postgres article foundations apps/blog/content/blog/serverless-postgres/index.mdx	Adds article metadata, framing, provider comparisons, workload recommendations, and explanations of billing models and idle behavior.
Provider profiles and selection guidance apps/blog/content/blog/serverless-postgres/index.mdx	Adds provider profiles, cost crossover analysis, secondary considerations, alternative provider categories, FAQ entries, and the closing call to action.

Estimated code review effort: 3 (Moderate) | ~30 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the new Serverless Postgres blog post and its interactive decision tree.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

apps/blog/src/components/DecisionTree.tsx (1)

347-379: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick win

Add cycle detection to recursive tree components

Both TextTree and TreeBranch recurse through next targets without tracking visited nodes. The current tree data is acyclic, but since DecisionTree is a reusable exported component, a future data change introducing a cycle would cause TextTree to infinitely recurse during server rendering (crashing the page) and TreeBranch to hang the tab on user interaction. A simple visited-set guard prevents both.

🛡️ Proposed fix for TextTree cycle detection

 function TextTree({
   byId,
   nodeId,
+  visited = new Set<string>(),
 }: {
   byId: Map<string, DecisionNode>;
   nodeId: string;
+  visited?: Set<string>;
 }) {
   const node = byId.get(nodeId);
-  if (!node) return null;
+  if (!node || visited.has(nodeId)) return null;
   if (isResult(node)) {
     return (
       <p className="text-sm text-foreground-neutral my-2">
         <strong>{node.title}.</strong> {node.why}
         {node.caveat ? ` ${node.caveat}` : ""}
       </p>
     );
   }
+  const nextVisited = new Set(visited);
+  nextVisited.add(nodeId);
   return (
     <div className="my-2">
       <p className="text-sm font-semibold text-foreground-neutral my-2">{node.question}</p>
       <ul className="list-none pl-4 my-0">
         {node.options.map((opt) => (
           <li key={opt.label} className="my-2 border-l border-stroke-neutral-strong pl-3">
             <span className="text-sm text-foreground-neutral-weak">{opt.label}:</span>
             {targetsOf(opt.next).map((childId) => (
-              <TextTree key={childId} byId={byId} nodeId={childId} />
+              <TextTree key={childId} byId={byId} nodeId={childId} visited={nextVisited} />
             ))}
           </li>
         ))}
       </ul>
     </div>
   );
 }

The same pattern (or a simpler depth limit) should be applied to TreeBranch for consistency.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/blog/src/components/DecisionTree.tsx` around lines 347 - 379, Add cycle
detection to the recursive DecisionTree renderers: both TextTree and TreeBranch
should track visited node IDs while traversing next targets and stop recursing
when a node is revisited. Update the recursive calls in TextTree (and mirror the
same guard in TreeBranch) to pass along a visited-set or equivalent depth guard
so future cyclic data cannot cause infinite recursion during SSR or in the
browser.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@apps/blog/src/components/DecisionTree.tsx`:
- Around line 347-379: Add cycle detection to the recursive DecisionTree
renderers: both TextTree and TreeBranch should track visited node IDs while
traversing next targets and stop recursing when a node is revisited. Update the
recursive calls in TextTree (and mirror the same guard in TreeBranch) to pass
along a visited-set or equivalent depth guard so future cyclic data cannot cause
infinite recursion during SSR or in the browser.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 702d50cf-d9e6-43f5-a5ea-5963ae17939a

📥 Commits

Reviewing files that changed from the base of the PR and between d062d35 and ce4d703.

📒 Files selected for processing (4)

• apps/blog/content/blog/serverless-postgres/index.mdx
• apps/blog/src/components/DecisionTree.tsx
• apps/blog/src/components/ServerlessPostgresChooser.tsx
• apps/blog/src/mdx-components.tsx

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Jul 10, 2026, 3:25 PM

[coderabbitai]

🧹 Nitpick comments (1)

apps/blog/content/blog/serverless-postgres/index.mdx (1)

107-114: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Consider hyphenating "open-source" as a compound adjective.

LanguageTool flags "open source project" on line 113 — when used as a compound adjective before a noun, "open-source" is the more standard form.

✏️ Optional style fix

- In March 2026, the Drizzle ORM team joined PlanetScale; Drizzle is stated to remain an independent open source project.
+ In March 2026, the Drizzle ORM team joined PlanetScale; Drizzle is stated to remain an independent open-source project.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/blog/content/blog/serverless-postgres/index.mdx` around lines 107 - 114,
Hyphenate “open source” when it directly modifies a noun in the PlanetScale
section: update the phrase “open source project” in the paragraph mentioning
Drizzle to “open-source project.”

Source: Linters/SAST tools

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@apps/blog/content/blog/serverless-postgres/index.mdx`:
- Around line 107-114: Hyphenate “open source” when it directly modifies a noun
in the PlanetScale section: update the phrase “open source project” in the
paragraph mentioning Drizzle to “open-source project.”

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 95bb9d59-ea5b-4b6d-8c47-29af13af6b0b

📥 Commits

Reviewing files that changed from the base of the PR and between ce4d703 and 5637d80.

⛔ Files ignored due to path filters (2)

• apps/blog/public/serverless-postgres/imgs/hero.svg is excluded by !**/*.svg
• apps/blog/public/serverless-postgres/imgs/meta.png is excluded by !**/*.png

📒 Files selected for processing (1)

• apps/blog/content/blog/serverless-postgres/index.mdx