Launching Prisma Compute in Public Beta
The hard part of building apps has moved up the stack. You describe what you want, and your agent codes it at 50x the speed.
What didn't change is everything after: finding somewhere to host it, configuring your database, copying connection strings between dashboards, setting environment variables, inspecting build output, chasing logs, and feeding all of that context back into the agent when something breaks.
The friction didn't disappear, it moved.
Introducing Prisma Compute
Today we're launching Prisma Compute in public beta: TypeScript app hosting that runs on the same infrastructure as your database, without sending traffic through a separate hosting vendor.
It runs on Bun, scales to zero when nothing is happening, and treats every deploy as an immutable version with its own preview URL. You can look at a change running in production-like conditions before you promote it, and roll back just as easily by promoting the previous one.
Every branch comes with a full database and an app deployment. Your agent can spin up a branch, test a new idea against a real database, and merge it into production when it's ready. App and database, together in one box.
The most important part is that your agent can drive the whole loop: build, deploy, read logs, fix, and redeploy. It can make a change, inspect what happened, fix what failed, and try again without jumping between tools.
That is the direction Prisma is moving in: one place where product builders, and their agents, can define the stack, deploy it, inspect it, and keep iterating.
Where Prisma is headed
Prisma started as a type-safe ORM for the TypeScript community, where you could express your database schema as code. Then we launched Prisma Postgres, so you could host your database with Prisma too. Now Prisma Compute brings the app and database together into one platform, where you, or your agent, can define the entire stack as code and deploy it.
With Prisma Compute, Prisma becomes a platform for product builders who want to build software with their agent, in the way software is built in 2026.
Try it
Compute is in public beta starting today. Sign in once with bunx @prisma/cli@latest auth login, the one step that needs a human, then point your coding agent at your project and tell it:
YouDeploy your app with @prisma/cli@latest.
Skillprisma-cli<br>Agent running prisma-cli<br>✔ Linked ./guestbook to project compute-guestbook-demo<br>Deploying compute-guestbook-demo / add-guestbook / guestbook<br>Build command bun run build<br>Output .<br>◇ Creating branch database…<br>✔ Created branch database<br>◇ Applying schema with prisma db push…<br>✔ Database in sync with prisma/schema.prisma<br>✔ Added branch env: DATABASE_URL, DIRECT_URL<br>Building locally… Built<br>Uploading… Uploaded<br>Deploying… Deployed<br>✔ Live in 4.5s<br>https://add-guestbook.guestbook.prisma.build
One prompt, and the agent reads the project, provisions a branch database, applies your schema, builds the app, and ships an immutable preview URL. When something breaks, it reads the same logs you just watched scroll by, fixes the cause, and redeploys. The loop stays inside the agent.
Want the full walkthrough, from signing in to connecting GitHub for deploy-on-push? Read the Compute quickstart.
We're early and shipping fast, so tell us what breaks or feels rough in the prisma-compute channel on our Discord.
Go build something.
Share this article<br>div]:bg-background-ppg-strong" data-state="closed"><br>div]:bg-background-ppg-strong" data-state="closed"><br>div]:bg-background-ppg-strong" data-state="closed">
Subscribe to our newsletter
On this pageIntroducing Prisma ComputeWhere Prisma is headedTry it