# Limitations

What Prisma Composer does not do yet, so you can name the gap instead of working around it blind.

Prisma Composer is in [Early Access](/guides/more-3-console-more-feature-maturity#early-access). This page lists what it does not do yet, so you can plan around a gap instead of discovering it mid-build. If something you need is missing here and below, check the [examples](https://github.com/prisma/composer/tree/main/examples) and design docs in the [Composer repository](https://github.com/prisma/composer), then file an issue there rather than guessing at an API.

## Contracts and communication

- **RPC over HTTP is the only contract kind.** No gRPC, WebSocket, or streaming contracts.
- **No in-memory contract bindings.** A dependency cannot yet be wired to a co-located handler without HTTP; use [`bootstrapService`](/guides/workflows-testing#integration-tests-bootstrapservice) with a loopback fake in tests.

## Deploys and auth

- **No interactive login for deploys.** Deploys authenticate only via a static `PRISMA_SERVICE_TOKEN`; there is no browser flow.
- **Deploys do not build.** `deploy` assembles your built output; the build is always yours to run first.
- **The `effect` family must be pinned** in your app's `package.json` until an upstream dependency fixes its version ranges; see [Getting started](/guides/introduction-4-getting-started#1-set-up-the-project). Every Composer command checks this and stops with a fix-naming error when the pin is missing.

## Platforms

- **Windows is not supported yet** for local development (`dev`).
- **Node.js 22.18 or newer is required.** Composer hands your TypeScript entry file straight to Node, and earlier versions cannot run `.ts` files directly.

## Runtime behavior to design around

These are properties of running on [Prisma Compute](/guides/deploy-compute) rather than missing features; [Deploying](/guides/workflows-deploying#production-behavior) covers each with the fix:

- Compute scales to zero, so idle database connections get closed and cold calls can see `ECONNRESET`.
- A deployed RPC endpoint answers only its wired consumers; hand-rolled probes get `401`.
- Environment variables prefixed `COMPOSER_*` belong to the deploy and are rewritten on every deploy.
- Streaming responses are delivered as your service sends them, but the service has 60 seconds to send the first bytes before the ingress returns `504 Gateway Time-out`; see [Request timeout](/guides/features-2-compute-request-timeout).

## Next steps

- [Deploying](/guides/workflows-deploying): operational behavior in full.
- [Building blocks](/guides/concepts-building-blocks): what ships today, and how extensions arrive.

## Related pages

- [Authentication & Tools](./authentication-tools-index.md)
- [Build](./build-index.md)
- [Changelog](../changelog.md)
- [Concepts](./concepts-index.md)
- [Console commands](./console-commands-index.md)
- [Contract Authoring](./contract-authoring-index.md)
- [Core Concepts](./core-concepts-index.md)
- [Data Modeling](./data-modeling-index.md)
- [Database](./database-index.md)
- [DB commands](./db-commands-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.