# Deployments (/docs/compute/deployments) > For the complete Prisma documentation index, see [llms.txt](https://www.prisma.io/docs/llms.txt). A markdown version of any docs page is available by appending `.md` to its URL. How deployments are created on Prisma Compute, and how to inspect, promote, roll back, start, and stop them. Location: Compute > Deployments A deployment is one built version of your app. Deployments live inside a [branch](https://www.prisma.io/docs/compute/branching), and the live deployment is the one currently serving traffic. ## Where deployments come from [#where-deployments-come-from] Deployments are created three ways: * **A git push.** After you [connect a GitHub repository](https://www.prisma.io/docs/compute/github), pushing a branch builds and deploys it: the default Git branch deploys to production, and every other branch gets an isolated preview. * **The [Console](https://pris.ly/pdp).** Trigger a build and deployment from the browser. * **[Prisma Composer](https://www.prisma.io/docs/composer).** `composer deploy` does not build your services; it assembles the services you have already built and provisions them. This is the CLI-driven path for multi-service apps. The unified CLI does not have a standalone `deploy` command for a single service. Use its `service` commands to manage the deployments those flows create. During the beta, the earlier CLI (`@prisma/cli@latest`) still offers an `app deploy` command that builds and deploys a single service from your terminal in one step. The same commands below manage the deployments it creates. ## Inspect deployments [#inspect-deployments] #### bun ```bash bunx prisma@next service show --service web bunx prisma@next service open --service web bunx prisma@next service deployment list --service web bunx prisma@next service deployment show dep_123 ``` #### pnpm ```bash pnpm dlx prisma@next service show --service web pnpm dlx prisma@next service open --service web pnpm dlx prisma@next service deployment list --service web pnpm dlx prisma@next service deployment show dep_123 ``` #### yarn ```bash yarn dlx prisma@next service show --service web yarn dlx prisma@next service open --service web yarn dlx prisma@next service deployment list --service web yarn dlx prisma@next service deployment show dep_123 ``` #### npm ```bash npx prisma@next service show --service web npx prisma@next service open --service web npx prisma@next service deployment list --service web npx prisma@next service deployment show dep_123 ``` `service show` describes the service and its current deployment, `service open` opens its URL, `deployment list` lists the deployment history, and `deployment show` shows one deployment in detail. ## Build logs [#build-logs] Each deployment starts as a build. Stream a build's logs, live or after the fact: #### bun ```bash bunx prisma@next build logs bld_123 --follow ``` #### pnpm ```bash pnpm dlx prisma@next build logs bld_123 --follow ``` #### yarn ```bash yarn dlx prisma@next build logs bld_123 --follow ``` #### npm ```bash npx prisma@next build logs bld_123 --follow ``` `--follow` keeps the connection open while the build runs; `--cursor ` resumes from a cursor a previous run reported. Build ids appear in `service show`, `service deployment show`, and the Console. ## Promote and roll back [#promote-and-roll-back] Promote a preview deployment to production: #### bun ```bash bunx prisma@next service deployment promote dep_123 --service web ``` #### pnpm ```bash pnpm dlx prisma@next service deployment promote dep_123 --service web ``` #### yarn ```bash yarn dlx prisma@next service deployment promote dep_123 --service web ``` #### npm ```bash npx prisma@next service deployment promote dep_123 --service web ``` Promotion rebuilds the deployment with **production** environment variables and makes the result live behind the service's endpoint. The rebuild is what lets a deployment built for a preview branch pick up production environment variables on its way to production. Roll back production to a previous deployment. Rollback reuses an existing build, so there is no rebuild step between you and a known-good state: #### bun ```bash bunx prisma@next service deployment rollback --service web bunx prisma@next service deployment rollback --service web --to dep_123 ``` #### pnpm ```bash pnpm dlx prisma@next service deployment rollback --service web pnpm dlx prisma@next service deployment rollback --service web --to dep_123 ``` #### yarn ```bash yarn dlx prisma@next service deployment rollback --service web yarn dlx prisma@next service deployment rollback --service web --to dep_123 ``` #### npm ```bash npx prisma@next service deployment rollback --service web npx prisma@next service deployment rollback --service web --to dep_123 ``` Without `--to`, rollback targets the deployment before the live one. ## Start, stop, delete [#start-stop-delete] #### bun ```bash bunx prisma@next service deployment stop dep_123 bunx prisma@next service deployment start dep_123 bunx prisma@next service deployment delete dep_123 ``` #### pnpm ```bash pnpm dlx prisma@next service deployment stop dep_123 pnpm dlx prisma@next service deployment start dep_123 pnpm dlx prisma@next service deployment delete dep_123 ``` #### yarn ```bash yarn dlx prisma@next service deployment stop dep_123 yarn dlx prisma@next service deployment start dep_123 yarn dlx prisma@next service deployment delete dep_123 ``` #### npm ```bash npx prisma@next service deployment stop dep_123 npx prisma@next service deployment start dep_123 npx prisma@next service deployment delete dep_123 ``` Stopping a deployment takes it out of service without deleting its artifact; starting it brings it back. Deleting a deployment removes it and the artifact it holds, after confirmation. ## Remove a service [#remove-a-service] #### bun ```bash bunx prisma@next service remove --service web ``` #### pnpm ```bash pnpm dlx prisma@next service remove --service web ``` #### yarn ```bash yarn dlx prisma@next service remove --service web ``` #### npm ```bash npx prisma@next service remove --service web ``` This removes the service from the selected branch (your active Git branch, unless you pass `--branch`). Pass `--yes` to skip the confirmation prompt. ## Next steps [#next-steps] * [Environment variables](https://www.prisma.io/docs/compute/environment-variables): persist config across deploys. * [GitHub integration](https://www.prisma.io/docs/compute/github): the push-to-deploy flow in detail. * [Domains](https://www.prisma.io/docs/compute/domains): point a custom domain at production. * [Prisma Composer](https://www.prisma.io/docs/composer): CLI-driven deploys for multi-service apps. ## Related pages - [`Alchemy`](https://www.prisma.io/docs/compute/alchemy): Provision Prisma Postgres and deploy applications to Prisma Compute in one TypeScript stack. - [`Branching`](https://www.prisma.io/docs/compute/branching): Branches are isolated environments that map to your Git branches, so preview work never touches production. - [`CLI reference`](https://www.prisma.io/docs/compute/cli-reference): Where the Prisma Compute commands in the unified Prisma CLI are documented. - [`Configuration`](https://www.prisma.io/docs/compute/configuration): Declare your deployable app in a typed prisma.compute.ts file so deploys are reproducible and monorepos work, without re-passing flags every time. - [`Domains`](https://www.prisma.io/docs/compute/domains): Point a custom domain at a production app and the platform verifies DNS and provisions TLS for you.