• Prisma Accelerate shuts down

Prisma Accelerate shuts down on December 1, 2026

Prisma's docs say standalone Prisma Accelerate will be retired on December 1, 2026. Every app that connects through a prisma:// URL has to point at its database before then: a direct URL for long-running servers, a pooled one for serverless, and a setup that has been checked for edge runtimes.

What breaks

The URL is the easy part. I scanned 33 public apps that use Accelerate and checked every finding by hand: 23 of them need more than deleting the import, the $extends(withAccelerate()) call and the package.

The common extras were edge entry points that reach Prisma Client through imports (14 apps), Accelerate URLs left in .env.example, READMEs or tests (14), @prisma/client/edge imports (8), and prisma generate --no-engine in scripts, Dockerfiles or CI (7). Five apps used the caching API, with 31 cacheStrategy calls between them.

How to fix it

Prisma's own checklist: swap the URL in every environment and keep a separate direct URL for migrations if you use a pooler; remove the extension, the accelerateUrl option and the package; regenerate the client; delete cacheStrategy, withAccelerateInfo() and $accelerate calls, since queries now go straight to the database. Load-test in staging and keep the old config as a rollback until production is stable.

Check a repository for this

The Accelerate extension, prisma:// URLs, edge client imports, generate flags in CI and Docker, and caching calls.

Runs in your browser with 2 anonymous GitHub API requests. Example: Codehagen/Badget@16a677f95361.

The same rules run offline, with a --fix for the safe rewrites, in atokim4/prisma-accelerate-exit (MIT).

Sources

Dates and wording re-read on the official pages on . Vendors move dates; the official page wins.