← Back to Changelog

Set up Prisma Next with new guides and debug failed Prisma Compute builds

July 3, 2026
PrismaPrisma NextPrisma ComputePrisma Postgres

Prisma Next publishes setup guides for new and existing projects on PostgreSQL and MongoDB, and extends the schema language with scalar list fields and MongoDB enums.

Prisma Compute (Public Beta) now sends an email when a build fails, exposes build logs through the Management API, and fails stuck build steps with a per-step timeout instead of hanging indefinitely.

Highlights

DocsPrisma Next setup guides are now available

Trying Prisma Next meant piecing the setup together from scattered posts. The docs now have setup guides covering new projects and adding Prisma Next to an existing project, for PostgreSQL and MongoDB.

Note: Prisma Next is in Early Access. Scope and behavior may still change.

Read the Prisma Next setup guides for installation steps. For background on the TypeScript rewrite, read The Next Evolution of Prisma ORM.

NewPrisma Compute build failures now include logs and timeout reasons

A failing build used to mean re-running the deploy and watching. Prisma Compute now sends an email when a build fails, exposes complete build logs through the Management API (with a pointer on the deploy check run), and fails stuck build steps with a per-step timeout instead of hanging indefinitely.

Read the Prisma Compute docs for how to fetch build logs from the Management API.

Prisma Next

Prisma Next adds more schema coverage for MongoDB, browser-safe imports for generated types and helpers, and language server improvements for editing schemas.

New
  • Prisma Next scalar list fields are now supported in schemas, migrations, and type inference. (prisma/prisma-next#870)
  • Prisma Next now supports MongoDB enums in schemas, database validators, and typed reads. (prisma/prisma-next#834)
  • Prisma Next now provides browser-safe static imports through @prisma-next/{target}/static for types and helpers used in browser code. (prisma/prisma-next#888)
Improved

Scalar list fields are authored directly in the schema:

model Post {
  id   String   @id @default(uuid())
  tags String[]
}

Types and helpers that are safe to use in browser code are imported from the static entry point:

import type { Post } from "@prisma-next/postgresql/static";

Prisma Compute

Prisma Compute adds deploy region configuration, consistent deployment terminology, Prisma Console navigation updates, and preview branch cleanup improvements.

New
  • Prisma Compute deploy regions can now be configured in prisma.compute.ts.
Improved
  • Prisma Console now has redesigned navigation and a new project overview view for Prisma Compute projects.
  • Prisma Compute now consistently uses deployments in the Prisma Console and the Management API where it used to mix in versions, matching the /v1/deployments API surface. Action recommended: update docs, scripts, or internal tooling that still refers to Prisma Compute versions.
  • Prisma Compute preview branch teardown now also de-provisions the associated database.
// prisma.compute.ts
import { defineConfig } from "@prisma/compute";

export default defineConfig({
  region: "eu-central-1",
});

Deprecations

  • Prisma Compute custom-domain API responses now include appId. The existing computeServiceId field is deprecated and will continue to be returned during the migration period. Action required: update code that reads computeServiceId from custom-domain API responses to read appId instead.

Fixes and improvements

Prisma Compute

Fixed
  • Prisma Compute Astro deploys no longer miss runtime dependencies at build time.

Prisma Next

Fixed
  • Prisma Next aggregation reads with $project and $addFields decode into typed results instead of returning raw BSON. (prisma/prisma-next#897)

Guides and articles


Need help applying these changes in production? Prisma Enterprise Support can help with schema design, performance, security, and compliance.