[gregory-boch-prisma]

This guide compares ways to run PostgreSQL, from self-managed servers to fully managed services.

Changes

• The provider list under "Databases managed by cloud providers" now starts with Prisma Postgres. It was between Neon and Render before. The "Third-party offerings" section already describes Prisma Postgres before the other providers.
• The sentence before the list now states the affiliation and the order: "Prisma, the publisher of this guide, makes Prisma Postgres, and the other providers are listed alphabetically." Before, the sentence gave no order and the list did not say whose service Prisma Postgres is.
• The same sentence now opens with "The following providers" instead of "The following cloud providers". The list already included hosted PostgreSQL services such as Heroku, Neon, Render and Supabase next to the cloud platforms, and the "Third party managed databases" section describes Prisma Postgres as an alternative to buying from a cloud provider. The headings stay as they are, so no anchor changes.
• The other nine providers keep their alphabetical order. No name or link changes.

Sources checked 2026-11-06

• https://www.prisma.io/dataguide/postgresql/5-ways-to-host-postgresql.md: the live list matches main (Amazon AWS, DigitalOcean, Google Cloud, Heroku, IBM, Microsoft Azure, Neon, Prisma Postgres, Render, Supabase), and the sentence before it reads "The following cloud providers offer managed PostgreSQL databases that you can purchase, configure, and scale as your needs require:".
• The same page, "Third party managed databases": "An alternative to purchasing databases directly from your cloud provider, you can instead choose to manage your databases through a third-party provider like Prisma Postgres."

Checks

• One list item moved and one sentence changed: 2 insertions, 2 deletions in content/04-postgresql/03-5-ways-to-host-postgresql.mdx.
• The nine providers after Prisma Postgres are in alphabetical order (checked with sort -c -f).
• No lastUpdated added: the article has none, and CONTRIBUTING.md keeps it for articles whose content was substantively reviewed and whose examples were re-tested.
• Not built locally: the change adds no link or anchor. The Vercel preview and CI build run on this PR.
• Claims check: the new sentence names the publisher and the list order, with no product claim.

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated
dataguide	Ready	Preview	Nov 6, 2026 1:07pm UTC

[prisma-gizmo]

✅ Gizmo reviewed 7e5e593 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

The change updates the intro sentence above the managed-provider list in content/04-postgresql/03-5-ways-to-host-postgresql.mdx:175 so that it discloses Prisma's affiliation with Prisma Postgres and states the list's ordering rule, following the earlier pass that moved Prisma Postgres to the top of that list.

What changed since the last reviewed commit. The only delta is the sentence itself: it now reads "The following providers offer managed PostgreSQL databases… Prisma, the publisher of this guide, makes Prisma Postgres, and the other providers are listed alphabetically:" instead of the old "The following cloud providers offer…". The list items themselves were settled in the previous commit, and the stated ordering rule matches the file: the nine providers after Prisma Postgres (Amazon AWS, DigitalOcean, Google Cloud, Heroku, IBM, Microsoft Azure, Neon, Render, Supabase) are in alphabetical order.

Dropping "cloud". The list has mixed cloud platforms (AWS, Google Cloud, IBM, Azure) with hosted PostgreSQL services (Heroku, Neon, Render, Supabase) since before this PR, so "providers" is more accurate than "cloud providers". The #### Cloud providers heading and the parent ### Databases managed by cloud providers heading were deliberately left unchanged to preserve existing anchors, and no internal links target this section's anchors.

How it fits the codebase. The disclosure follows the transparency the article already practices elsewhere: the "Third party managed databases" section, the comparison table, the "When to choose Prisma Postgres" section, and the FAQ all name Prisma Postgres explicitly, while outbound product links there carry utm_source=dataguide attribution and this plain list item does not. The change adds no links, dates, or unverifiable product claims, and no SQL or commands were touched, so no content-verification evidence regeneration is required.

[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)

[gregory-boch-prisma]

@prisma-gizmo review

[prisma-gizmo]

New findings: 🟠 1 major · trace

[gregory-boch-prisma]

@prisma-gizmo review

[prisma-gizmo]

New findings: none · trace

Still open from previous reviews: 🟠 1 major

[gregory-boch-prisma]

@prisma-gizmo review

[gregory-boch-prisma]

@prisma-gizmo review

[prisma-gizmo]

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

[gregory-boch-prisma]

@prisma-gizmo review