From 0ccb82e057871f1318fd1ca5f0fdcc3da742b6bc Mon Sep 17 00:00:00 2001
From: Nikolas Burk <nikolas.burk@gmail.com>
Date: Tue, 16 Sep 2025 11:40:02 +0200
Subject: [PATCH 01/11] no required login for local ppg workflows

---
 .../325-prisma-config-reference.mdx           | 32 +++++++++----------
 .../800-more/350-ai-tools/100-cursor.mdx      |  2 +-
 .../800-more/350-ai-tools/200-tabnine.mdx     |  2 +-
 .../800-more/350-ai-tools/300-windsurf.mdx    |  2 +-
 .../1100-integrations/500-vscode.mdx          |  2 +-
 5 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/content/200-orm/500-reference/325-prisma-config-reference.mdx b/content/200-orm/500-reference/325-prisma-config-reference.mdx
index f8bffe5d73..0fa0334e92 100644
--- a/content/200-orm/500-reference/325-prisma-config-reference.mdx
+++ b/content/200-orm/500-reference/325-prisma-config-reference.mdx
@@ -12,6 +12,7 @@ The Prisma Config file configures the Prisma CLI, including subcommands like `mi
 You can define your config in either of two ways:
 
 - Using the `defineConfig` helper:
+
   ```ts
   import path from "node:path";
   import { defineConfig } from "prisma/config";
@@ -26,11 +27,12 @@ You can define your config in either of two ways:
     },
     typedSql: {
       path: path.join("db", "queries"),
-    }
+    },
   });
   ```
 
 - Using TypeScript's `satisfies` operator with the `PrismaConfig` type:
+
   ```ts
   import path from "node:path";
   import type { PrismaConfig } from "prisma";
@@ -45,7 +47,7 @@ You can define your config in either of two ways:
     },
     typedSql: {
       path: path.join("db", "queries"),
-    }
+    },
   } satisfies PrismaConfig;
   ```
 
@@ -57,10 +59,10 @@ Here is a simplified version of the `PrismaConfig` type:
 export declare type PrismaConfig = {
   // Whether features with an unstable API are enabled.
   experimental: {
-    adapter: true,
-    externalTables: true,
-    studio: true,
-  },
+    adapter: true;
+    externalTables: true;
+    studio: true;
+  };
 
   // The path to the schema file, or path to a folder that shall be recursively searched for *.prisma files.
   schema?: string;
@@ -98,14 +100,13 @@ Prisma Config files can be named as `prisma.config.*` or `.config/prisma.*` with
 
 :::tip[Recommendation]
 
-- Use **`prisma.config.ts`** for small TypeScript projects.  
-- Use **`.config/prisma.ts`** for larger TypeScript projects with multiple configuration files (following the [`.config` directory proposal](https://github.com/pi0/config-dir)).  
+- Use **`prisma.config.ts`** for small TypeScript projects.
+- Use **`.config/prisma.ts`** for larger TypeScript projects with multiple configuration files (following the [`.config` directory proposal](https://github.com/pi0/config-dir)).
 
 :::
 
 ## Options reference
 
-
 ### `schema`
 
 Configures how Prisma ORM locates and loads your schema file(s). Can be a file or folder path. Relative paths are resolved relative to the `prisma.config.ts` file location. See [here](/orm/prisma-schema/overview/location#multi-file-prisma-schema) for more info about schema location options.
@@ -118,8 +119,8 @@ Configures how Prisma ORM locates and loads your schema file(s). Can be a file o
 
 A function that returns a Prisma driver adapter instance which is used by the Prisma CLI to run migrations. The function should return a `Promise` that resolves to a valid Prisma driver adapter.
 
-| Property          | Type                                                           | Required | Default |
-| ----------------- | -------------------------------------------------------------- | -------- | ------- |
+| Property  | Type                                                   | Required | Default |
+| --------- | ------------------------------------------------------ | -------- | ------- |
 | `adapter` | `() => Promise<SqlMigrationAwareDriverAdapterFactory>` | No       | none    |
 
 Example using the Prisma ORM D1 driver adapter:
@@ -134,7 +135,7 @@ import "dotenv/config";
 
 export default {
   experimental: {
-    adapter: true
+    adapter: true,
   },
   schema: path.join("prisma", "schema.prisma"),
   async adapter() {
@@ -176,7 +177,7 @@ import type { PrismaConfig } from "prisma";
 
 export default {
   experimental: {
-    studio: true
+    studio: true,
   },
   studio: {
     adapter: async (env: Env) => {
@@ -219,7 +220,7 @@ export default defineConfig({
 });
 ```
 
-Learn more about the [`externalTables` feature here](/orm/prisma-schema/data-model/externally-managed-tables). 
+Learn more about the [`externalTables` feature here](/orm/prisma-schema/data-model/externally-managed-tables).
 
 ### `migrations.path`
 
@@ -277,7 +278,7 @@ export default defineConfig({
 });
 ```
 
-Learn more about the [`externalTables` feature here](/orm/prisma-schema/data-model/externally-managed-tables). 
+Learn more about the [`externalTables` feature here](/orm/prisma-schema/data-model/externally-managed-tables).
 
 ### `views.path`
 
@@ -409,7 +410,6 @@ Prisma CLI commands such as `prisma validate` or `prisma migrate` use `prisma.co
 - Paths defined in the config file (e.g., `schema`, `migrations`) are always resolved **relative to the location of the config file**, not where you run the CLI command from.
 - The CLI must first **find the config file** itself, which depends on how Prisma is installed and the package manager used.
 
-
 ### Behavior with `pnpm prisma`
 
 When Prisma is installed locally and run via `pnpm prisma`, the config file is detected automatically whether you run the command from the project root or a subdirectory.
diff --git a/content/200-orm/800-more/350-ai-tools/100-cursor.mdx b/content/200-orm/800-more/350-ai-tools/100-cursor.mdx
index 9d8275a356..f2d6c6a49f 100644
--- a/content/200-orm/800-more/350-ai-tools/100-cursor.mdx
+++ b/content/200-orm/800-more/350-ai-tools/100-cursor.mdx
@@ -528,7 +528,7 @@ With its built-in database management interface, the [Prisma VS Code extension](
 
 The UI enables the following workflows:
 
-- Authenticate with the [Prisma Console](https://console.prisma.io)
+- Authenticate with the [Prisma Console](https://console.prisma.io) (not required for local Prisma Postgres workflows)
 - View, create and delete Prisma Postgres instances (local & remote)
 - "Push to cloud": Easily deploy a local Prisma Postgres instance
 - View and edit data via an embedded Prisma Studio
diff --git a/content/200-orm/800-more/350-ai-tools/200-tabnine.mdx b/content/200-orm/800-more/350-ai-tools/200-tabnine.mdx
index 63c470a872..af2e38a5d6 100644
--- a/content/200-orm/800-more/350-ai-tools/200-tabnine.mdx
+++ b/content/200-orm/800-more/350-ai-tools/200-tabnine.mdx
@@ -465,7 +465,7 @@ With its built-in database management interface, the [Prisma VS Code extension](
 
 The UI enables the following workflows:
 
-- Authenticate with the [Prisma Console](https://console.prisma.io)
+- Authenticate with the [Prisma Console](https://console.prisma.io) (not required for local Prisma Postgres workflows)
 - View, create and delete Prisma Postgres instances (local & remote)
 - "Push to cloud": Easily deploy a local Prisma Postgres instance
 - View and edit data via an embedded Prisma Studio
diff --git a/content/200-orm/800-more/350-ai-tools/300-windsurf.mdx b/content/200-orm/800-more/350-ai-tools/300-windsurf.mdx
index b312ff8758..1ae8c08775 100644
--- a/content/200-orm/800-more/350-ai-tools/300-windsurf.mdx
+++ b/content/200-orm/800-more/350-ai-tools/300-windsurf.mdx
@@ -552,7 +552,7 @@ With its built-in database management interface, [the Prisma VS Code extension](
 
 The UI enables the following workflows:
 
-- Authenticate with the [Prisma Console](https://console.prisma.io)
+- Authenticate with the [Prisma Console](https://console.prisma.io) (not required for local Prisma Postgres workflows)
 - View, create and delete Prisma Postgres instances (local & remote)
 - "Push to cloud": Easily deploy a local Prisma Postgres instance
 - View and edit data via an embedded Prisma Studio
diff --git a/content/250-postgres/1100-integrations/500-vscode.mdx b/content/250-postgres/1100-integrations/500-vscode.mdx
index 618e4731b9..b6f1b972fe 100644
--- a/content/250-postgres/1100-integrations/500-vscode.mdx
+++ b/content/250-postgres/1100-integrations/500-vscode.mdx
@@ -19,7 +19,7 @@ The Prisma VS Code extension includes a dedicated UI to manage Prisma Postgres i
 
 The UI enables the following workflows:
 
-- Authenticate with the [Prisma Console](https://console.prisma.io)
+- Authenticate with the [Prisma Console](https://console.prisma.io) (not required for local Prisma Postgres workflows)
 - View, create and delete  Prisma Postgres instances (local & remote)
 - "Push to cloud": Easily deploy a local Prisma Postgres instance
 - View and edit data via an embedded Prisma Studio

From 03c48fef32e14adf6a9c6e7fe847ac16e545a1f7 Mon Sep 17 00:00:00 2001
From: Nikolas Burk <nikolas.burk@gmail.com>
Date: Tue, 16 Sep 2025 14:46:19 +0200
Subject: [PATCH 02/11] remove preview label from direct connections page

---
 content/250-postgres/300-database/650-direct-connections.mdx | 1 -
 1 file changed, 1 deletion(-)

diff --git a/content/250-postgres/300-database/650-direct-connections.mdx b/content/250-postgres/300-database/650-direct-connections.mdx
index 744cbabcfb..a0f8a98eba 100644
--- a/content/250-postgres/300-database/650-direct-connections.mdx
+++ b/content/250-postgres/300-database/650-direct-connections.mdx
@@ -4,7 +4,6 @@ metaTitle: "Direct connections (TCP)"
 metaDescription: "Learn about connecting directly to your Prisma Postgres database via direct TCP."
 tocDepth: 3
 toc: true
-sidebar_class_name: preview-badge
 ---
 
 ## Overview

From 412dea9106ff51bcd8d9d9657fba10d69749d4e5 Mon Sep 17 00:00:00 2001
From: Nikolas Burk <nikolas.burk@gmail.com>
Date: Tue, 16 Sep 2025 14:50:47 +0200
Subject: [PATCH 03/11] update flow for getting direct connection string

---
 .../115-import-from-existing-database-mysql.mdx       | 10 +++++-----
 .../100-introduction/200-getting-started.mdx          | 11 +++++------
 .../300-database/650-direct-connections.mdx           |  5 ++---
 3 files changed, 12 insertions(+), 14 deletions(-)

diff --git a/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx b/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx
index 52c8461fb9..bb43aeb438 100644
--- a/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx
+++ b/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx
@@ -41,11 +41,11 @@ Follow these steps to create a new Prisma Postgres database:
 
 Once your database was provisioned, find your direct Prisma Postgres connection string:  
 
-1. Navigate to your active Prisma Postgres instance.
-1. Click the **API Keys** tab in the project's sidenav.
-1. Click the **Create API key** button.
-1. In the popup, provide a **Name** for the API key and click **Create**.
-1. Copy the connection string starting with `postgres://`, this is your direct connection string.
+1. Open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
+1. Navigate to a environment with an active Prisma Postgres instance
+1. Click the **Dashboard** tab in the project's sidenav
+1. Find the **Connect to your database** card and click the **Connect** button
+1. Copy the connection string starting with `postgres://`, this is your direct connection string
 
 Save the connection string, you'll need it in the next step.
 
diff --git a/content/250-postgres/100-introduction/200-getting-started.mdx b/content/250-postgres/100-introduction/200-getting-started.mdx
index c9a59e48b3..c190dbba22 100644
--- a/content/250-postgres/100-introduction/200-getting-started.mdx
+++ b/content/250-postgres/100-introduction/200-getting-started.mdx
@@ -54,12 +54,11 @@ prisma generate --no-engine
 You can access Prisma Postgres with any ORM or database tool of your choice via [direct TCP connections](/postgres/database/direct-connections).
 
 In order to get a direct TCP connection string, you need to:
-1. open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
-1. navigate to a environment with an active Prisma Postgres instance
-1. click the **API Keys** tab in the project's sidenav
-1. click the **Create API key** button 
-1. in the popup, provide a **Name** for the API key and click **Create**
-1. copy the connection string starting with `postgres://`, this is your direct TCP connection string
+1. Open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
+1. Navigate to a environment with an active Prisma Postgres instance
+1. Click the **Dashboard** tab in the project's sidenav
+1. Find the **Connect to your database** card and click the **Connect** button
+1. Copy the connection string starting with `postgres://`, this is your direct connection string
 
 Once you have the connection string, you can follow the setup docs for PostgreSQL of any ORM or database tool:
 
diff --git a/content/250-postgres/300-database/650-direct-connections.mdx b/content/250-postgres/300-database/650-direct-connections.mdx
index a0f8a98eba..fc3d7a6300 100644
--- a/content/250-postgres/300-database/650-direct-connections.mdx
+++ b/content/250-postgres/300-database/650-direct-connections.mdx
@@ -18,9 +18,8 @@ In order to get a direct connection string, you need to:
 
 1. Open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
 1. Navigate to a environment with an active Prisma Postgres instance
-1. Click the **API Keys** tab in the project's sidenav
-1. Click the **Create API key** button
-1. In the popup, provide a **Name** for the API key and click **Create**
+1. Click the **Dashboard** tab in the project's sidenav
+1. Find the **Connect to your database** card and click the **Connect** button
 1. Copy the connection string starting with `postgres://`, this is your direct connection string
 
 ## Connection string

From 1165a06d5bf9970b7396ad6a77f52282dfb466e6 Mon Sep 17 00:00:00 2001
From: Nikolas Burk <nikolas.burk@gmail.com>
Date: Tue, 16 Sep 2025 16:17:17 +0200
Subject: [PATCH 04/11] add workspace metrics

---
 .../250-postgres/100-introduction/250-overview.mdx   | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/content/250-postgres/100-introduction/250-overview.mdx b/content/250-postgres/100-introduction/250-overview.mdx
index 6ba64123e0..1d9feb32f4 100644
--- a/content/250-postgres/100-introduction/250-overview.mdx
+++ b/content/250-postgres/100-introduction/250-overview.mdx
@@ -11,8 +11,18 @@ toc: true
 
 It supports the following workflows:
 
-- Schema migrations and queries (via [Prisma ORM](https://www.prisma.io/orm))
+- Schema migrations and queries (via [Prisma ORM](https://www.prisma.io/orm) or any other ORM/database library)
 - Connection pooling and caching (via [Prisma Accelerate](https://www.prisma.io/accelerate))
+- Local database workflows via [`prisma dev`](/postgres/database/local-development)
+
+## Usage metrics
+
+You can view the following usage metrics in your Console Dashboard:
+- Cumulative usage over time
+- Total count of requests
+- Storage used per project in your workspace
+- Operations used per day
+- Databases per project
 
 ## Billing 
 

From cd68be539ceffda462c467e33dbbbb15e35cab10 Mon Sep 17 00:00:00 2001
From: Nikolas Burk <nikolas.burk@gmail.com>
Date: Tue, 16 Sep 2025 17:24:53 +0200
Subject: [PATCH 05/11] add workspace metrics

---
 content/250-postgres/100-introduction/250-overview.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/250-postgres/100-introduction/250-overview.mdx b/content/250-postgres/100-introduction/250-overview.mdx
index 1d9feb32f4..e0dcda86a1 100644
--- a/content/250-postgres/100-introduction/250-overview.mdx
+++ b/content/250-postgres/100-introduction/250-overview.mdx
@@ -18,6 +18,7 @@ It supports the following workflows:
 ## Usage metrics
 
 You can view the following usage metrics in your Console Dashboard:
+
 - Cumulative usage over time
 - Total count of requests
 - Storage used per project in your workspace

From c46f20a771b52f609656478a9ef6ecc1ab95aa13 Mon Sep 17 00:00:00 2001
From: Nikolas Burk <nikolas.burk@gmail.com>
Date: Tue, 16 Sep 2025 17:44:46 +0200
Subject: [PATCH 06/11] add prisma config updates

---
 .../325-prisma-config-reference.mdx           | 35 +++++++++++++++++--
 1 file changed, 33 insertions(+), 2 deletions(-)

diff --git a/content/200-orm/500-reference/325-prisma-config-reference.mdx b/content/200-orm/500-reference/325-prisma-config-reference.mdx
index 0fa0334e92..1624180ee1 100644
--- a/content/200-orm/500-reference/325-prisma-config-reference.mdx
+++ b/content/200-orm/500-reference/325-prisma-config-reference.mdx
@@ -67,10 +67,10 @@ export declare type PrismaConfig = {
   // The path to the schema file, or path to a folder that shall be recursively searched for *.prisma files.
   schema?: string;
 
-  // The Driver Adapter used for Prisma CLI.
+  // Configuration for the driver adapter used for Prisma CLI.
   adapter?: () => Promise<SqlMigrationAwareDriverAdapterFactory>;
 
-  // The configuration for Prisma Studio.
+  // Configuration for Prisma Studio.
   studio?: {
     adapter: () => Promise<SqlMigrationAwareDriverAdapterFactory>;
   };
@@ -91,6 +91,15 @@ export declare type PrismaConfig = {
   typedSql?: {
     path: string;
   };
+
+  // Configuration to specify how the CLI should connect to the DB.
+  engine: "classic" | "js";
+
+  // Configuration of your database connection details.
+  datasource: {
+    url: string;
+    shadowDatabaseUrl?: string;
+  };
 };
 ```
 
@@ -331,6 +340,28 @@ Failed to load config file "~" as a TypeScript/JavaScript module. Error: Error:
 
 :::
 
+### `engine`
+
+Determines whether you want to configure the database connection details via the `datasource` or an `adapter`.
+
+| Property | Type                | Required | Default |
+| -------- | ------------------- | -------- | ------- |
+| `engine` | `"classic" \| "js"` | No       | none    |
+
+Note that:
+
+- if you're using `"classic"`, you must specify a `datasource` objedct with a `url`
+- if you're using `"js"`, you must provide an `adapter` function
+
+### `datasource`
+
+Defines the database connection details. Only valid when `engine` is set to `"classic"`.
+
+| Property                       | Type     | Required | Default |
+| ------------------------------ | -------- | -------- | ------- |
+| `datasource.url`               | `string` | Yes      | none    |
+| `datasource.shadowDatabaseUrl` | `string` | No       | none    |
+
 ## Common patterns
 
 ### Setting up your project

From 5ed148c952963610973eb2462cd90322b605a77a Mon Sep 17 00:00:00 2001
From: Nikolas Burk <nikolas.burk@gmail.com>
Date: Wed, 17 Sep 2025 12:25:20 +0200
Subject: [PATCH 07/11] revert changes to prisma config

---
 .../325-prisma-config-reference.mdx           | 69 +++++--------------
 1 file changed, 19 insertions(+), 50 deletions(-)

diff --git a/content/200-orm/500-reference/325-prisma-config-reference.mdx b/content/200-orm/500-reference/325-prisma-config-reference.mdx
index 1624180ee1..904f8f516f 100644
--- a/content/200-orm/500-reference/325-prisma-config-reference.mdx
+++ b/content/200-orm/500-reference/325-prisma-config-reference.mdx
@@ -12,7 +12,6 @@ The Prisma Config file configures the Prisma CLI, including subcommands like `mi
 You can define your config in either of two ways:
 
 - Using the `defineConfig` helper:
-
   ```ts
   import path from "node:path";
   import { defineConfig } from "prisma/config";
@@ -27,12 +26,11 @@ You can define your config in either of two ways:
     },
     typedSql: {
       path: path.join("db", "queries"),
-    },
+    }
   });
   ```
 
 - Using TypeScript's `satisfies` operator with the `PrismaConfig` type:
-
   ```ts
   import path from "node:path";
   import type { PrismaConfig } from "prisma";
@@ -47,7 +45,7 @@ You can define your config in either of two ways:
     },
     typedSql: {
       path: path.join("db", "queries"),
-    },
+    }
   } satisfies PrismaConfig;
   ```
 
@@ -59,18 +57,18 @@ Here is a simplified version of the `PrismaConfig` type:
 export declare type PrismaConfig = {
   // Whether features with an unstable API are enabled.
   experimental: {
-    adapter: true;
-    externalTables: true;
-    studio: true;
-  };
+    adapter: true,
+    externalTables: true,
+    studio: true,
+  },
 
   // The path to the schema file, or path to a folder that shall be recursively searched for *.prisma files.
   schema?: string;
 
-  // Configuration for the driver adapter used for Prisma CLI.
+  // The Driver Adapter used for Prisma CLI.
   adapter?: () => Promise<SqlMigrationAwareDriverAdapterFactory>;
 
-  // Configuration for Prisma Studio.
+  // The configuration for Prisma Studio.
   studio?: {
     adapter: () => Promise<SqlMigrationAwareDriverAdapterFactory>;
   };
@@ -91,15 +89,6 @@ export declare type PrismaConfig = {
   typedSql?: {
     path: string;
   };
-
-  // Configuration to specify how the CLI should connect to the DB.
-  engine: "classic" | "js";
-
-  // Configuration of your database connection details.
-  datasource: {
-    url: string;
-    shadowDatabaseUrl?: string;
-  };
 };
 ```
 
@@ -109,13 +98,14 @@ Prisma Config files can be named as `prisma.config.*` or `.config/prisma.*` with
 
 :::tip[Recommendation]
 
-- Use **`prisma.config.ts`** for small TypeScript projects.
-- Use **`.config/prisma.ts`** for larger TypeScript projects with multiple configuration files (following the [`.config` directory proposal](https://github.com/pi0/config-dir)).
+- Use **`prisma.config.ts`** for small TypeScript projects.  
+- Use **`.config/prisma.ts`** for larger TypeScript projects with multiple configuration files (following the [`.config` directory proposal](https://github.com/pi0/config-dir)).  
 
 :::
 
 ## Options reference
 
+
 ### `schema`
 
 Configures how Prisma ORM locates and loads your schema file(s). Can be a file or folder path. Relative paths are resolved relative to the `prisma.config.ts` file location. See [here](/orm/prisma-schema/overview/location#multi-file-prisma-schema) for more info about schema location options.
@@ -128,8 +118,8 @@ Configures how Prisma ORM locates and loads your schema file(s). Can be a file o
 
 A function that returns a Prisma driver adapter instance which is used by the Prisma CLI to run migrations. The function should return a `Promise` that resolves to a valid Prisma driver adapter.
 
-| Property  | Type                                                   | Required | Default |
-| --------- | ------------------------------------------------------ | -------- | ------- |
+| Property          | Type                                                           | Required | Default |
+| ----------------- | -------------------------------------------------------------- | -------- | ------- |
 | `adapter` | `() => Promise<SqlMigrationAwareDriverAdapterFactory>` | No       | none    |
 
 Example using the Prisma ORM D1 driver adapter:
@@ -144,7 +134,7 @@ import "dotenv/config";
 
 export default {
   experimental: {
-    adapter: true,
+    adapter: true
   },
   schema: path.join("prisma", "schema.prisma"),
   async adapter() {
@@ -186,7 +176,7 @@ import type { PrismaConfig } from "prisma";
 
 export default {
   experimental: {
-    studio: true,
+    studio: true
   },
   studio: {
     adapter: async (env: Env) => {
@@ -229,7 +219,7 @@ export default defineConfig({
 });
 ```
 
-Learn more about the [`externalTables` feature here](/orm/prisma-schema/data-model/externally-managed-tables).
+Learn more about the [`externalTables` feature here](/orm/prisma-schema/data-model/externally-managed-tables). 
 
 ### `migrations.path`
 
@@ -287,7 +277,7 @@ export default defineConfig({
 });
 ```
 
-Learn more about the [`externalTables` feature here](/orm/prisma-schema/data-model/externally-managed-tables).
+Learn more about the [`externalTables` feature here](/orm/prisma-schema/data-model/externally-managed-tables). 
 
 ### `views.path`
 
@@ -340,28 +330,6 @@ Failed to load config file "~" as a TypeScript/JavaScript module. Error: Error:
 
 :::
 
-### `engine`
-
-Determines whether you want to configure the database connection details via the `datasource` or an `adapter`.
-
-| Property | Type                | Required | Default |
-| -------- | ------------------- | -------- | ------- |
-| `engine` | `"classic" \| "js"` | No       | none    |
-
-Note that:
-
-- if you're using `"classic"`, you must specify a `datasource` objedct with a `url`
-- if you're using `"js"`, you must provide an `adapter` function
-
-### `datasource`
-
-Defines the database connection details. Only valid when `engine` is set to `"classic"`.
-
-| Property                       | Type     | Required | Default |
-| ------------------------------ | -------- | -------- | ------- |
-| `datasource.url`               | `string` | Yes      | none    |
-| `datasource.shadowDatabaseUrl` | `string` | No       | none    |
-
 ## Common patterns
 
 ### Setting up your project
@@ -441,6 +409,7 @@ Prisma CLI commands such as `prisma validate` or `prisma migrate` use `prisma.co
 - Paths defined in the config file (e.g., `schema`, `migrations`) are always resolved **relative to the location of the config file**, not where you run the CLI command from.
 - The CLI must first **find the config file** itself, which depends on how Prisma is installed and the package manager used.
 
+
 ### Behavior with `pnpm prisma`
 
 When Prisma is installed locally and run via `pnpm prisma`, the config file is detected automatically whether you run the command from the project root or a subdirectory.
@@ -517,4 +486,4 @@ You can specify a custom location for your config file when running Prisma CLI c
 
 ```terminal
 prisma validate --config ./path/to/myconfig.ts
-```
+```
\ No newline at end of file

From 4703058aa8cf26a2cec819eb8474c3662d0dea8b Mon Sep 17 00:00:00 2001
From: Nikolas Burk <nikolas.burk@gmail.com>
Date: Wed, 1 Oct 2025 11:38:27 +0200
Subject: [PATCH 08/11] remove note about no login for local ppg management in
 vs code

---
 content/200-orm/800-more/350-ai-tools/100-cursor.mdx   | 2 +-
 content/200-orm/800-more/350-ai-tools/200-tabnine.mdx  | 2 +-
 content/200-orm/800-more/350-ai-tools/300-windsurf.mdx | 2 +-
 content/250-postgres/1100-integrations/500-vscode.mdx  | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/200-orm/800-more/350-ai-tools/100-cursor.mdx b/content/200-orm/800-more/350-ai-tools/100-cursor.mdx
index f2d6c6a49f..9d8275a356 100644
--- a/content/200-orm/800-more/350-ai-tools/100-cursor.mdx
+++ b/content/200-orm/800-more/350-ai-tools/100-cursor.mdx
@@ -528,7 +528,7 @@ With its built-in database management interface, the [Prisma VS Code extension](
 
 The UI enables the following workflows:
 
-- Authenticate with the [Prisma Console](https://console.prisma.io) (not required for local Prisma Postgres workflows)
+- Authenticate with the [Prisma Console](https://console.prisma.io)
 - View, create and delete Prisma Postgres instances (local & remote)
 - "Push to cloud": Easily deploy a local Prisma Postgres instance
 - View and edit data via an embedded Prisma Studio
diff --git a/content/200-orm/800-more/350-ai-tools/200-tabnine.mdx b/content/200-orm/800-more/350-ai-tools/200-tabnine.mdx
index af2e38a5d6..63c470a872 100644
--- a/content/200-orm/800-more/350-ai-tools/200-tabnine.mdx
+++ b/content/200-orm/800-more/350-ai-tools/200-tabnine.mdx
@@ -465,7 +465,7 @@ With its built-in database management interface, the [Prisma VS Code extension](
 
 The UI enables the following workflows:
 
-- Authenticate with the [Prisma Console](https://console.prisma.io) (not required for local Prisma Postgres workflows)
+- Authenticate with the [Prisma Console](https://console.prisma.io)
 - View, create and delete Prisma Postgres instances (local & remote)
 - "Push to cloud": Easily deploy a local Prisma Postgres instance
 - View and edit data via an embedded Prisma Studio
diff --git a/content/200-orm/800-more/350-ai-tools/300-windsurf.mdx b/content/200-orm/800-more/350-ai-tools/300-windsurf.mdx
index 1ae8c08775..b312ff8758 100644
--- a/content/200-orm/800-more/350-ai-tools/300-windsurf.mdx
+++ b/content/200-orm/800-more/350-ai-tools/300-windsurf.mdx
@@ -552,7 +552,7 @@ With its built-in database management interface, [the Prisma VS Code extension](
 
 The UI enables the following workflows:
 
-- Authenticate with the [Prisma Console](https://console.prisma.io) (not required for local Prisma Postgres workflows)
+- Authenticate with the [Prisma Console](https://console.prisma.io)
 - View, create and delete Prisma Postgres instances (local & remote)
 - "Push to cloud": Easily deploy a local Prisma Postgres instance
 - View and edit data via an embedded Prisma Studio
diff --git a/content/250-postgres/1100-integrations/500-vscode.mdx b/content/250-postgres/1100-integrations/500-vscode.mdx
index b6f1b972fe..618e4731b9 100644
--- a/content/250-postgres/1100-integrations/500-vscode.mdx
+++ b/content/250-postgres/1100-integrations/500-vscode.mdx
@@ -19,7 +19,7 @@ The Prisma VS Code extension includes a dedicated UI to manage Prisma Postgres i
 
 The UI enables the following workflows:
 
-- Authenticate with the [Prisma Console](https://console.prisma.io) (not required for local Prisma Postgres workflows)
+- Authenticate with the [Prisma Console](https://console.prisma.io)
 - View, create and delete  Prisma Postgres instances (local & remote)
 - "Push to cloud": Easily deploy a local Prisma Postgres instance
 - View and edit data via an embedded Prisma Studio

From 64ef7ed666a4b7b4f958ac9d03baa385ffa2a112 Mon Sep 17 00:00:00 2001
From: Nikolas Burk <nikolas.burk@gmail.com>
Date: Tue, 7 Oct 2025 10:46:52 +0200
Subject: [PATCH 09/11] revise connection details

---
 .../115-import-from-existing-database-mysql.mdx        | 10 +++++-----
 .../500-reference/325-prisma-config-reference.mdx      | 10 ++++++----
 .../100-introduction/200-getting-started.mdx           | 10 +++++-----
 .../300-database/650-direct-connections.mdx            | 10 +++++-----
 4 files changed, 21 insertions(+), 19 deletions(-)

diff --git a/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx b/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx
index bb43aeb438..52c8461fb9 100644
--- a/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx
+++ b/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx
@@ -41,11 +41,11 @@ Follow these steps to create a new Prisma Postgres database:
 
 Once your database was provisioned, find your direct Prisma Postgres connection string:  
 
-1. Open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
-1. Navigate to a environment with an active Prisma Postgres instance
-1. Click the **Dashboard** tab in the project's sidenav
-1. Find the **Connect to your database** card and click the **Connect** button
-1. Copy the connection string starting with `postgres://`, this is your direct connection string
+1. Navigate to your active Prisma Postgres instance.
+1. Click the **API Keys** tab in the project's sidenav.
+1. Click the **Create API key** button.
+1. In the popup, provide a **Name** for the API key and click **Create**.
+1. Copy the connection string starting with `postgres://`, this is your direct connection string.
 
 Save the connection string, you'll need it in the next step.
 
diff --git a/content/200-orm/500-reference/325-prisma-config-reference.mdx b/content/200-orm/500-reference/325-prisma-config-reference.mdx
index 904f8f516f..73d50374ad 100644
--- a/content/200-orm/500-reference/325-prisma-config-reference.mdx
+++ b/content/200-orm/500-reference/325-prisma-config-reference.mdx
@@ -55,11 +55,12 @@ Here is a simplified version of the `PrismaConfig` type:
 
 ```ts
 export declare type PrismaConfig = {
+
   // Whether features with an unstable API are enabled.
   experimental: {
-    adapter: true,
-    externalTables: true,
-    studio: true,
+    adapter: boolean;
+    externalTables: boolean;
+    studio: boolean;
   },
 
   // The path to the schema file, or path to a folder that shall be recursively searched for *.prisma files.
@@ -68,7 +69,7 @@ export declare type PrismaConfig = {
   // The Driver Adapter used for Prisma CLI.
   adapter?: () => Promise<SqlMigrationAwareDriverAdapterFactory>;
 
-  // The configuration for Prisma Studio.
+  // Configuration for Prisma Studio.
   studio?: {
     adapter: () => Promise<SqlMigrationAwareDriverAdapterFactory>;
   };
@@ -89,6 +90,7 @@ export declare type PrismaConfig = {
   typedSql?: {
     path: string;
   };
+  
 };
 ```
 
diff --git a/content/250-postgres/100-introduction/200-getting-started.mdx b/content/250-postgres/100-introduction/200-getting-started.mdx
index c190dbba22..ac3fc926fd 100644
--- a/content/250-postgres/100-introduction/200-getting-started.mdx
+++ b/content/250-postgres/100-introduction/200-getting-started.mdx
@@ -54,11 +54,11 @@ prisma generate --no-engine
 You can access Prisma Postgres with any ORM or database tool of your choice via [direct TCP connections](/postgres/database/direct-connections).
 
 In order to get a direct TCP connection string, you need to:
-1. Open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
-1. Navigate to a environment with an active Prisma Postgres instance
-1. Click the **Dashboard** tab in the project's sidenav
-1. Find the **Connect to your database** card and click the **Connect** button
-1. Copy the connection string starting with `postgres://`, this is your direct connection string
+1. Navigate to your active Prisma Postgres instance.
+1. Click the **API Keys** tab in the project's sidenav.
+1. Click the **Create API key** button.
+1. In the popup, provide a **Name** for the API key and click **Create**.
+1. Copy the connection string starting with `postgres://`, this is your direct connection string.
 
 Once you have the connection string, you can follow the setup docs for PostgreSQL of any ORM or database tool:
 
diff --git a/content/250-postgres/300-database/650-direct-connections.mdx b/content/250-postgres/300-database/650-direct-connections.mdx
index fc3d7a6300..109921ef1b 100644
--- a/content/250-postgres/300-database/650-direct-connections.mdx
+++ b/content/250-postgres/300-database/650-direct-connections.mdx
@@ -16,11 +16,11 @@ If you connect to it via another tool, you can do so with a [direct connection s
 
 In order to get a direct connection string, you need to:
 
-1. Open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
-1. Navigate to a environment with an active Prisma Postgres instance
-1. Click the **Dashboard** tab in the project's sidenav
-1. Find the **Connect to your database** card and click the **Connect** button
-1. Copy the connection string starting with `postgres://`, this is your direct connection string
+1. Navigate to your active Prisma Postgres instance.
+1. Click the **API Keys** tab in the project's sidenav.
+1. Click the **Create API key** button.
+1. In the popup, provide a **Name** for the API key and click **Create**.
+1. Copy the connection string starting with `postgres://`, this is your direct connection string.
 
 ## Connection string
 

From c18893558337dece5df60e686a0c424dd70769a9 Mon Sep 17 00:00:00 2001
From: Nikolas <nikolas.burk@gmail.com>
Date: Wed, 8 Oct 2025 14:16:44 +0200
Subject: [PATCH 10/11] Apply suggestion from @nikolasburk

---
 .../250-postgres/100-introduction/250-overview.mdx   | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/content/250-postgres/100-introduction/250-overview.mdx b/content/250-postgres/100-introduction/250-overview.mdx
index e0dcda86a1..e3d8035024 100644
--- a/content/250-postgres/100-introduction/250-overview.mdx
+++ b/content/250-postgres/100-introduction/250-overview.mdx
@@ -19,11 +19,13 @@ It supports the following workflows:
 
 You can view the following usage metrics in your Console Dashboard:
 
-- Cumulative usage over time
-- Total count of requests
-- Storage used per project in your workspace
-- Operations used per day
-- Databases per project
+- Key metrics
+    - Estimated upcoming invoice
+    - Total storage used
+    - Total DBs
+- Overall usage
+    - Cumulative operations
+    - Operations per day
 
 ## Billing 
 

From 278c740339c7a2489bf1d9316873c34e848c7b4d Mon Sep 17 00:00:00 2001
From: Nikolas <nikolas.burk@gmail.com>
Date: Wed, 8 Oct 2025 14:17:35 +0200
Subject: [PATCH 11/11] Apply suggestion from @nikolasburk

---
 content/250-postgres/300-database/650-direct-connections.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/250-postgres/300-database/650-direct-connections.mdx b/content/250-postgres/300-database/650-direct-connections.mdx
index 879de63355..d020e30f5b 100644
--- a/content/250-postgres/300-database/650-direct-connections.mdx
+++ b/content/250-postgres/300-database/650-direct-connections.mdx
@@ -16,6 +16,7 @@ If you connect to it via another tool, you can do so with a [direct connection s
 
 In order to get a direct connection string, you need to:
 
+1. Open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
 1. Navigate to your active Prisma Postgres instance.
 1. Click the **API Keys** tab in the project's sidenav.
 1. Click the **Create API key** button.