Traditional servers

If your application is deployed via a Platform-as-a-Service (PaaS) provider, whether containerized or not, it is a traditionally-deployed app. Common deployment examples include Heroku and Koyeb.

Traditional (PaaS) guides

Deploy to Heroku

In this guide, you will set up and deploy a Node.js server that uses Prisma ORM with PostgreSQL to Heroku. The application exposes a REST API and uses Prisma Client to handle fetching, creating, and deleting records from a database.

Deploy to Render

This guide explains how to deploy a Node.js server that uses Prisma ORM and PostgreSQL to Render.

Deploy to Koyeb

In this guide, you will set up and deploy a Node.js server that uses Prisma ORM with PostgreSQL to Koyeb. The application exposes a REST API and uses Prisma Client to handle fetching, creating, and deleting records from a database.

Deploy to Sevalla

This guide explains how to deploy a Node.js server that uses Prisma ORM and PostgreSQL to Sevalla. The app exposes a REST API and uses Prisma Client to query a PostgreSQL database. Both the app and database will be hosted on Sevalla.

Deploy to Fly.io

This guide explains how to deploy a Node.js server that uses Prisma ORM and PostgreSQL to Fly.io.

Deploy to Railway

This guide explains how to deploy an app that uses Prisma ORM and Prisma Postgres to Railway. The app exposes a REST API and uses Prisma Client to query a Prisma Postgres database. Your app will run on Railway and connect to a managed Prisma Postgres database.