I Tested the Entire Prisma Platform on My Project: The Good, What Broke, and the Cloud Bill A solo developer ran the Sellary digital-commerce platform on Prisma Postgres and Prisma Compute in an isolated staging lab, with an AI coding agent performing setup, to test whether the full Prisma platform could run the app end-to-end. The experiment kept production untouched by using separate database credentials, test-mode Razorpay keys and dummy CI secrets, and found that a naive `prisma migrate deploy` against a clean database would have left 32 of 36 tables missing, requiring a generated baseline SQL script. The writeup also flagged a Windows PowerShell BOM issue that breaks PostgreSQL imports and covers latency, pricing and the resulting cloud bill. A few months ago, I wrote an article titled “I Reduced Prisma Database Operations by 60% Without Upgrading My Database” https://medium.com/@amanbind898/i-reduced-prisma-database-operations-by-60-without-upgrading-my-database-d4101e7b191d . In that post, I shared how profiling slow queries with EXPLAIN ANALYZE helped us cut database operations on my project, Sellary sellary.in https://sellary.in —a digital commerce platform for Indian creators. Shortly after publishing it, Martin Janse van Rensburg from the Prisma team reached out with an intriguing challenge: "Since you already use Prisma ORM, would you be up for a follow-up running Sellary on the whole Prisma platform, adding Prisma Postgres https://www.prisma.io/postgres and Prisma Compute https://www.prisma.io/compute , with an AI agent doing the setup?" Martin offered two months of trial credits and asked for an honest, unfiltered take: setup experience, developer experience, latency, pricing, and what broke along the way. As a solo developer running an independent project, my rule is simple: you never risk customer data or production uptime on an infrastructure experiment. Sellary currently runs in production on Next.js 16 App Router , Prisma ORM 6, and Supabase Postgres with Vercel hosting—and our hosting bill is currently $0/month . So we established a strict ground rule: Zero risk to production. To us, "zero risk" meant far more than just creating a git branch. We set three strict rules to keep our production data 100% safe: 1. Completely Separate Database Credentials: The staging application only ever connected to a freshly provisioned Prisma Postgres database in Singapore sellary-staging-db . Production Supabase connection strings SUPABASE DATABASE URL / SUPABASE DIRECT URL were never injected into the experiment's GitHub Secrets or staging environment. If a query went rogue, it had zero network access to production tables. 2. Sandbox External Services: Sellary handles real money via Razorpay. For staging, payment gateways were strictly bound to test-mode keys rzp test ... , and webhook secrets were dummy-scoped. A complete checkout could be executed in staging without touching live payment rails or triggering creator payouts. 3. Using Dummy Secrets in GitHub Actions: Next.js App Router analyzes routes at build time. To prevent production secrets from being needed on GitHub Actions runners or logged in build traces , we injected mock credentials and used SKIP ENV VALIDATION=1 during the CI build step, keeping production secrets completely air-gapped from the build pipeline. We created an isolated staging lab on a dedicated git branch experiment/prisma-infrastructure , equipped an AI coding agent with official Prisma skills, and evaluated whether Prisma Postgres https://www.prisma.io/postgres and Prisma Compute https://www.prisma.io/compute could run Sellary end-to-end. Here is an honest breakdown of what worked, the friction points we hit, and the economics. Sellary isn't a simple demo app. Our database schema contains 36 models, 28 enums, and over 1,400 lines in schema.prisma , alongside raw SQL queries with PostgreSQL-specific features like FILTER WHERE ... and ON CONFLICT DO UPDATE . Because the project had evolved rapidly during early development, our migration history was behind our schema. If we had naively run prisma migrate deploy against a clean database, 32 out of our 36 tables would have been completely missing. Rather than trying to guess, we used Prisma's migration engine to generate a clean baseline SQL script: npx prisma migrate diff --from-empty --to-schema-datamodel prisma/schema.prisma --script prisma/baseline.sql The Windows Catch: If you run this in PowerShell on Windows, default redirection emits UTF-8 with a Byte Order Mark EF BB BF . PostgreSQL's query engine rejects this with a syntax error at byte 0. We stripped the BOM using an explicit UTF-8 encoding stream before applying it. Once applied to our Singapore staging database ap-southeast-1 , we verified parity: npx prisma migrate diff --from-schema-datamodel prisma/schema.prisma --to-url "$DATABASE URL" Output: No difference detected. All 36 models, indexes, and relations mapped cleanly with zero application query rewrites. Prisma Compute https://www.prisma.io/compute runs containerized workloads powered by Bun. We configured Next.js 16 for standalone output output: 'standalone' in next.config.ts and defined our micro-container service using Prisma Composer in service.ts and module.ts : python import nextjs from '@prisma/composer/nextjs'; import { compute } from '@prisma/composer-prisma-cloud'; export default compute { name: 'web', deps: {}, build: nextjs { module: import.meta.url, appDir: '.' } , } ; We then set up GitHub Actions using prisma/cloud-deploy-action@v1 to build and deploy on every push to our staging branch. That is where we encountered the real-world friction. When bridging bleeding-edge developer tools with an existing codebase, edge cases happen. Here are the three specific hurdles we encountered: prisma deploy module.ts . In GitHub Actions, prisma/cloud-deploy-action checks if node modules/.bin/prisma exists. Because npm ci installs Prisma 6, the action executed the local binary—which lacks the deploy verb—causing the CI runner to halt. build-command : build-command: - npm run build && rm -f node modules/.bin/prisma node modules/.bin/prisma.cmd Next.js builds cleanly with Prisma 6, unlinks the local binary, and allows the deployment step to fall back to the bundled Prisma 8 Compute CLI via Bunx. $prismaConfig: 1 Marker Trap prisma.config.ts by checking for an internal marker: value "$prismaConfig" === 1 . In a hybrid repo on Prisma 6, importing definePrismaConfig from @prisma/cli-engine breaks local commands like npx prisma generate . function definePrismaConfig