# 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 quickest way to run the CLI is `npx prisma@latest <command>` (or `bunx`/`pnpm dlx`), with Node.js 22.18 or newer.
* The platform command groups are `auth`, `project` (including `project env`), `postgres`, `bucket`, `branch`, `git`, `service` (including `service version` and `service domain`), and `agent`, plus the root-level [`dev`](https://www.prisma.io/docs/cli/dev) and [`deploy`](https://www.prisma.io/docs/cli/deploy) verbs for Composer apps. The same binary also carries the [Prisma 8 data commands](https://www.prisma.io/docs/cli) (`contract`, `db`, `migration`). There is no `compute` namespace: Compute is managed through the resource groups above.
* Commands are targeted by parameters, not ambient state: the subject resource is the first positional argument, and there is no interactive picker. A missing target fails with a structured error (exit 2) before any network call.
* There is no committed compute config file. Builds detect the framework from the repository, and a Composer app describes itself in its module. `.prisma/local.json` is gitignored and only stores your local link to the workspace and project. In CI, set `PRISMA_PROJECT_ID` / `PRISMA_SERVICE_ID` to override the linked project and service.

## 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]

* Push-triggered builds detect `nextjs`, `nuxt`, `astro`, `hono`, `nestjs`, `tanstack-start`, and `bun`.
* A [Prisma Composer](https://www.prisma.io/docs/composer) app declares its build explicitly per service (the `node` and `nextjs` build adapters), so detection is not involved.

## 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 does not mutate existing versions 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.
* CI with a service token remains available when you need full control over deploys.
* 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 service needs a promoted version first.
* Up to 3 custom domains per service.
* There is no workspace-wide domain list in the CLI.

## Logs [#logs]

* `service logs <service>` reads a version's logs (`--version-id <id>` selects one); build output for a deploy is available in the Console.
* It returns `FEATURE_UNAVAILABLE` when the platform can't serve logs for the resolved version.
* Logs stream in time-bounded segments, so direct API clients should expect to reconnect.

## Runtime [#runtime]

* This release focuses on HTTP services. 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 service lives in one region, chosen at creation (`service create --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 deployment and runtime config only: not schema migrations or data cloning. Databases are managed with the [`postgres` commands](https://www.prisma.io/docs/cli/postgres).
* 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 the Prisma CLI](https://www.prisma.io/docs/compute/getting-started): your first deploy.

## 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.
- [`Deploy Button`](https://www.prisma.io/docs/compute/deploy-button): Add a Deploy with Prisma button that copies a public Composer repository and starts a Composer-managed deployment.
- [`Deploy on push`](https://www.prisma.io/docs/compute/deploy-on-push): Graduate a Composer app from manual deploys to a Git workflow, with production deploys on push and an isolated preview environment per branch.
- [`Deployments`](https://www.prisma.io/docs/compute/deployments): How deploys create service versions on Prisma Compute, and how to inspect, promote, roll back, start, and stop them.