What does my TypeScript app need before I put it into public use?
npm run dev as an application-readiness check as well as a hosting decision.npm run dev runs whatever your project's dev script defines. In many frameworks it starts a development server with fast rebuilds and development diagnostics. Opening that process to the internet does not establish a production deployment or prove that the application's data and access rules are ready.
We make Prisma Compute and Prisma Postgres. Provider and framework documentation linked here was checked on October 20, 2026. The steps apply to an existing app; use the framework's production instructions for its actual build and startup commands.
What changes between development and production?
The hosting provider needs an artifact it can reproduce and a supported way to run the server. Your users need the application to retain data, enforce access rules and fail in a way someone can diagnose. These are separate checks: a correct build can still point at the wrong database.
| Development assumption | Production question |
|---|---|
The app reads a local .env file. | Which server-side inputs does the deployed version receive? |
| Test records live in memory or a local JSON file. | Which managed database stores records across instances and deploys? |
| A developer opens the home page. | Can a real role sign in, complete the business action and see the saved result? |
| An error appears in the terminal. | Where can the owner find a request error and the deployed version? |
| The developer restarts the process. | How does the team recover code and data after a failed change? |
Which host should I choose?
Choose around the framework and runtime you actually have. The options below are listed alphabetically.
| Host | Good fit | Preparation |
|---|---|---|
| Netlify | Your framework's production integration fits Netlify's deploy workflow. | Configure its build, server functions and database environment. |
| Prisma Compute | Your TypeScript server fits the deployed Bun runtime and you want managed Postgres in the same project. | Add a Composer declaration, configure inputs and build before deploying. |
| Vercel | Your app already follows its framework and deployment workflow. | Confirm dynamic routes, functions and the Preview/Production configuration. |
A static export can suit an app with no server-side work. An application with private database queries or secret API calls needs those operations on a supported server runtime. Uploading a frontend folder alone does not deploy an arbitrary backend process.
How do I prepare the app for Prisma Compute?
1. Identify and run the production build
Read the scripts in package.json and the framework's deployment guide. For Next.js, review the production checklist. For a project that uses npm, commits package-lock.json and defines its production build as build, verify a clean installation and build:
npm ci
npm run buildA successful command exits with code 0; its messages depend on the application. Fix missing configuration and type/build errors before deploying. Use your repository's actual package manager and lockfile rather than introducing npm into a pnpm or Bun project.
Follow the framework deployment guide to declare the service's build and entry point in Composer. Compute's deploy command does not run the build for you. Next.js needs its configured standalone artifact; a custom HTTP server must use the assigned service port and listen on 0.0.0.0.
2. Configure durable data and secrets
Create an account-owned Prisma Postgres database in Console, then configure the existing client with the pooled application URL. Use a separate direct connection where your migration or administration workflow requires one. Prisma ORM is optional.
Move real records out of process memory and local files. Apply the schema with the migration workflow for your client, and verify which database the app connects to. A deployment does not prove that a manually managed schema has been applied.
Set server-side inputs for database credentials, private API keys and the app's public origin or authentication callbacks. Give previews their own credentials and test database. Store customer uploads in object storage.
3. Deploy a review version and exercise it
Use getting started to authenticate, then deploy the built Composer app to a named test stage: npx prisma@latest deploy --stage review. Verify the intended project and review stage in the deploy report. Open its actual URL from a second browser or device. Test both an allowed action and an action the current user must not be allowed to perform.
Create a fictional record, reload, then redeploy the same code and read the record again. Check login callbacks at the deployed origin, not just localhost. Confirm that invalid input produces a useful response and that logs exclude credentials and customer payloads.
4. Define the release and recovery procedure
Record which source commit and live service version passed review. Keep the test steps with the repository and decide how schema changes reach production. With deploy on push, the GitHub connection and the repository workflow are both required.
After review passes, check the intended production database and migration plan, then build and deploy the approved commit with production inputs. Verify the production URL and sign-in, and test a fictional save/read using an agreed test account with cleanup afterward.
Before customers depend on saved data, choose an appropriate backup plan and test restoration into a separate database. Keep code rollback and data recovery as separate procedures. Review usage limits and spending controls before sharing the production URL.
Invite customers using the verified production URL.
When should I choose another setup?
Prisma Compute runs deployed services on Bun and currently has no WebSocket server support, multi-region service deployment or persistent writable filesystem. Check the runtime limitations before committing to dependencies that require them. Prisma Postgres can still be the database from another app host.
If the remaining work is an unresolved authorization rule, missing recovery plan or unreliable business action, changing the host alone will not complete it. Resolve those application requirements in the review environment before inviting customers.
Frequently asked questions
Test a production deployment before inviting users
Prepare the app's build and inputs, then deploy a separate review environment with Prisma Compute and Prisma Postgres.