← Back to Blog
Series · 8 parts

Prisma Compute

The story of Prisma Compute: TypeScript app hosting that runs on the same infrastructure as your database. From the public beta launch to the runtime engineering underneath.

Read the Prisma Compute docs
AnnouncementJune 8, 2026

Launching Prisma Compute in Public Beta

Prisma Compute is now in public beta: TypeScript app hosting that runs on the same infrastructure as your database. Point your agent at your project and tell it to deploy.

PlatformJune 11, 2026

We put Bun's Rust rewrite in production on Prisma Compute

Why Prisma Compute's public beta runs on Bun's Rust rewrite canary: the memory and connection-pool failures we hit on stable Bun, and what changed.

PlatformJune 12, 2026

We Launched Prisma Compute with Custom Domains

Prisma Compute launched with custom domain support. Here's how we made the setup one DNS record while handling TLS certificate provisioning, storage, and routing behind the scenes.

AnnouncementJune 19, 2026

Deploy Prisma Apps with create-prisma

create-prisma now scaffolds Compute-ready Prisma apps with prisma.compute.ts, compute:deploy, Prisma Postgres, and Prisma Skills add-ons.

AnnouncementJune 19, 2026

Configure Prisma Compute deploys in TypeScript

Prisma Compute now reads a typed TypeScript config file, so deploys are reproducible and monorepos work: declare one app or several, then ship the whole system with one command.

PlatformJune 19, 2026

Image Transformations with Bun on Prisma Compute

Bun includes native image transformations, and Prisma Compute runs on Bun. Build image resize and format routes as ordinary app requests instead of paying for a separate image transformation service.

PlatformJune 19, 2026

How I Built a Chat App That Never Drops a Token

A personal walkthrough of building Open Chat (oss.chat): durable, resumable AI chat on Durable Streams, Prisma Streams, TanStack DB, and Prisma Compute. How each piece works and what it enables.

PlatformJune 23, 2026

Price the Work, Not the Workflow

Agents can ship, preview, test, and retry in loops. Infrastructure pricing should charge for the work an app performs, not the workflow around it.