Open
Conversation
Contributor
WalkthroughDocumentation rebranding campaign replacing "Prisma Data Platform" with "Prisma Developer Platform" across ~50 MDX documentation files spanning prisma-postgres, accelerate, optimize, platform, management API, ORM deployment, and CLI references. All changes are terminology-only with no functional code modifications. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~30 minutes The homogeneous nature of changes across files—consistent string replacements for platform rebranding—simplifies individual assessments, but the sheer volume (~50 files) and distributed scope across different product areas warrants careful verification for consistency and completeness. Two files contain modest content expansions (maturity-levels policy additions, cli-reference command documentation), which introduce minor analytical overhead. 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
🍈 Lychee Link Check Report3664 links: ✅ All links are working!Full Statistics Table
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (3)
apps/docs/content/docs.v6/postgres/query-optimization/setup.mdx (1)
71-71:⚠️ Potential issue | 🟡 MinorPre-existing section numbering gap:
2.4is missing.The guide jumps from
### 2.3. Add the Optimize API Key...straight to### 2.5. Use Prisma Optimize to generate insights, skipping2.4entirely. While this isn't introduced by this PR, it's worth correcting here since readers following the numbered steps will naturally notice the gap and wonder if they missed something.📝 Proposed fix for the section numbering
-### 2.5. Use Prisma Optimize to generate insights +### 2.4. Use Prisma Optimize to generate insights🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs.v6/postgres/query-optimization/setup.mdx` at line 71, There's a missing numbered heading between "### 2.3. Add the Optimize API Key..." and "### 2.5. Use Prisma Optimize to generate insights"; add a new "### 2.4." heading (for example "### 2.4. Verify Optimize API key and project settings") and a short one- or two-sentence step that bridges 2.3 and 2.5 (e.g., confirm the API key is set in environment/config and the project/org is selected in the Optimize UI). Update the surrounding headings so numbering flows sequentially from 2.3 → 2.4 → 2.5 and ensure the new heading text is consistent with the existing style.apps/docs/content/docs/(index)/prisma-postgres/import-from-existing-database-mysql.mdx (1)
44-44:⚠️ Potential issue | 🟡 MinorPre-existing formatting artifact: stray
** **on line 44While not introduced by this PR, line 44 contains
** **(two bold markers wrapping a space), which renders as an invisible bold element and creates an unintended whitespace gap in the sentence:
Once your database is** **provisioned✏️ Suggested fix
-Once your database is** **provisioned, find your direct Prisma Postgres connection string: +Once your database is provisioned, find your direct Prisma Postgres connection string:🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs/`(index)/prisma-postgres/import-from-existing-database-mysql.mdx at line 44, Remove the stray bold markers in the sentence "Once your database is** **provisioned" so it reads "Once your database is provisioned"; locate the text in the MDX file where that exact fragment appears and delete the `** **` (or replace with a single space) to eliminate the invisible bold element and unwanted gap.apps/docs/content/docs.v6/platform/maturity-levels.mdx (1)
18-40:⚠️ Potential issue | 🟡 MinorMinor preposition inconsistency: "on" vs. "in".
Lines 18 and 28 use "on the Prisma Developer Platform" while line 40 uses "in the Prisma Developer Platform." This is likely carried over from the old text, but since all three lines are being touched in this PR, it's a good opportunity to make them consistent. Pick one preposition — "on" reads more naturally for a platform.
Suggested fix
-If a feature in the Prisma Developer Platform is Generally Available: +If a feature on the Prisma Developer Platform is Generally Available:🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs.v6/platform/maturity-levels.mdx` around lines 18 - 40, Replace the inconsistent preposition "in" with "on" so all feature descriptions consistently read "on the Prisma Developer Platform"; update the phrase used in the General Availability section (the occurrence that currently reads "in the Prisma Developer Platform") to "on the Prisma Developer Platform" to match the earlier "on the Prisma Developer Platform" instances found in the Early Access and Preview sections.
♻️ Duplicate comments (2)
apps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/kysely.mdx (1)
122-122: Covered by the comment on typeorm.mdx line 106.The branding change here is identical in pattern and shares the same potential timing concern about the console's displayed name. See the comment there.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs.v6/`(index)/prisma-postgres/quickstart/kysely.mdx at line 122, Update the sentence that mentions "Prisma Developer Platform" in the line "Claiming moves the database into your [Prisma Developer Platform](https://console.prisma.io) account." to match the fix applied in typeorm.mdx: use the current public branding ("Prisma Console") or neutral phrasing and avoid implying immediate UI/name changes (e.g., "moves the database into your Prisma Console account" or "moves the database into your Prisma account via the Prisma Console"); keep the claim URL link to https://console.prisma.io and ensure the wording does not assume the console name shown in the UI will match immediately.apps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/drizzle-orm.mdx (1)
97-97: Covered by the comment on typeorm.mdx line 106.Same branding change, same shared URL, same timing consideration applies here.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs.v6/`(index)/prisma-postgres/quickstart/drizzle-orm.mdx at line 97, Replace the old branding and link in the sentence that currently reads "Prisma Developer Platform" and links to https://console.prisma.io, and make the same timing/wording change you applied in typeorm.mdx: update the displayed product name to the new official branding, swap the hard-coded URL to the shared canonical claim URL used across docs, and adjust the "24 hours" phrasing if you changed it in typeorm.mdx; specifically edit the sentence containing the exact strings "Prisma Developer Platform", "https://console.prisma.io", and "24 hours" so they match the updated branding, shared URL, and timing wording from your typeorm.mdx change.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/docs/content/docs.v6/`(index)/prisma-postgres/quickstart/typeorm.mdx:
- Line 106: Replace the label text "[Prisma Developer
Platform](https://console.prisma.io)" with "Prisma Console" (keeping the same
URL) where it appears in the docs to match the actual site branding;
specifically locate the exact link text instance and update it in the affected
files (the instance currently reading "[Prisma Developer
Platform](https://console.prisma.io)" in typeorm.mdx, kysely.mdx, and
drizzle-orm.mdx) so the displayed anchor text reads "Prisma Console" while
preserving the URL.
In `@apps/docs/content/docs.v6/orm/overview/beyond-prisma-orm.mdx`:
- Line 59: Fix the two grammar issues in the sentence in
apps/docs/content/docs.v6/orm/overview/beyond-prisma-orm.mdx: change "Prisma
Accelerate take features" to "Prisma Accelerate takes features" (subject-verb
agreement) and change "Get started for free the [Prisma Developer Platform]" to
"Get started for free on the [Prisma Developer Platform]" (add the preposition
"on the"); update the single sentence string accordingly.
---
Outside diff comments:
In `@apps/docs/content/docs.v6/platform/maturity-levels.mdx`:
- Around line 18-40: Replace the inconsistent preposition "in" with "on" so all
feature descriptions consistently read "on the Prisma Developer Platform";
update the phrase used in the General Availability section (the occurrence that
currently reads "in the Prisma Developer Platform") to "on the Prisma Developer
Platform" to match the earlier "on the Prisma Developer Platform" instances
found in the Early Access and Preview sections.
In `@apps/docs/content/docs.v6/postgres/query-optimization/setup.mdx`:
- Line 71: There's a missing numbered heading between "### 2.3. Add the Optimize
API Key..." and "### 2.5. Use Prisma Optimize to generate insights"; add a new
"### 2.4." heading (for example "### 2.4. Verify Optimize API key and project
settings") and a short one- or two-sentence step that bridges 2.3 and 2.5 (e.g.,
confirm the API key is set in environment/config and the project/org is selected
in the Optimize UI). Update the surrounding headings so numbering flows
sequentially from 2.3 → 2.4 → 2.5 and ensure the new heading text is consistent
with the existing style.
In
`@apps/docs/content/docs/`(index)/prisma-postgres/import-from-existing-database-mysql.mdx:
- Line 44: Remove the stray bold markers in the sentence "Once your database
is** **provisioned" so it reads "Once your database is provisioned"; locate the
text in the MDX file where that exact fragment appears and delete the `** **`
(or replace with a single space) to eliminate the invisible bold element and
unwanted gap.
---
Duplicate comments:
In
`@apps/docs/content/docs.v6/`(index)/prisma-postgres/quickstart/drizzle-orm.mdx:
- Line 97: Replace the old branding and link in the sentence that currently
reads "Prisma Developer Platform" and links to https://console.prisma.io, and
make the same timing/wording change you applied in typeorm.mdx: update the
displayed product name to the new official branding, swap the hard-coded URL to
the shared canonical claim URL used across docs, and adjust the "24 hours"
phrasing if you changed it in typeorm.mdx; specifically edit the sentence
containing the exact strings "Prisma Developer Platform",
"https://console.prisma.io", and "24 hours" so they match the updated branding,
shared URL, and timing wording from your typeorm.mdx change.
In `@apps/docs/content/docs.v6/`(index)/prisma-postgres/quickstart/kysely.mdx:
- Line 122: Update the sentence that mentions "Prisma Developer Platform" in the
line "Claiming moves the database into your [Prisma Developer
Platform](https://console.prisma.io) account." to match the fix applied in
typeorm.mdx: use the current public branding ("Prisma Console") or neutral
phrasing and avoid implying immediate UI/name changes (e.g., "moves the database
into your Prisma Console account" or "moves the database into your Prisma
account via the Prisma Console"); keep the claim URL link to
https://console.prisma.io and ensure the wording does not assume the console
name shown in the UI will match immediately.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (61)
apps/docs/content/docs.v6/(index)/prisma-postgres/from-the-cli.mdxapps/docs/content/docs.v6/(index)/prisma-postgres/import-from-existing-database-mysql.mdxapps/docs/content/docs.v6/(index)/prisma-postgres/import-from-existing-database-postgresql.mdxapps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/drizzle-orm.mdxapps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/kysely.mdxapps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/typeorm.mdxapps/docs/content/docs.v6/accelerate/caching.mdxapps/docs/content/docs.v6/accelerate/connection-pooling.mdxapps/docs/content/docs.v6/accelerate/getting-started.mdxapps/docs/content/docs.v6/guides/github-actions.mdxapps/docs/content/docs.v6/guides/management-api-basic.mdxapps/docs/content/docs.v6/guides/multiple-databases.mdxapps/docs/content/docs.v6/guides/use-prisma-in-pnpm-workspaces.mdxapps/docs/content/docs.v6/optimize/getting-started.mdxapps/docs/content/docs.v6/orm/more/ai-tools/chatgpt.mdxapps/docs/content/docs.v6/orm/more/comparisons/prisma-and-drizzle.mdxapps/docs/content/docs.v6/orm/overview/beyond-prisma-orm.mdxapps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-cloudflare.mdxapps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-deno-deploy.mdxapps/docs/content/docs.v6/orm/prisma-client/deployment/traditional/deploy-to-railway.mdxapps/docs/content/docs.v6/orm/prisma-client/setup-and-configuration/databases-connections/index.mdxapps/docs/content/docs.v6/orm/reference/prisma-cli-reference.mdxapps/docs/content/docs.v6/platform/about.mdxapps/docs/content/docs.v6/platform/index.mdxapps/docs/content/docs.v6/platform/maturity-levels.mdxapps/docs/content/docs.v6/platform/platform-cli/about.mdxapps/docs/content/docs.v6/platform/platform-cli/commands.mdxapps/docs/content/docs.v6/postgres/database/connection-pooling.mdxapps/docs/content/docs.v6/postgres/integrations/vscode.mdxapps/docs/content/docs.v6/postgres/introduction/management-api-sdk.mdxapps/docs/content/docs.v6/postgres/introduction/npx-create-db.mdxapps/docs/content/docs.v6/postgres/query-optimization/setup.mdxapps/docs/content/docs/(index)/prisma-postgres/from-the-cli.mdxapps/docs/content/docs/(index)/prisma-postgres/import-from-existing-database-mysql.mdxapps/docs/content/docs/(index)/prisma-postgres/import-from-existing-database-postgresql.mdxapps/docs/content/docs/(index)/prisma-postgres/quickstart/drizzle-orm.mdxapps/docs/content/docs/(index)/prisma-postgres/quickstart/kysely.mdxapps/docs/content/docs/(index)/prisma-postgres/quickstart/typeorm.mdxapps/docs/content/docs/accelerate/caching.mdxapps/docs/content/docs/accelerate/connection-pooling.mdxapps/docs/content/docs/accelerate/getting-started.mdxapps/docs/content/docs/ai/tools/chatgpt.mdxapps/docs/content/docs/cli/init.mdxapps/docs/content/docs/console/features/optimize.mdxapps/docs/content/docs/console/index.mdxapps/docs/content/docs/console/more/feature-maturity.mdxapps/docs/content/docs/guides/database/multiple-databases.mdxapps/docs/content/docs/guides/deployment/bun-workspaces.mdxapps/docs/content/docs/guides/deployment/pnpm-workspaces.mdxapps/docs/content/docs/guides/integrations/github-actions.mdxapps/docs/content/docs/guides/making-guides.mdxapps/docs/content/docs/guides/postgres/vscode.mdxapps/docs/content/docs/management-api/getting-started.mdxapps/docs/content/docs/management-api/sdk.mdxapps/docs/content/docs/optimize/getting-started.mdxapps/docs/content/docs/orm/more/comparisons/prisma-and-drizzle.mdxapps/docs/content/docs/orm/prisma-client/deployment/edge/deploy-to-cloudflare.mdxapps/docs/content/docs/orm/prisma-client/deployment/edge/deploy-to-deno-deploy.mdxapps/docs/content/docs/orm/prisma-client/deployment/traditional/deploy-to-railway.mdxapps/docs/content/docs/orm/reference/prisma-cli-reference.mdxapps/docs/content/docs/postgres/npx-create-db.mdx
| ::: | ||
|
|
||
| The database created is temporary and will be deleted in 24 hours unless claimed. Claiming moves the database into your [Prisma Data Platform](https://console.prisma.io) account. Visit the claim URL from the output to keep your database. | ||
| The database created is temporary and will be deleted in 24 hours unless claimed. Claiming moves the database into your [Prisma Developer Platform](https://console.prisma.io) account. Visit the claim URL from the output to keep your database. |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Prisma console.prisma.io current platform name branding 2026
💡 Result:
As of February 24, 2026, console.prisma.io is branded as Prisma Console (“Console” in Prisma’s docs). (prisma.io)
In Prisma’s current branding/docs, Prisma Console is the web platform used to manage/configure Prisma’s hosted products (notably Prisma Accelerate, Prisma Optimize, and Prisma Postgres). (prisma.io)
Citations:
🏁 Script executed:
# Search for the other two files mentioned in the review
fd -t f "kysely.mdx|drizzle-orm.mdx" --exec grep -n "Prisma Developer Platform" {} +Repository: prisma/web
Length of output: 1496
🏁 Script executed:
# Also check the specific line ranges mentioned
fd -t f "kysely.mdx" -x sed -n '120,125p' {}Repository: prisma/web
Length of output: 569
🏁 Script executed:
fd -t f "drizzle-orm.mdx" -x sed -n '95,100p' {}Repository: prisma/web
Length of output: 569
Update branding references to match console.prisma.io's actual label.
The docs now reference "Prisma Developer Platform", but the console itself is currently branded as Prisma Console in Prisma's documentation. A reader clicking the link will encounter a mismatch between the label in the docs and the actual page title.
This affects three files:
- typeorm.mdx line 106
- kysely.mdx line 122
- drizzle-orm.mdx line 97
Either update all three references to "Prisma Console" or align the console's branding documentation with this new label before shipping.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/docs/content/docs.v6/`(index)/prisma-postgres/quickstart/typeorm.mdx at
line 106, Replace the label text "[Prisma Developer
Platform](https://console.prisma.io)" with "Prisma Console" (keeping the same
URL) where it appears in the docs to match the actual site branding;
specifically locate the exact link text instance and update it in the affected
files (the instance currently reading "[Prisma Developer
Platform](https://console.prisma.io)" in typeorm.mdx, kysely.mdx, and
drizzle-orm.mdx) so the displayed anchor text reads "Prisma Console" while
preserving the URL.
| ## Grow with Prisma | ||
|
|
||
| Prisma Accelerate take features built into Prisma ORM and build upon them by adding additional capabilities like globally-optimized caching and connection pooling. Get started for free the [Prisma Data Platform](https://console.prisma.io/login) and explore how Accelerate can help you build scalable, high-performance applications! | ||
| Prisma Accelerate take features built into Prisma ORM and build upon them by adding additional capabilities like globally-optimized caching and connection pooling. Get started for free the [Prisma Developer Platform](https://console.prisma.io/login) and explore how Accelerate can help you build scalable, high-performance applications! |
Contributor
There was a problem hiding this comment.
Two grammatical errors slipped into this sentence.
The rebranding itself is correct, but the sentence has two prose issues:
"Prisma Accelerate take features"— subject-verb agreement: should be "takes"."Get started for free the [Prisma Developer Platform]"— missing preposition: should be "for free on the" (or "for free with the").
✏️ Proposed fix
-Prisma Accelerate take features built into Prisma ORM and build upon them by adding additional capabilities like globally-optimized caching and connection pooling. Get started for free the [Prisma Developer Platform](https://console.prisma.io/login) and explore how Accelerate can help you build scalable, high-performance applications!
+Prisma Accelerate takes features built into Prisma ORM and builds upon them by adding additional capabilities like globally-optimized caching and connection pooling. Get started for free on the [Prisma Developer Platform](https://console.prisma.io/login) and explore how Accelerate can help you build scalable, high-performance applications!📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| Prisma Accelerate take features built into Prisma ORM and build upon them by adding additional capabilities like globally-optimized caching and connection pooling. Get started for free the [Prisma Developer Platform](https://console.prisma.io/login) and explore how Accelerate can help you build scalable, high-performance applications! | |
| Prisma Accelerate takes features built into Prisma ORM and builds upon them by adding additional capabilities like globally-optimized caching and connection pooling. Get started for free on the [Prisma Developer Platform](https://console.prisma.io/login) and explore how Accelerate can help you build scalable, high-performance applications! |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/docs/content/docs.v6/orm/overview/beyond-prisma-orm.mdx` at line 59, Fix
the two grammar issues in the sentence in
apps/docs/content/docs.v6/orm/overview/beyond-prisma-orm.mdx: change "Prisma
Accelerate take features" to "Prisma Accelerate takes features" (subject-verb
agreement) and change "Get started for free the [Prisma Developer Platform]" to
"Get started for free on the [Prisma Developer Platform]" (add the preposition
"on the"); update the single sentence string accordingly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update copy for PDP
Summary by CodeRabbit