Add Accelerate offboarding guide and retirement navigation

[luanvdw]

Overview

Documents the supported path for existing Accelerate customers who want to keep their database, and makes both offboarding paths visible ahead of the December 1, 2026 retirement.

Changes

• Adds accelerate/keep-your-database.mdx, a version-aware guide for removing the Accelerate connection, client extension, caching APIs, and legacy generation flags without moving data.
• Adds a Migrating off Accelerate sidebar section with direct links to the existing Prisma Postgres migration guide and the new keep-your-database guide.
• Adds retirement notices to the Accelerate landing and getting-started pages, and clarifies that Prisma Postgres retains connection pooling but not Accelerate query caching.

Why

Non-PostgreSQL and mixed-database customers need actionable offboarding guidance even when Prisma Postgres is not a direct replacement. The guide avoids prescribing third-party products, separates Prisma ORM 7 adapter setup from Prisma ORM 6 engine setup, and treats pooling, edge compatibility, caching removal, and load validation as explicit cutover requirements.

Verification

• pnpm --filter docs lint:links — 0 errors
• pnpm --filter docs lint:spellcheck — 0 issues
• pnpm --filter docs types:check
• pnpm --filter docs lint:agent-ready — 0 failures, 0 warnings
• Local preview verified the new sidebar section, both routes, and retirement notices on the Accelerate landing and getting-started pages.
• Disposable fixtures verified Prisma ORM 7 PostgreSQL and MySQL/MariaDB adapter generation/type checking; Prisma ORM 6.19 relational generation after removing --no-engine; Prisma ORM 6.19 MongoDB direct generation; and cacheStrategy failures at both type-check and runtime validation levels.

No live database connectivity was required for these docs-only fixture checks. The guide directs customers to validate their provider-specific connection and representative load in preview before production cutover.

Summary by CodeRabbit

• Documentation
  • Added a retirement warning for standalone Prisma Accelerate, scheduled for December 1, 2026.
  • Added migration guidance for moving to Prisma Postgres or retaining an existing database without Accelerate.
  • Documented connection pooling and query caching differences with Prisma Postgres.
  • Added a comprehensive guide for removing Accelerate, including runtime, deployment, validation, and cleanup steps.
  • Added navigation links for migration resources.

[vercel]

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

Project	Deployment	Actions	Updated
blog	Ready	Preview	Sep 3, 2026 8:50am UTC
docs	Ready	Preview	Sep 3, 2026 8:50am UTC
eclipse	Ready	Preview	Sep 3, 2026 8:50am UTC
site	Ready	Preview	Sep 3, 2026 8:50am UTC

[github-actions]

🍈 Lychee Link Check Report

29 links: ✅ 5 OK | 🚫 0 errors | 🔀 2 redirects | 👻 24 excluded

✅ All links are working!

---

Full Statistics Table

Status	Count
✅ Successful	5
🔀 Redirected	2
👻 Excluded	24
🚫 Errors	0
⛔ Unsupported	0
⏳ Timeouts	0
❓ Unknown	0

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Essentials

Run ID: 76ef712a-a65a-4021-91bb-a50e08c92b1e

📥 Commits

Reviewing files that changed from the base of the PR and between 8629791 and 872e6c0.

📒 Files selected for processing (4)

• apps/docs/content/docs/accelerate/getting-started.mdx
• apps/docs/content/docs/accelerate/index.mdx
• apps/docs/content/docs/accelerate/keep-your-database.mdx
• apps/docs/content/docs/accelerate/meta.json

Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

---

Walkthrough

The documentation announces standalone Prisma Accelerate retirement on December 1, 2026. It adds migration guidance for Prisma Postgres and existing databases, including connection changes, client and cache removal, environment updates, validation, rollout, and cleanup.

Changes

Accelerate retirement documentation

Layer / File(s)	Summary
Retirement messaging and navigation apps/docs/content/docs/accelerate/getting-started.mdx, apps/docs/content/docs/accelerate/index.mdx, apps/docs/content/docs/accelerate/meta.json	Adds retirement warnings, updates Prisma Postgres capability descriptions, and adds migration navigation links.
Connection and client migration apps/docs/content/docs/accelerate/keep-your-database.mdx	Documents runtime-specific URLs, Accelerate client and cache removal, Prisma ORM version differences, generation changes, and MongoDB compatibility.
Deployment and rollout validation apps/docs/content/docs/accelerate/keep-your-database.mdx	Documents environment updates, rollback settings, staged validation, production cutover, monitoring, and credential cleanup.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Merge Risk: ⚪ Minimal · up to 872e6

This change adds Accelerate retirement and migration documentation, navigation, and version-specific setup guidance. No current merge-readiness risk remains.

Suggested reviewers: ankur-arch

🚥 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 summarizes the main changes: adding an Accelerate offboarding guide and retirement navigation. It is concise, specific, and aligned with the pull request objectives.
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.

Full details: Docstring Coverage

Explanation

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 files. (4 skipped: 4 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/accelerate-offboarding-guide

---

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