Repository navigation
Add /compare/vercel (Prisma vs Vercel hosting) - #8538
vanrensbird wants to merge 1 commit into
Conversation
Draft /compare/vercel for Prisma Compute, Prisma Postgres, and Prisma ORM against Vercel hosting. Reuses the existing compare chrome. Does not replace /compare/vercel-neon-drizzle. Excludes the unreleased URL from lychee. Co-authored-by: rensburg <rensburg@prisma.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Comment |
ankur-arch
left a comment
ankur-arch
left a comment
There was a problem hiding this comment.
Reviewed the draft properly so it is ready when you un-draft. Pricing on both sides checks out against the live Vercel pricing, Pro plan and spend-management pages and against prisma.io/pricing and the Compute pricing doc, and it agrees with /compare/vercel-neon-drizzle. Tone toward Vercel is fair. Structure, createPageMetadata, OG card, JSON-LD, .md and .json routes, the next.config registry and the sitemap are all wired like the sibling pages. oxlint and oxfmt are clean and the site suite passes with the three new tests. No em dashes.
Four things to fix before un-drafting, inline below: the cron claim, the co-location wording, the missing single-region trade-off, and the duplicate preview rows.
Quick polish, your call: the "no first-party ORM" cell cites the generic docs index, which cannot support a negative claim; vercel.com/docs/frameworks/nextjs 301s to /docs/frameworks/full-stack/nextjs; "free to use, and free and open source" says free twice; "Both host TypeScript apps." opens the hero, the table intro and the meta description; the meta description is 238 characters. The seven-level ternary in page-ai-actions.tsx would be a Record lookup keyed by slug, and comparison-metadata.ts's JSON allowlist can go now that every slug has a .json route. The shared INLINE/BODY/LIST/STEPS constants are byte-identical across five compare pages and deserve a hoist in a follow-up.
Not merging while it is a draft.
| "You want a mature frontend CDN, Image Optimization, and the Vercel hosting ecosystem. Prisma Compute hosts TypeScript HTTP services next to Prisma Postgres. It is not a general CDN platform.", | ||
| "You want hosting and the database managed from the Vercel dashboard. Prisma Postgres works with an app on Vercel, but it is managed from the Prisma Console.", | ||
| "You want to pick the database and ORM separately and connect them yourself. See [Prisma vs Vercel + Neon + Drizzle](/compare/vercel-neon-drizzle) when that stack is the alternative.", | ||
| "You need WebSocket servers or a built-in cron scheduler. Prisma Compute does not support those today. See [Compute limitations](/docs/compute/limitations).", |
There was a problem hiding this comment.
Listing cron as unsupported is wrong. The limitations doc says scheduled jobs come from Composer's cron building block or an external scheduler. Say "Compute has no built-in cron scheduler; scheduled jobs come from Composer's cron building block" here and at line 124.
| feature: "App and database placement", | ||
| vercel: "Database placement depends on the Marketplace provider and the deployment region.", | ||
| prisma: | ||
| "Prisma Compute hosts the app next to Prisma Postgres in the same project, so the app and database do not need a cross-vendor network hop.", |
There was a problem hiding this comment.
"Hosts the app next to Prisma Postgres" reads as co-location, but each service runs in one region and the docs tell users to create the service in the database's region. Either qualify it ("when the service is created in the database's region") or keep the claim to same project, same vendor. Same wording at lines 24, 142 and 155 and in _sections.tsx line 139.
|
|
||
| export const WRONG_CHOICE = [ | ||
| "You want a mature frontend CDN, Image Optimization, and the Vercel hosting ecosystem. Prisma Compute hosts TypeScript HTTP services next to Prisma Postgres. It is not a general CDN platform.", | ||
| "You want hosting and the database managed from the Vercel dashboard. Prisma Postgres works with an app on Vercel, but it is managed from the Prisma Console.", |
There was a problem hiding this comment.
The Compute FAQ lists "an app that needs more than one region" next to WebSockets and a global CDN as cases where Vercel with Prisma Postgres fits better. Add single-region here so the page matches the docs' own trade-off list.
| prisma: "https://www.prisma.io/docs/compute", | ||
| }, | ||
| }, | ||
| { |
There was a problem hiding this comment.
"Preview environments" and "Preview deployments" are near duplicates; the Vercel cell says "Preview deployments for every Git push" in both. Merge them into one Environments row like the vercel-neon-drizzle page.
This branch was successfully deployed
3 participants
Draft only. Do not merge.
Adds
/compare/vercel: Prisma Compute, Prisma Postgres, and Prisma ORM compared with Vercel application hosting. Same chrome as the Neon and Vercel + Neon + Drizzle pages. Does not replace/compare/vercel-neon-drizzle.Hero CTA is Get started with Prisma. The closing first check on this slug only is Get started with Prisma and start building in minutes. Other compare pages still use the create-a-database line.
Author is Martin Janse van Rensburg. Choose is a table. JSON-LD,
.mdexport, Open-with-AI, directory listing, and tests are wired. Lychee excludes the unreleased URL until it is live.Checked Prisma Free and Vercel Hobby/Pro on 19 October 2026. Live Free numbers include 1M Compute requests, 360 GB-hours, 4 vCPU-hours, 10 GB outbound bandwidth, 200,000 Postgres operations, 2 GB storage, and 50 databases. Vercel Hobby is $0 for personal use. Pro is $20 a month plus usage, with a $20 monthly credit.