[gregory-boch-prisma]

The Neon alternatives post compares Prisma Postgres + Prisma Compute, Railway, Render and Supabase for hosting an app and Postgres in one place. Supabase now has Compute, a private alpha that runs backend services including Node, so the post's Supabase hosting lines needed its status.

Changes

• Situation table, row 1: "Supabase hosts no frontend (its Compute private alpha runs backend services)", the wording already on the app-hosting post (blog, docs: update Railway and Supabase facts #8521).
• Supabase entry, "What it does": adds that Supabase Compute, which runs backend services, is a private alpha (us-west-2 only, not for production).
• Supabase entry, "Trade-offs": a Node.js server that serves production needs another host, because Edge Functions are not Node.js or Bun and Supabase Compute is a private alpha (us-west-2 only, not for production).
• FAQ "Does Supabase host my app as well as the database?": the same qualifier, with the check date.
• Sources list links supabase.com/compute; "How we compared" lists the 2026-10-19 check.
• updatedAt 2026-10-14 -> 2026-10-19 and one update-history line. Title, metaTitle, H1, metaDescription, excerpt and first paragraph are not edited.

Sources checked 2026-10-19

• https://supabase.com/compute.md: "Compute is in Private Alpha behind a waitlist", and Node is among the languages it runs.
• https://supabase.com/compute: "Only projects created in us-west-2 can access Compute during private alpha"; the waitlist terms say the alpha "should not be used to serve production workloads or your own end customers".
• https://supabase.com/docs/guides/platform/custom-domains.md: custom domains are not intended for hosting frontend applications through Edge Functions (same as on 2026-10-16).

Checks

• Do-not-claim lint on the diff and commit messages: 2 hits, both on the existing Supabase preview-database sentence and its docs link (lines 85 and 153), already on main and picked up only because those lines were edited. No claim about Prisma.
• No non-ASCII characters in added lines or commit messages.
• Content-only change to one MDX file; table cell counts are the same.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the article’s comparison of Neon and Supabase to clarify that Supabase Compute is in private alpha, limited to us-west-2, and not intended for production.
  • Clarified that Supabase Edge Functions are separate from Compute, and production frontend and Node.js server hosting still require another provider.
  • Updated the article date, comparison sources, and change history.

[vercel]

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

Project	Deployment	Actions	Updated
blog	Ready	Preview	Oct 19, 2026 11:15am UTC
docs	Ready	Preview	Oct 19, 2026 11:15am UTC
eclipse	Ready	Preview	Oct 19, 2026 11:15am UTC
site	Ready	Preview	Oct 19, 2026 11:15am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
handbook	Skipped		Oct 19, 2026 11:15am UTC

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: 4fc58054-31bd-45d7-b1e0-dab67a26befb

📥 Commits

Reviewing files that changed from the base of the PR and between 50c9fca and 30fb057.

📒 Files selected for processing: 1

• apps/blog/content/blog/neon-vs-prisma-postgres-app-hosting-in-one-place/index.mdx

Included review availability: This review used your included allowance. Your plan provides up to 5 included reviews per hour; 3 remain after this review.

Walkthrough

The article now states that Supabase Compute is a private alpha limited to us-west-2 and is not available for production. The comparison, FAQ, source list, and update history reflect these details.

Changes

Supabase Compute article update

Layer / File(s)	Summary
Update Supabase Compute details apps/blog/content/blog/neon-vs-prisma-postgres-app-hosting-in-one-place/index.mdx	The article updates its comparison and FAQ to distinguish Supabase Compute from Edge Functions and state that production frontend and Node.js hosting require another host. It adds a dated source check and update-history entry, and advances the article’s update date.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: vanrensbird

Merge Risk: ⚪ Minimal · up to 30fb0

The post’s Compute availability caveats match Supabase’s private-alpha terms, so no material merge risk remains.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: documenting the Supabase Compute status in the Neon alternatives blog post.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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