Add Prisma vs Vercel platform comparison blog post

[sneub]

Adds a Prisma vs Vercel comparison for TypeScript teams choosing an application platform, covering Prisma ORM 8, Postgres, Compute, and Composer alongside Vercel's hosting and service model.

The article includes explicit “choose when” guidance, explains both platforms' per-branch application previews, and distinguishes Prisma's separate preview databases and schema migration graph from copy-on-write database branches. It follows the Prisma blog's voice with an answer-first structure and links to supporting product documentation.

Validation: MDX generation passed; the blog loader resolves the article and its processed content; staged whitespace checks passed.

Summary by CodeRabbit

• Documentation
  • Added a blog post comparing Prisma and Vercel for hosting full-stack TypeScript applications.
  • Covers application hosting, managed Postgres, typed data access, service composition, previews, preview databases, and runtime billing.
  • Explains branching workflows, schema migration handling, service contracts, typed dependencies, and compatibility between Prisma tools and Vercel-hosted applications.
  • Warns that preview environments must use preview-scoped database connections to avoid writing to production.

[vercel]

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

Project	Deployment	Actions	Updated
blog	Ready	Preview	Sep 16, 2026 1:00pm UTC
docs	Ready	Preview	Sep 16, 2026 1:00pm UTC
eclipse	Ready	Preview	Sep 16, 2026 1:00pm UTC
site	Ready	Preview	Sep 16, 2026 1:00pm UTC

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: b92d8058-e3d8-47d4-8fa9-1bf89c5a147b

📥 Commits

Reviewing files that changed from the base of the PR and between 39cbe3f and a70ca11.

📒 Files selected for processing (1)

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

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

Walkthrough

A new MDX blog post compares Prisma and Vercel for full-stack TypeScript applications. It covers platform components, selection criteria, service composition, previews, databases, runtime behavior, billing, and using Prisma with Vercel.

Changes

Platform comparison article

Layer / File(s)	Summary
Prisma and Vercel platform comparison apps/blog/content/blog/prisma-vs-vercel/index.mdx	Adds a blog post covering platform components, selection criteria, comparison criteria, Composer contracts, Vercel Services and bindings, branch previews, preview databases, runtime details, billing, and Prisma usage within Vercel-hosted applications.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to a70ca

The new comparison article and its documented preview-database warning are supported by the supplied repository context, with no unresolved merge risk identified.

🚥 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 clearly and concisely describes the main change: adding a blog post that compares Prisma and Vercel as platforms.
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)

• Create PR with unit tests
• Commit unit tests in branch codex/prisma-vs-vercel-blog

---

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

[prisma-robot]

Reviewed head 39cbe3f.

Ran the blog gates locally (test 41/41, types:check, lint:links all clean once @prisma/eclipse is built). All ten prisma.io/docs links resolve to pages in apps/docs; all twelve external links return 200. Checked the Prisma claims against the Compute, Composer, and migration-graph docs, and the Vercel claims (Services/Python, bindings, Pro credit, Fluid compute meters, Neon copy-on-write previews) against the linked pages. Frontmatter validates against source.config.ts, author exists, first product mentions are linked, no em dashes or hype words.

One finding, fixed in a70ca11:

• Preview database isolation was overstated. The post says each branch tests "in isolation from production" and promises "a preview with an isolated database", but the Compute branching doc carves out the case where a database reached through DATABASE_URL is only as isolated as that variable's value. Added one sentence to the "How do you deploy and test changes?" section stating the caveat and linking to the environment variables doc, matching what the Netlify comparison already says. lint:links still passes.

Re-reviewing the new head next.

— reviewer

[prisma-robot]

Review clean at a70ca11

Fresh read of the head, including my own fix from the previous round. Branch is current with main.

What the PR does: adds one blog post, apps/blog/content/blog/prisma-vs-vercel/index.mdx, comparing Prisma (ORM 8, Postgres, Compute, Composer) with Vercel for TypeScript teams: choose-when guidance, a comparison table, sections on defining the application, previews and preview databases, runtime and billing, and using Prisma on Vercel. Same shape and frontmatter as the Netlify comparison merged in #8286.

What I checked this round:

• Gates: pnpm --filter blog run check (format, lint, tests 41/41, lint:links 0 errors) and types:check pass with @prisma/eclipse built.
• Frontmatter validates against source.config.ts; tags are from the enum; author exists in author-bios.ts.
• All 11 prisma.io/docs links resolve to pages in apps/docs; all 12 external links return 200.
• Prisma claims against the docs: Compute runs on Bun, one region per service, no WebSocket servers, the four pricing meters and no separate charge for deploys or preview branches, deploy-on-push per branch, DATABASE_URL isolation caveat and per-branch env values, Composer cron/storage/streams modules, RPC-over-HTTP contracts, authenticated service calls, build-then-deploy, the two-service getting-started guide, and the ORM 8 JSON contract per ARCHITECTURE.md.
• Vercel claims against the linked pages: Services polyglot (Next.js plus Python), bindings, Pro plan monthly credit and per-deploying-seat billing, Fluid compute billing Active CPU and Provisioned Memory separately, Neon copy-on-write branch per preview.
• Voice: no em dashes, no hype words, first product mentions linked.

Risk: low. Content-only change, one new file, nothing else touched, gates green, and every product claim traces to a doc or the vendor's own page. If it merged now I would be comfortable.

Note, not this PR's problem: oxfmt wants to reformat apps/blog/scripts/lint.ts on main, so running the blog check gate dirties the tree. The open chore/update-oxlint-oxfmt branch looks like the right place for that, so I did not propose a separate task.

— reviewer