Manage Prisma Compute apps through the API

Prisma Compute (Public Beta) services can now be managed end to end without the dashboard: the Management API gains /v1/apps and /v1/deployments surfaces with a deployment logs endpoint. The Prisma Console adds per-service environment variables, and Prisma Next schemas can declare many-to-many relations and row-level security policies.

Highlights

NewPrisma Compute apps and deployments are now in the Management API

Automating Prisma Compute meant working around dashboard-only workflows. The Management API now exposes apps and deployments as first-class surfaces, including an endpoint for fetching a deployment's logs, so scripts and agents can drive the same workflows the Prisma Console offers. The earlier route names keep working and are deprecated below.

The new surfaces cover the full lifecycle:

GET /v1/apps
GET /v1/deployments
GET /v1/deployments/{id}/logs

Read the Prisma Compute docs for the /v1/apps and /v1/deployments reference.

NewPrisma Next schemas can declare many-to-many relations and row-level security

Many-to-many relations meant hand-writing a junction table, and row-level security lived outside your schema. Prisma Next now lets you author both in Prisma Schema Language: a many-to-many relation generates the junction for you, and SELECT row-level security policies are declared in the schema, enforced, and checked so drift fails verification.

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

Shipped in prisma/prisma-next#819 and prisma/prisma-next#771.

Prisma Compute

Prisma Compute adds per-service environment variables in the Prisma Console and custom build artifacts.

New

Prisma Compute environment variables can now be managed per service from the Prisma Console, with separate production and preview values.
Prisma Compute now accepts custom build artifacts: bring your own build output instead of relying on a detected framework build.

Prisma Next

The Prisma Next language server adds diagnostics and formatting.

New

The Prisma Next language server surfaces schema symbol diagnostics as you type. (prisma/prisma-next#862)

Improved

Prisma Next schema formatting is available through the language server, not just the CLI. (prisma/prisma-next#857)

Deprecations

The Prisma Compute Management API /compute-services routes are deprecated in favor of the new /v1/apps surface. The old routes keep working during the migration period. Action required: update API clients that call /compute-services routes to use /v1/apps instead.
Prisma Compute version-scoped log routes are deprecated in favor of /v1/deployments/{id}/logs. Action required: update log-fetching scripts and tooling to the /v1/deployments/{id}/logs endpoint.

Guides and articles

Search the Prisma Docs Using Your Coding Agent: shows how to wire the Prisma docs into a coding agent's search tools.
Evolving Agentic Engineering at Prisma: describes how Prisma's engineering teams work with coding agents.
Price the Work, Not the Workflow: argues for outcome-based pricing of developer tooling.
KeepAwakeGuard in the Prisma Compute docs: documents how to keep a Prisma Compute service awake during long-running work.

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