blog: Netlify alternatives: answer first with Prisma Compute and Prisma Postgres, limits in one line each

[gregory-boch-prisma]

Why

This page is our answer to the tracked prompt "What are good Netlify alternatives for a full-stack TypeScript app with a Postgres database?". It gets read, but it does not get Prisma recommended. From 2026-10-01 to 2026-10-05 the four tracked engines gave 20 answers. Prisma Compute was named in 0 of them, Prisma Postgres in 3, and this page was cited in 6. Across the 76 answers in the diagnosis, Compute is named as a host 0 times, and 37 answers mention Prisma only as the ORM. ChatGPT search reads the page in every answer (ChatGPT-User fetched it 21 times on 2026-10-02). It then ranks hosts on the criteria the page puts first: the 60 s limit, WebSockets and background jobs from "Why teams leave Netlify". The page's own FAQ on this exact question opened with "The answer depends on which part of Netlify stopped fitting" and named no first pick. This PR is PR A: sentence-level edits that state the pick. The structural rewrite is PR B.

What changed

All edits are in apps/blog/content/blog/prisma-vs-netlify/index.mdx.

• Opening: names the first pick, "Prisma Compute with Prisma Postgres: the app and the database on one plan, deployed on push, no Docker". Sources: pricing.ts plans; docs/compute/deploy-on-push; docs/compute/faq.mdx:38 (no Docker images).
• Alternatives intro: states the first pick, then says the other profiles cover when each option is the better choice. It replaces "none of them is a better Netlify".
• Prisma profile: "Best when" now matches the pick (a TypeScript app and its Postgres database on one plan from one vendor). The runtime sentence is copied from docs/compute/faq.mdx:55 ("TypeScript services on Bun: Node.js, Bun or Next.js apps"). The one-region and WebSockets sentence moved out of the profile. Those limits stay in the opening, in Runtime limits and in the "Is Prisma a replacement" FAQ.
• Bun caveat in the routing list: "If your code depends on Node.js behavior Bun does not provide, that is a reason not to choose Compute." Source: docs/compute/faq.mdx:38.
• Vercel profile: Marketplace databases listed as Prisma Postgres, Neon, or Supabase. Source: Vercel's Marketplace storage docs, fetched 2026-10-06.
• FAQ "What are the best Netlify alternatives for a TypeScript app with Postgres?": rewritten in place with Prisma first. Free is 200,000 operations a month and 500 MB with no usage billing. Starter is a $10 base with 1 million operations a month and 10 GB, plus metered compute. Source: apps/site/src/lib/markdown/pricing.ts. Each other option gets a one-line route: Railway or Render for a WebSocket server or a Docker image, Fly.io for many regions, and Vercel for a Next.js frontend with a Marketplace database. The answer keeps the note that Render's Postgres is managed and Railway's own docs call its Postgres template unmanaged. Sources, all fetched 2026-10-06: docs.railway.com (specs and limits, services, databases), render.com/docs (websocket, docker, native runtimes, databases), fly.io/docs/reference/regions, and vercel.com/docs.
• Frontmatter updatedAt is 2026-10-06. The update note is now labeled "September and October 2026". It corrects the title-change date to 2026-10-05 (site, docs, blog: one positioning sentence, Compute GA notes, a /postgres FAQ and Compare Prisma links #8360) and drops "the body is unchanged", because blog: stop repeating pre-release labels for Composer, ORM 8, the deploy action and Compute #8344 changed body text that day. It also records the 2026-10-06 changes.

What did not change

• Title, H1, metaTitle, metaDescription, excerpt and tags are unchanged. There is no compute tag, because the tag enum in apps/blog/source.config.ts has no such value. The URL is unchanged.
• The post makes no claim that Prisma is closest to Netlify. It claims no edge, multi-region, WebSockets, long-running workers, point-in-time recovery or flat pricing for Prisma. Starter is a $10 base plus metered compute.
• No sentence about cron on Compute.
• Compute is not called beta. Composer gets no maturity label.
• The Node.js caveat stays. The runtime wording is the docs FAQ sentence, not "Compute runs Node.js, Bun and Next.js services".
• No Render price was added. The Render workspace price in docs/compute/faq.mdx is still unverified.
• The "Using Prisma ORM and Prisma Postgres on Netlify" section is not touched or expanded.
• Left for PR B, because these are structural changes:
  • "Why teams leave Netlify" is still the first H2.
  • The Bun, one-region and 60 s limits still appear in several sections instead of one line each in one section.
  • Three places still narrow the pick: the routing list ("several TypeScript services sharing Postgres"), the ORM 7 line under "Choose Prisma if", and the closing "Which one to pick".

Expected effect

This is a mention play, not a first pick. ChatGPT search fetches the live page when it answers, so the edit should show within about a week of merge. The expected result is Prisma Compute named in the table or shortlist of some weekly GPT answers. Today that count is 0 of 5. A first pick is not expected. No vendor is an unhedged first pick in any of the 20 answers, and the pick is decided on persistent servers, workers, Docker and WebSockets, which Compute does not offer. No change is expected on Gemini, Claude or Grok. Measure with per-answer "Compute named as host" counts, not PromptWatch visibility.

If this merges after 2026-10-06, set updatedAt and the "On 2026-10-06" date in the update note to the merge date. The sitemap lastmod and the JSON-LD dateModified come from updatedAt.

Checks

• check-ai-signs.sh, check-plain.sh and check-staccato.py are clean on the whole file.
• Two review passes (facts, and reader and scope) found no blockers. Their sentence-level minor points are applied in the second commit. The structural ones are listed above for PR B.

Reviewers needed

Shane Neubauer (author of record) and Ankur Datta (rewrote the body on Sep 17). No human has reviewed this post since then.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the Prisma hosting article with refreshed recommendations for full-stack TypeScript and Prisma Postgres apps.
  • Expanded the alternatives guidance to cover supported runtimes and frameworks, platform limitations, plan allowances and pricing, and options for WebSockets, Docker, multi-region deployments, and Next.js frontends.

[vercel]

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

Project	Deployment	Actions	Updated
blog	Ready	Preview	Oct 6, 2026 9:16am UTC
docs	Ready	Preview	Oct 6, 2026 9:16am UTC
eclipse	Ready	Preview	Oct 6, 2026 9:16am UTC
site	Ready	Preview	Oct 6, 2026 9:16am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
handbook	Skipped		Oct 6, 2026 9:16am 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: 20614540-31b9-4b47-9c7f-e03d3309d316

📥 Commits

Reviewing files that changed from the base of the PR and between 737d842 and bb2525c.

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-vs-netlify/index.mdx

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

---

Walkthrough

The article now recommends Prisma Compute with Prisma Postgres for full-stack TypeScript apps with Postgres. It also updates Bun guidance, platform comparisons, and FAQ details, including plan allowances and alternative platforms.

Changes

Article recommendation update

Layer / File(s)	Summary
Recommendation and runtime guidance apps/blog/content/blog/prisma-vs-netlify/index.mdx	The opening now recommends Prisma Compute with Prisma Postgres for full-stack TypeScript apps with Postgres. The Bun guidance and update note are revised.
Alternatives and FAQ apps/blog/content/blog/prisma-vs-netlify/index.mdx	The alternatives section and FAQ name Prisma Compute with Prisma Postgres as the first pick, specify Free and Starter allowances and pricing, and describe when to consider Railway, Render, Fly.io, or Vercel.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to bb252

The runtime guidance matches Compute’s documented deployment model, and no actionable merge-blocking risk is established. The update is ready for normal checks.

🚥 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 identifies the main change: recommending Prisma Compute with Prisma Postgres first and summarizing plan limits. It is specific and relevant, though somewhat long.
Docstring Coverage	✅ Passed	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	✅ 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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

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

---

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