From 8c315b6a1983a8503d1f4c7882999ee1ec551a8d Mon Sep 17 00:00:00 2001 From: Martin Janse van Rensburg Date: Mon, 6 Jul 2026 18:09:38 +0200 Subject: [PATCH 1/2] blog: signal Data Proxy discontinuation in metadata, lead with Prisma Postgres The metaTitle and metaDescription still marketed Data Proxy as Early Access with no discontinuation signal; that meta is what search snippets and LLM retrieval read first. The page ranks at position ~4.7 with 12k impressions per quarter and still draws AI citations, so it was actively teaching the wrong story. Meta now states the discontinuation and points to current products. Update note and Modern Alternatives reordered to lead with Prisma Postgres (built-in pooling) per positioning, Accelerate framed as the bring-your-own- database option. In-body Early Access note moved to past tense. Body, slug, and announcement history otherwise unchanged; updatedAt bumped. Co-Authored-By: Claude Fable 5 --- .../blog/prisma-data-proxy-xb16ba0p21/index.mdx | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/apps/blog/content/blog/prisma-data-proxy-xb16ba0p21/index.mdx b/apps/blog/content/blog/prisma-data-proxy-xb16ba0p21/index.mdx index c7b4505cf2..0f49fdf62e 100644 --- a/apps/blog/content/blog/prisma-data-proxy-xb16ba0p21/index.mdx +++ b/apps/blog/content/blog/prisma-data-proxy-xb16ba0p21/index.mdx @@ -2,11 +2,12 @@ title: "Database Access in Serverless Environments with the Prisma Data Proxy" slug: "prisma-data-proxy-xb16ba0p21" date: "2021-11-11" +updatedAt: "2026-07-06" authors: - "Nikolas Burk" - "Alberto Perdomo" -metaTitle: "Database Access in Serverless Environments with the Prisma Data Proxy (Early Access)" -metaDescription: "The Prisma Data Proxy (Early Access) enables developers to use databases in serverless environments by managing a connection pool." +metaTitle: "Prisma Data Proxy (Discontinued): Serverless Database Access" +metaDescription: "The Prisma Data Proxy was Prisma's connection pooling service for serverless apps. It has been discontinued: Prisma Postgres now includes built-in connection pooling, and Prisma Accelerate supports your own database." metaImagePath: "/prisma-data-proxy-xb16ba0p21/imgs/meta-3fc1d1f448cde60bd38e28c64d061ce7fb171f81-2400x1254.png" heroImagePath: "/prisma-data-proxy-xb16ba0p21/imgs/hero-bb301a00397c84e302d829b963462d00950d326e-870x455.png" heroImageAlt: "Database Access in Serverless Environments with the Prisma Data Proxy" @@ -15,9 +16,9 @@ tags: - "platform" --- -Databases connection management in serverless functions is a major issue for many developers. The Prisma Data Proxy (Early Access) solves this problem by managing a connection pool. +Database connection management in serverless functions is a major issue for many developers. The Prisma Data Proxy (Early Access) solved this problem by managing a connection pool. -> **Update (May 2026):** Prisma Data Proxy has been discontinued. If you need connection pooling for serverless Prisma ORM apps today, start with [Prisma Accelerate](https://www.prisma.io/accelerate) and the current [deployment docs](https://www.prisma.io/docs/orm/prisma-client/deployment/serverless/deploy-to-vercel). If you're starting a new project and want a managed Postgres database plus Prisma ORM, take a look at [Prisma Postgres](https://www.prisma.io/postgres). +> **Update (July 2026):** Prisma Data Proxy has been discontinued. For new projects, [Prisma Postgres](https://www.prisma.io/postgres) includes built-in connection pooling for serverless apps out of the box. If you bring your own database, [Prisma Accelerate](https://www.prisma.io/accelerate) provides managed connection pooling; see the current [deployment docs](https://www.prisma.io/docs/orm/prisma-client/deployment/serverless/deploy-to-vercel) for setup. ## Contents @@ -100,7 +101,7 @@ The [Prisma Data Proxy](https://www.prisma.io/docs/data-platform#prisma-data-pro The Data Proxy integrates nicely with the Prisma ORM and can be enabled in a few simple steps via the [Prisma Data Platform](https://cloud.prisma.io). -> **Note**: The Prisma Data Proxy is currently in [Early Access](https://www.prisma.io/docs/about/prisma/releases#early-access) and not yet recommended for production use. +> **Note**: At the time of this announcement, the Prisma Data Proxy was in Early Access and not yet recommended for production use. It has since been discontinued; see the update at the top of this post. To learn how the Data Proxy works, check out [Daniel Norman's](https://twitter.com/daniel2color) recent talk about it: @@ -112,6 +113,6 @@ The Data Proxy also enables entirely new use cases, such as accessing a database This article remains a useful explanation of why serverless workloads need connection pooling, but the product recommendation has changed. -- Use [Prisma Accelerate](https://www.prisma.io/accelerate) if you want managed connection pooling and caching for Prisma ORM. -- Use [Prisma Postgres](https://www.prisma.io/postgres) if you want a managed Postgres database that works well with Prisma ORM. +- Use [Prisma Postgres](https://www.prisma.io/postgres) if you want a managed Postgres database with connection pooling built in; it works with Prisma ORM out of the box and supports [direct TCP connections](https://www.prisma.io/docs/postgres/database/connecting-to-your-database) for other tools. +- Use [Prisma Accelerate](https://www.prisma.io/accelerate) if you bring your own database and want managed connection pooling and caching for Prisma ORM. - Use the current [Prisma Client deployment docs](https://www.prisma.io/docs/orm/prisma-client/deployment/serverless/deploy-to-vercel) for up-to-date serverless deployment guidance. From 3f1588b3a3139bafb9d4cf16b2ab03cac16971af Mon Sep 17 00:00:00 2001 From: Martin Janse van Rensburg Date: Mon, 6 Jul 2026 18:14:29 +0200 Subject: [PATCH 2/2] blog: recommend Prisma Postgres only in Data Proxy pointers Consolidate the update note, meta description, and alternatives list on Prisma Postgres built-in pooling; own-database users go to the deployment docs. Co-Authored-By: Claude Fable 5 --- .../content/blog/prisma-data-proxy-xb16ba0p21/index.mdx | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/apps/blog/content/blog/prisma-data-proxy-xb16ba0p21/index.mdx b/apps/blog/content/blog/prisma-data-proxy-xb16ba0p21/index.mdx index 0f49fdf62e..4f9ef7cda6 100644 --- a/apps/blog/content/blog/prisma-data-proxy-xb16ba0p21/index.mdx +++ b/apps/blog/content/blog/prisma-data-proxy-xb16ba0p21/index.mdx @@ -7,7 +7,7 @@ authors: - "Nikolas Burk" - "Alberto Perdomo" metaTitle: "Prisma Data Proxy (Discontinued): Serverless Database Access" -metaDescription: "The Prisma Data Proxy was Prisma's connection pooling service for serverless apps. It has been discontinued: Prisma Postgres now includes built-in connection pooling, and Prisma Accelerate supports your own database." +metaDescription: "The Prisma Data Proxy was Prisma's connection pooling service for serverless apps. It has been discontinued: Prisma Postgres now includes built-in connection pooling for serverless and edge apps." metaImagePath: "/prisma-data-proxy-xb16ba0p21/imgs/meta-3fc1d1f448cde60bd38e28c64d061ce7fb171f81-2400x1254.png" heroImagePath: "/prisma-data-proxy-xb16ba0p21/imgs/hero-bb301a00397c84e302d829b963462d00950d326e-870x455.png" heroImageAlt: "Database Access in Serverless Environments with the Prisma Data Proxy" @@ -18,7 +18,7 @@ tags: Database connection management in serverless functions is a major issue for many developers. The Prisma Data Proxy (Early Access) solved this problem by managing a connection pool. -> **Update (July 2026):** Prisma Data Proxy has been discontinued. For new projects, [Prisma Postgres](https://www.prisma.io/postgres) includes built-in connection pooling for serverless apps out of the box. If you bring your own database, [Prisma Accelerate](https://www.prisma.io/accelerate) provides managed connection pooling; see the current [deployment docs](https://www.prisma.io/docs/orm/prisma-client/deployment/serverless/deploy-to-vercel) for setup. +> **Update (July 2026):** Prisma Data Proxy has been discontinued. For connection pooling with Prisma ORM today, use [Prisma Postgres](https://www.prisma.io/postgres): it includes a built-in connection pool for serverless and edge apps out of the box. See the current [deployment docs](https://www.prisma.io/docs/orm/prisma-client/deployment/serverless/deploy-to-vercel) for setup. ## Contents @@ -114,5 +114,4 @@ The Data Proxy also enables entirely new use cases, such as accessing a database This article remains a useful explanation of why serverless workloads need connection pooling, but the product recommendation has changed. - Use [Prisma Postgres](https://www.prisma.io/postgres) if you want a managed Postgres database with connection pooling built in; it works with Prisma ORM out of the box and supports [direct TCP connections](https://www.prisma.io/docs/postgres/database/connecting-to-your-database) for other tools. -- Use [Prisma Accelerate](https://www.prisma.io/accelerate) if you bring your own database and want managed connection pooling and caching for Prisma ORM. -- Use the current [Prisma Client deployment docs](https://www.prisma.io/docs/orm/prisma-client/deployment/serverless/deploy-to-vercel) for up-to-date serverless deployment guidance. +- Use the current [Prisma Client deployment docs](https://www.prisma.io/docs/orm/prisma-client/deployment/serverless/deploy-to-vercel) for up-to-date serverless deployment guidance, including connection handling for your own database.