[gregory-boch-prisma]

"5 ways to host PostgreSQL databases" compares local, self-managed, cloud-provider and third-party PostgreSQL hosting, with a "When to choose Prisma Postgres" list and an FAQ.

Changes

• "When to choose Prisma Postgres", the backups case: it read "You want backups handled automatically rather than scripting and testing your own" with no plan scope, in a list whose first case now describes the Free plan. Automatic backups are on paid plans only, so the line now adds: daily snapshots on days the database has activity on Starter, Pro and Business, kept 7 days (30 on Business); the Free plan has no backups, and pg_dump against the direct connection string keeps your own copy on any plan with available usage. This matches the comparison table's "Paid plans" Backups cell and the FAQ "How are backups handled?".
• Same list, the "zero infrastructure" case: "there are no instances, networks, or backups to configure first" now reads "there are no instances or networks to configure first", and "provisioned instantly" reads "provisioned in seconds". Backups are not something a Free database has, and the backups case covers paid plans.
• The comparison table already says "Paid plans" for Prisma Postgres backups; no change there.
• No lastUpdated bump, per the repo's AGENTS.md ("Don't bump dates"), matching Describe Prisma Postgres in the PostgreSQL hosting guide with documented facts #527, Link the Postgres import docs and describe Prisma Postgres client-neutrally #531 and 5 ways to host PostgreSQL: laptop database case and Free plan limits #532. The page has no update-history list.

Sources checked 2026-10-24

• https://www.prisma.io/pricing.md: the Data table's "Backups" row has a dash (none) for Free, "Daily, 7-day retention" for Starter and Pro, and "Daily, 30-day retention" for Business.
• https://www.prisma.io/docs/postgres/database/backups.md: "On Starter, Pro, and Business plans, Prisma Postgres automatically creates snapshots of your database"; "Snapshots are created daily, but only on days when the database has activity."
• https://www.prisma.io/postgres.md: "Starter and Pro keep them for 7 days and Business keeps them for 30; the Free plan has none." and "To keep your own copy, run pg_dump against the direct connection string, on any plan with available usage."

Checks

• git diff --check: clean.
• prettier --check (3.9.9, repo config) on the changed file: pass.
• npm test, npm run typecheck and the full build not run locally; the change is two prose lines with no links or components, and CI covers the build and link check.
• Claims check on the diff, this body and the commit message: 0 matches.

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated
dataguide	Ready	Preview	Oct 24, 2026 9:56pm UTC

[prisma-gizmo]

✅ Gizmo reviewed 6146f44 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

This PR corrects the "When to choose Prisma Postgres" section of content/04-postgresql/03-5-ways-to-host-postgresql.mdx so its backup claims match Prisma Postgres's actual plan gating: automatic backups exist only on paid plans, not on Free. The backups bullet now scopes the promise: daily snapshots on days with activity, kept 7 days (30 on Business) on Starter/Pro/Business, no backups on Free, and pg_dump against the direct connection string as the reader-run fallback on any plan with available usage. The "zero infrastructure" bullet drops "or backups" from its list of things there is nothing to configure, and softens "provisioned instantly" to "provisioned in seconds" (line 293). The new wording aligns the list with the article's own comparison table, whose Prisma Postgres row already says "Paid plans" for Backups and "Seconds" for setup time, and with the FAQ's "How are backups handled?" answer on the same page. The article is a marketing-adjacent comparison page; per the repo's AGENTS.md rules ("never fabricate", "don't bump dates"), the PR cites vendor pricing and backup docs as sources and leaves lastUpdated alone, both of which match repo convention and the sibling PRs referenced in the description. The change is two prose lines in an MDX article — no links, components, or commands added, so nothing new to test against a throwaway environment, and no internal-link surface for the build's link checker to trip over.

[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: 🟡 1 minor · trace

[prisma-gizmo]

New findings: none · trace

Still open from previous reviews: 🟡 1 minor

[prisma-gizmo]

New findings: none · trace

Still open from previous reviews: 🟡 1 minor

[prisma-gizmo]

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

[gregory-boch-prisma]

@prisma-gizmo review