prisma-platform-core-concepts

Push a git branch with the GitHub integration connected, or run prisma deploy module.ts --stage <name> from the CLI. The branch itself is the environment and gets its own services, databases, and buckets automatically.

A preview branch that declares a database in the module gets a fresh, empty Prisma Postgres database wired in as a branch-scoped DATABASE_URL. Schema comes from committed migrations; production data never carries over.

No, environment variable values are write-only by design. Listing shows names and scopes only, and no API returns values; to change a value you replace it and re-deploy since variables resolve at deploy time.

Preview environments are torn down when their upstream git branch is deleted, or reclaimed automatically when idle and unpinned. Push or deploy the branch again to re-create it, but the database starts empty.

The Compute runtime has no global Temporal, so reading ORM DateTime columns throws RUNTIME.TEMPORAL_UNAVAILABLE. Add the temporal-polyfill dependency and import it at the service entry, or use the *String column types.

The CLI cannot create or delete branches directly, retry failed builds, read environment variable values, or rename buckets. Branches are created by pushing or deploying a stage and removed by deleting the git branch.