[gregory-boch-prisma]

Adds an FAQ entry on hosting the app and Postgres in one place to 5 ways to host PostgreSQL databases, and corrects the article's answer on whether managed PostgreSQL is production-ready.

Changes

content/04-postgresql/03-5-ways-to-host-postgresql.mdx:

• New FAQ entry "Can I host the app and Postgres in one place?", after "Can I develop locally and deploy to a hosted database?". The article names Prisma Postgres throughout but never said where the app runs. The entry:
  • says some platforms host the app and a managed PostgreSQL database in the same account;
  • names Prisma Compute with Prisma Postgres: Compute hosts TypeScript apps built for Node.js, Bun or Next.js, runs them on Bun, and uses the same six regions as Prisma Postgres. Each service runs in one region chosen when you create it, so the app goes in the database's region;
  • says any PostgreSQL client works and Prisma ORM is optional;
  • states one limit: Compute does not run WebSocket servers today, with a link to the Compute limitations page;
  • links Neon alternatives with app hosting and Postgres in one place (2026) and App hosting platforms with managed Postgres compared (2026). The Compute link uses the page's existing utm_source=dataguide pattern.
• The entry is plain prose, not PrismaOutlinks or PostgresCallout, because the Markdown exporter drops those two components (mdx-to-markdown.mjs, DROPPED) and the answer needs to be in /dataguide/postgresql/5-ways-to-host-postgresql.md.
• "Is managed PostgreSQL production-ready?": the answer said the provider handles high availability, backups and scaling for any managed host, Prisma Postgres included. It now says the provider runs the server, its backups and its upgrades, and lists high availability and failover, backup retention and point-in-time recovery among the guarantees to confirm before committing. Nothing on prisma.io states high availability or failover for Prisma Postgres.

Sources checked 2026-10-07

• /compute and /docs/compute: TypeScript apps for Node.js, Bun or Next.js next to Prisma Postgres; any Postgres client works, Prisma ORM optional.
• /docs/compute/limitations: one region per service from us-east-1, us-west-1, eu-west-3, eu-central-1, ap-northeast-1, ap-southeast-1; no multi-region deployments; WebSocket servers not supported.
• /docs/compute/faq: Bun runtime; keep the app and its database in the same region.
• /docs/postgres/faq: the same six regions for Prisma Postgres.
• Both linked blog URLs return 200, and the Neon post's link text matches its published title.

Checks

• Claims check: the new entry adds no competitor facts, no pricing, and no claims about caching, point-in-time recovery, branching, replicas, failover, autoscaling, multi-region, Docker, cron or preview data.
• On commit 81d4ecc: npm test 70/70; npm run typecheck; ADD_PREFIX=true npm run build, including the link check (19,817 internal links on 143 pages resolve); the new entry appears in the generated postgresql/5-ways-to-host-postgresql.md; Prettier clean (pre-commit hook). All 13 CI checks passed. scripts/deployment-smoke.mjs against the preview https://dataguide-git-docs-host-app-and-postgres-1007-prisma.vercel.app exits 0 for content revision 94509e3b47c167972478919818fc919e0326ab50b4670fd914334340243d559b and commit 81d4ecc1f2d3559f3c8b1d4e73efd89a8eeeec3d (preview, canonical root https://www.prisma.io/dataguide), and the preview's /postgresql/5-ways-to-host-postgresql.md contains the new entry.
• On the final commit 1444bb4, which changed the production-ready answer: all 12 check runs pass (test and build on Node.js 22.18.0 and 24, the database tutorials, CodeQL and the Gizmo review).
• The prose checkers from prisma/web's docs-reader-review skill (check-ai-signs.sh, check-plain.sh, check-staccato.py) are clean on the added text.
• lastUpdated is not set. The page has none, and CONTRIBUTING.md reserves it for articles whose examples were re-tested. This change adds no commands or examples. In content-verification.json the article stays unreviewed.

Not changed, worth a follow-up

Some existing Prisma Postgres wording on this page goes beyond what the Prisma Postgres docs state, and this PR leaves it alone to keep the change small: the comparison table's "Scaling: Automatic" and "Serverless/edge apps" cells. The Prisma Postgres docs document scale-to-zero only. These cells are not simply unsourced, though: /postgres says "Autoscaling that handles spikes without capacity planning", the pricing page lists "Auto-scaling" under the managed connection pool, and /docs/postgres lists edge runtime support through the serverless driver. The fix is a decision for the Prisma Postgres owner, because the product pages and the docs disagree. The Free plan has no backups, which the "How are backups handled?" answer does not say.

🤖 Generated with Claude Code

[prisma-gizmo]

✅ Gizmo reviewed 1444bb4 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

Change walkthrough

This PR extends the PostgreSQL hosting guide with a new FAQ entry and, in the latest commit, rewords an existing answer to remove unsupported claims.

New FAQ entry. content/04-postgresql/03-5-ways-to-host-postgresql.mdx gains "Can I host the app and Postgres in one place?", placed after the local-development/deployment question. It answers directly, names Prisma Compute with Prisma Postgres (frameworks, Bun runtime, the six shared regions, one region per service), states that any PostgreSQL client works with Prisma ORM optional, and discloses the WebSocket limitation with a link to the Compute docs. It closes with links to the two comparison blog posts. The entry is deliberately plain prose rather than PrismaOutlinks or PostgresCallout, so the Markdown exporter keeps it in the /dataguide/postgresql/5-ways-to-host-postgresql.md output — a sensible constraint given the page's retrieval-set motivation. The Compute product link follows the page's existing utm_source=dataguide pattern.

Incremental delta (this pass). Since the last reviewed commit, the "Is managed PostgreSQL production-ready?" answer at content/04-postgresql/03-5-ways-to-host-postgresql.mdx:340 was reworded from "the provider handling high availability, backups, and scaling" to "the provider running the server, its backups and its upgrades", with high availability and failover and point-in-time recovery moved into the list of specifics readers should confirm per provider. This is the follow-up the PR description originally deferred: the old sentence asserted as universal what the Prisma Postgres docs don't claim (high availability, failover), while the new wording is verifiable and consistent with the neighboring "How are backups handled?" answer, which also tells readers to confirm retention options. It aligns with AGENTS.md's label-uncertainty rule. Note that the PR description's "Not changed, worth a follow-up" section is now stale — it describes the pre-reword text as still present.

Verification per the PR description. npm test (70/70), typecheck, and ADD_PREFIX=true npm run build with the internal-link check (19,817 links on 143 pages) pass on the head commit; CI is green and the preview's markdown export contains the new entry. No lastUpdated bump, matching the CONTRIBUTING.md rule for articles without re-tested commands.

[vercel]

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

Project	Deployment	Actions	Updated
dataguide	Ready	Preview	Oct 7, 2026 12:13pm UTC

[github-actions]

This PR changes the following pages (Vercel Preview Deploy links):

• /dataguide/postgresql/5-ways-to-host-postgresql (currently)

(Note that links will only be valid after Vercel preview deploy succeeded)

[prisma-gizmo]

New findings: none · trace

[prisma-gizmo]

No critical or major Gizmo finding is open and the head commit has been reviewed. Approving.

[prisma-gizmo]

New findings: none · trace

[prisma-gizmo]

No critical or major Gizmo finding is open and the head commit has been reviewed. Approving.

[prisma-gizmo]

New findings: none · trace

[prisma-gizmo]

No critical or major Gizmo finding is open and the head commit has been reviewed. Approving.