$0
Permanent hard-capped Compute allowance, with no usage billing or payment card. Apps pause if a limit is reached.
- 1 million requests per month
- 360 GB-hours provisioned memory per month
- 4 active vCPU-hours per month
Prisma Compute
Managed TypeScript application hosting with optional Postgres provisioning and isolated branch previews.
Prisma Compute hosts TypeScript HTTP services, including Node.js-style applications running on Bun. Prisma Composer can deploy services alongside an optional Prisma Postgres database, with typed dependencies and migrations for ORM-backed
postgres() resources. With deploy-on-push configured, branches get isolated application previews and fresh Composer-declared databases rather than production-data copies. Compute also works with external databases without Prisma ORM, but database isolation and migrations then remain the developer’s responsibility.Best for
TypeScript teams deploying APIs or full-stack apps that want application releases, Postgres provisioning, and isolated previews managed through one workflow.
Watch out for
Compute runs on Bun and targets HTTP services; automatic database migrations apply only to Composer postgres() resources, not external database connections.
- Workloads
- APIs
- Backend Services
- Web Applications
- Services
- Compute
- Hosting model
- Managed
Development & Execution
Supported platform capabilities, execution environments, development technologies, deployment models, integrations, and triggers.
Runtimes
- Bun
Languages
- JavaScript
- TypeScript
Frameworks
- Astro
- Express.js
- Hono
- Next.js
- Nuxt
- TanStack Start
Capabilities
- Scale to Zero
- Deployment Rollbacks
- Preview Environments
Database support
- PostgreSQL
Deployment & packaging
- Serverless (Managed Runtime)
Integrations
- GitHub
Triggers
- HTTP Requests
Pricing
Published pricing structure, representative costs, and material billing factors.
- Starting Price
- $10/month
- Primary Billing
- Plan based
- Free Tier
- Recurring free allowances
- Commitment
- The monthly workspace base subscription covers Compute and Postgres once. Paid Compute usage is metered beyond requests included in the plan
Prisma Plans
One Prisma workspace plan includes Compute and Postgres. The base fee is paid once; these cards show Compute allowances, while Postgres operations and storage have separate meters.
$10/month
One shared workspace subscription; Compute memory, CPU and bandwidth are metered from the first unit.
- 5 million Compute requests included per month
- Additional requests and Compute resources are billed by usage
$49/month
Higher request allowance with the same Compute resource rates.
- 20 million Compute requests included per month
- Additional requests and Compute resources are billed by usage
$129/month
Largest published request allowance and Business workspace support; Compute resource rates remain unchanged.
- 100 million Compute requests included per month
- Additional requests and Compute resources are billed by usage
Prisma Compute usage Additional Usage Cost
Paid plans include monthly request allowances. Additional requests cost $1 per million; provisioned memory while running or kept awake, active CPU time, and outbound internet bandwidth are charged from the first unit. Idle scale-to-zero time and deployments are not billed as separate units.
| Resource | Billing Unit | Price |
|---|---|---|
| Requests beyond allowance | per million requests | $1 |
| Provisioned memory | per GB-hour while running | $0.006 |
| Active CPU | per vCPU-hour used | $0.064 |
| Outbound bandwidth | per GB sent to the internet | $0.025 |
Free Tier
No card requiredRecurring Free workspace allowance without a credit card or usage billing. When any Free limit is reached, apps pause until the next reset or plan upgrade. Postgres has separate Free allowances in the same workspace.
- Requests: 1 million requests per month
- Provisioned memory: 360 GB-hours per month
- Active CPU: 4 vCPU-hours per month
- Outbound bandwidth: 10 GB per month
Enterprise Pricing
Prisma offers custom pricing for higher-volume teams across its workspace products.
Billing Commitment
The monthly workspace base subscription covers Compute and Postgres once. Paid Compute usage is metered beyond requests included in the plan; memory, CPU and outbound bandwidth are billed from the first unit.
Infrastructure & Availability
Where workloads run, how deployment is scoped, and what underlying infrastructure the platform depends on.
Prisma Compute services execute in one selected application region, not across multiple regions. Prisma Compute and Prisma Postgres share the six region choices, allowing co-location by selecting the same region for each service and database; this inventory covers Compute execution only.
Application execution regions
Each Compute HTTP service runs in a customer-selected region. A single service cannot deploy across multiple regions.
Applies to
- Prisma Compute services
Deployment model
- Managed cloud
Execution
- Single Region
Placement
- Customer-Selected
Deployment scope
- Regional
Geographic availability
- North America
- 2
- Europe
- 2
- Asia Pacific
- 2
Availability footprint
- Regions
- 6
Available Regions
| Location | Area | Region ID |
|---|---|---|
| San Francisco | North America | us-west-1 |
| North Virginia | North America | us-east-1 |
| Paris | Europe | eu-west-3 |
| Frankfurt | Europe | eu-central-1 |
| Tokyo | Asia Pacific | ap-northeast-1 |
| Singapore | Asia Pacific | ap-southeast-1 |
Availability reviewed · Availability source
Resource & Execution Limits
Request response deadline
60 seconds
Time to first response byte; streams already started are not cut off by this deadline
Custom domains
3 per service
Production branch only; service must have a promoted version
Environment variable value
8 KB
Maximum per value; values are write-only and resolved at deploy time
Security & Compliance
Security Controls
- Secrets Management
- Write-only scoped environment variables Production, preview and branch scopes; applied to new deployments
- Deployment Credentials
- GitHub OIDC token exchange or scoped service tokens GitHub deploy-on-push and external CI
FAQ
Does Prisma Compute require Prisma Postgres or Prisma ORM?
No. Prisma Compute can host TypeScript HTTP services that connect to an external database, and Prisma ORM is optional. Prisma Composer can additionally provision Prisma Postgres and wire it to application services, but that integrated path is a choice rather than a requirement.
Are Prisma Compute preview databases copies of production?
No. With deploy on push configured, non-default branches get separate application services and fresh databases for each Composer-declared Prisma Postgres resource. Production data is not copied. Connections provided through DATABASE_URL are only isolated if a separate preview-scoped database URL is configured.
Does Prisma Compute run database migrations during deployment?
Only for Prisma Composer postgres() resources backed by an ORM contract. The deployment applies committed migrations before starting the service. Composer rawPostgres() databases and connections supplied through DATABASE_URL need a separate migration workflow.
Is the Prisma Compute Starter plan another $10 on top of Prisma Postgres?
No. Starter is one $10-per-month Prisma workspace subscription covering both Compute and Postgres allowances. Compute resource usage and qualifying Postgres operations or storage overages are metered separately; there is no second Starter base fee for using both products.
Does rolling back Prisma Compute restore the database too?
No. A Compute rollback reactivates a previous application service version without rebuilding it. It does not undo schema migrations or restore database contents, so an earlier app version must still work with the current database schema.
