# Known limitations (/docs/compute/limitations)

> 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.

What the Prisma Compute beta can and can't do.

Location: Compute > Known limitations

Prisma Compute is in [Public Beta](https://www.prisma.io/docs/console/more/feature-maturity#public-beta). This page lists what the beta can and can't do.

## CLI [#cli]

* The package is `@prisma/cli`; the executable is `prisma-cli`. The quickest way to run it is `npx @prisma/cli@latest <command>` (or `bunx`/`pnpm dlx`), with Node.js 22.12 or newer for `npx` and `pnpm`.
* The command groups are `version`, `init`, `agent`, `auth`, `project` (including `project env`), `git`, `branch`, `build`, `database`, and `app`. There is no `schema` or `migrate` command, and no product-branded `compute` namespace.
* Committed configuration lives in [`prisma.compute.ts`](https://www.prisma.io/docs/compute/configuration) (or `prisma.compute.json`). `.prisma/local.json` is a gitignored local pin of the workspace and project, and `PRISMA_PROJECT_ID` / `PRISMA_APP_ID` override it for CI.

## Projects and branches [#projects-and-branches]

* Project setup is explicit: `--yes` won't create or choose a project for you.
* The first branch in a project is production; the rest are preview by default.
* `branch list` inspects branches; it doesn't create remote state.
* Deleting a branch on GitHub can tear down the matching platform branch, but production and default branches are always left alone.

## Frameworks and runtimes [#frameworks-and-runtimes]

* `app deploy --framework` accepts `nextjs`, `nuxt`, `astro`, `hono`, `nestjs`, `tanstack-start`, `custom`, and `bun`.
* `app build --build-type` accepts `auto`, `nextjs`, `nuxt`, `astro`, `nestjs`, `tanstack-start`, `custom`, and `bun`.
* Use `--entry` for Bun, or whenever detection needs a hand.

## Environment variables [#environment-variables]

* Values are write-only: once saved, they are never returned by any surface, and there is no command to pull them into a local `.env`.
* `project env list` returns keys and metadata only.
* Values resolve at deploy time; changing one doesn't mutate existing deployments or trigger a redeploy.
* Production variables can't be branch-scoped.
* Keys must match `[A-Z_][A-Z0-9_]*`; values are non-empty, up to 8 KB.

## GitHub [#github]

* GitHub is the only supported provider, and a project connects to one repository.
* Auto-deploy supports multiple apps declared in `prisma.compute.ts`: one push build fans out into a targeted build per app. CI with a service token remains available when you need full control.
* The webhook path is branch- and push-driven. There are no PR comments or PR status automation.

## Domains [#domains]

* Custom domains are production-only and CNAME-based: they attach to the default (production) branch, and the app needs a promoted deployment first.
* Up to 3 custom domains per app.
* There is no workspace-wide domain list in the CLI.

## Logs [#logs]

* `app logs` streams the live deployment or a specific one.
* It returns `FEATURE_UNAVAILABLE` when the platform can't serve logs for the resolved deployment.
* Logs stream in time-bounded segments, so direct API clients should expect to reconnect.

## Runtime [#runtime]

* This release focuses on HTTP apps. Background work between requests is supported through the `@prisma/compute` keep-awake primitives; see [Keeping instances awake](https://www.prisma.io/docs/compute/keeping-instances-awake). Cron scheduling, a persistent filesystem, and edge runtimes are not part of it.
* WebSocket servers are not currently a supported Public Beta capability. `waitUntil` and `KeepAwakeGuard` only prevent an instance from scaling to zero; they do not change connection-lifetime limits or guarantee continuity through restarts or deployments.
* No multi-region deployments. Each app lives in one region, chosen at creation with `app deploy --region`: `us-east-1` (the default), `us-west-1`, `eu-west-3`, `eu-central-1`, `ap-northeast-1`, or `ap-southeast-1`.
* Not yet recommended for mission-critical or heavy production workloads.
* Exact limits, pricing, retention policies, and runtime guardrails can still change before general availability.

## Databases and migrations [#databases-and-migrations]

* These docs cover app deploy and runtime config only: not database creation, schema migrations, or data cloning.
* Don't assume production data is copied into preview branches.
* Don't assume production migrations run automatically on deploy.
* Pass database URLs and other runtime config through [environment variables](https://www.prisma.io/docs/compute/environment-variables).

## Next steps [#next-steps]

* [FAQ](https://www.prisma.io/docs/compute/faq): quick answers to common questions.
* [Get started with `@prisma/cli`](https://www.prisma.io/docs/compute/getting-started): your first deploy.

## Related pages

- [`@prisma/cli`](https://www.prisma.io/docs/compute/getting-started): Deploy your first app to Prisma Compute with the @prisma/cli beta package, then learn the variations you'll need next.
- [`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): Every @prisma/cli command, flag, environment variable, and error code for Prisma Compute.
- [`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.
- [`Deployments`](https://www.prisma.io/docs/compute/deployments): Build, deploy, inspect, promote, and roll back app deployments on Prisma Compute.