# One platform for your app and its database (/compute)

> Prisma Compute | Host TypeScript apps (Node.js, Bun or Next.js) next to Postgres. For the complete Prisma website index, see [llms.txt](https://www.prisma.io/llms.txt). A Markdown version of any listed page is available at its `.md` URL — this one is `/compute.md`.

Prisma Compute is a platform-as-a-service (PaaS) for TypeScript apps (Node.js, Bun or Next.js) that runs them next to Prisma Postgres. Generally available since August 2026. Free plan, no credit card. Any Postgres client works; Prisma ORM is optional.

Prisma Compute hosts TypeScript apps (Node.js, Bun or Next.js) next to Prisma Postgres in one project.

- [Get started free](https://console.prisma.io/sign-up)
- [Read the docs](/docs)

Generally available since August 2026. Free plan, no credit card.

- Set up deploy on push, and every feature branch gets a preview with its own declared databases
- Your app runs next to Prisma Postgres, in one of six regions
- Streams responses and scales to zero when idle, for agents as well as apps

### Prisma Compute at a glance

- **Connect** — Deploy from your machine with npx prisma deploy module.ts, or connect the GitHub repo and add the deploy workflow to deploy on every push.
- **Deploy** — One deploy provisions the services and databases declared in module.ts, and applies the migrations of any database typed by a Prisma ORM contract.
- **Live** — Production, plus a preview per feature branch with its own services and declared databases once deploy on push is set up.
- **Apps** — Bring a Next.js, Hono or Bun app, or an agent: add a Composer declaration (service.ts and module.ts) around the server code you already have, then deploy.

## One platform can ship features two never could

When your hosting provider and your database provider are separate companies, the things that depend on them being aware of each other (per-branch previews with their own database, end-to-end test data) depend on an integration between the two that you set up and maintain.

Prisma Compute exists to change that.

- A preview or staging environment per Git branch
- Ship app and database in one deploy
- Host streaming agents natively
- One module.ts for app and database

## What one platform unlocks

Compute and Prisma Postgres run as a single platform. The features below are only possible because of that.

- **Built for hosting AI agents** — Agents stream their answers and spend most of their time waiting on a model API. Compute streams a response as your service sends it, bills memory and active CPU separately, and scales to zero between tasks.
- **A preview per feature branch** — Once deploy on push is set up, every feature branch (any branch except the default) gets its own services and a new database for each one the Composer module declares, and deleting the branch tears them down. A database typed by a Prisma ORM contract gets your migrations applied on deploy; one declared with rawPostgres() keeps your own migration step. No shared test DB that passes tests production fails.
- **App and database on one platform** — Your app runs next to Prisma Postgres, in the same project, with PgBouncer pooling included. Any Postgres client works, and Prisma ORM is optional.
- **[S3-compatible file storage built in](/docs/compute/object-storage)** — Object Store buckets live inside your project, next to its databases, managed from the same Console and API. Any S3 client works, with per-bucket keys scoped to read or read-write.

## Built to work with the rest of Prisma

Prisma Compute is where the stack comes together: your app, your database, and your data model on one platform. Standard Postgres underneath: leave with pg_dump; the Composer module is a TypeScript file in your repo, not a runtime.

**Best together. Swappable when needed.**

## Compare Prisma

How Prisma Compute and Prisma Postgres compare with the other hosting and Postgres options, and where each one fits.

- **[App hosting platforms with managed Postgres compared (2026)](/blog/app-hosting-platforms-with-managed-postgres-2026)** — Prisma Compute, Railway, Render, Fly.io, Supabase, Neon and Vercel compared for an app next to managed Postgres.
- **[Where to host a TypeScript frontend, a Node API and Postgres](/blog/where-to-host-typescript-frontend-node-api-postgres)** — Hosting a TypeScript frontend, a Node API and their Postgres database from one GitHub repository.
- **[Choosing hosting and Postgres after your first 100 paying users](/blog/choosing-hosting-and-postgres-after-your-first-100-users)** — What to run the app and the database on once real users arrive.
- **[Neon vs Prisma Postgres for hosting and the database in one place](/blog/neon-vs-prisma-postgres-app-hosting-in-one-place)** — Neon alternatives when the app and its database should live in one project.
- **[Netlify alternatives for a full-stack TypeScript app with Postgres](/blog/prisma-vs-netlify)** — Where to move a TypeScript app with Postgres when Netlify stops fitting.
- **[Move a local Postgres database online (2026)](/blog/from-local-to-production-with-prisma-postgres)** — Prisma Postgres, Neon, Render, Railway and Supabase compared for taking a laptop Postgres database online with pg_dump and pg_restore.
- **[Migrate a local Postgres database to Prisma Postgres](/docs/postgres/import-from-existing-database)** — The docs guide for copying a local PostgreSQL database into Prisma Postgres with pg_dump and pg_restore over the direct connection.

## FAQ

### Can I host my existing GitHub repo with a TypeScript frontend and Node API here?

Yes, when the frontend and the API are TypeScript services built for Node.js, Bun or Next.js. Add a Composer declaration around the server code you already have (a service.ts per service and one module.ts); the porting guide in the docs has a prompt your coding agent can write it from. Run your build, then deploy with npx prisma deploy module.ts. For deploy on push, connect the repository and add the prisma/cloud-deploy-action workflow; from then on every feature branch gets a preview with its own declared databases.

### What does Prisma Compute not do?

Compute does not support WebSocket servers, cron scheduling or a persistent filesystem today, and each service runs in one region, chosen from six. A request has 60 seconds to send its first byte, and a response that has started streaming is not cut off. The runtime is Bun. The Compute FAQ in the docs has the full list of trade-offs.

### Do I need Prisma ORM?

No. Your app reaches Prisma Postgres, or any other Postgres, through a connection string, so any Postgres client works. Prisma ORM is optional.

### Is Prisma Compute related to Prisma Cloud?

No. Prisma Compute is unrelated to Palo Alto Networks' Prisma Cloud. Prisma makes Prisma ORM, Prisma Postgres and Prisma Compute, and the dashboard is Prisma Console.

### What does it cost?

The Free plan includes 1M requests, 360 GB-hours of memory, 4 active vCPU-hours and 10 GB of outbound bandwidth a month for Compute, and 200k operations, 2 GB and 50 databases for Prisma Postgres, with no credit card and no usage billing. Starter is $10 a month base plus metered compute: 5M requests and 1M operations are included, memory ($0.006 per GB-hour), active vCPU ($0.064 per hour) and bandwidth ($0.025 per GB) are metered from the first unit, and you can set a spend limit. An idle app scales to zero. The pricing page lists every plan.

## One platform. Both layers. Features only possible because of it.

Compute is part of a TypeScript stack where hosting and the database travel as a unit: preview them together, deploy them together, debug them together.

- Built to host the agents you're building, not just the apps
- A preview per feature branch, app and database together
- App next to its database, in one project
- Trusted by 500,000+ developers · 46,500+ GitHub stars

- [Get started free](https://console.prisma.io/sign-up)
- [Read the docs](/docs)