# App hosting platforms with managed Postgres compared (2026): Prisma Compute, Railway, Render, Fly.io, Supabase, Neon and Vercel URL: https://www.prisma.io/blog/app-hosting-platforms-with-managed-postgres-2026 Published: 2026-09-30 Updated: 2026-11-12 Authors: Gregory Boch Tags: platform, prisma-postgres Description: Prisma Compute, Railway, Render, Fly.io, Supabase, Neon and Vercel compared for an app next to managed Postgres: previews, idle cost, pooling, backups and prices. > Blog posts describe Prisma as it was on the date shown and are not kept current. Before implementing from a post, check the documentation index at https://www.prisma.io/docs/llms.txt and the changelog at https://www.prisma.io/changelog.md. > For an index of every published post, fetch https://www.prisma.io/blog/llms.txt. Five platforms host a Node.js app next to managed Postgres in 2026: Prisma Compute with Prisma Postgres, Railway, Render, Fly.io, and Vercel with a Marketplace database (Prisma Postgres, Neon or Supabase); Supabase and Neon run the database with functions beside it. They differ on who runs the database, what an idle app costs, previews per pushed branch or per pull request, and runtime limits. Prisma Compute runs TypeScript apps built for Node.js, Bun or Next.js on Bun, next to Prisma Postgres in one project and region. Prisma makes Prisma ORM, Prisma Postgres and Prisma Compute. > [!NOTE] > **How we compared** > > We make Prisma Compute and Prisma Postgres. The comparison table and the platform sections are in alphabetical order, and the criteria are the columns of the Quick comparison table. The Prisma cells come from Prisma's docs and pricing page; every other cell was checked against the vendor's own pricing page or docs on 29 September 2026, the Railway, Neon, point-in-time recovery and Postgres extension cells again on 8 October 2026, the Fly.io and Neon price cells and the Fly.io project cell on 12 October 2026, and the Railway price and backups cells and the Neon Functions Free allowance on 14 October 2026, listed under [Sources and check dates](#sources-and-check-dates). Where a vendor page states no number, the cell says so. ## Quick recommendation [#quick-recommendation] A TypeScript service and its database from one GitHub repository in one project, from one provider, on one bill: Prisma Compute and Prisma Postgres. The Free plan has no usage billing; Starter is a $10 base, and Compute memory, CPU and bandwidth are metered on top. A WebSocket server or a Python or Go API: Render or Fly.io run the container you have next to a managed database, Railway runs it next to a Postgres template Railway maintains, and Fly.io runs the app's Machines in more than one region, with its Managed Postgres cluster in one region you choose. A Python or Go API on any of the three can also use Prisma Postgres for the database, or Neon or Supabase, since each accepts any Postgres client. Point-in-time recovery today: Neon, Railway (opt-in), Render (paid databases), Fly Managed Postgres or Supabase (paid add-on), because Prisma Postgres does not have it yet; it is coming in November 2026. | Your situation | Pick | Why | | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | I just want it deployed from GitHub, everything in one project | Prisma Compute + Prisma Postgres | App and database in one project. Add a Prisma Composer declaration and make two changes to each Node.js or Bun server, three if it talks to Postgres, run your build, deploy with `npx prisma deploy` (it does not build for you), then connect the repo and add the `prisma/cloud-deploy-action` workflow for deploy on push | | First paying users on a TypeScript app | Prisma Compute + Prisma Postgres | Starter is a $10 base with 5M requests and 1M database operations included and Compute usage metered on top, plus daily snapshots on days with database activity, kept 7 days, and a spend limit you set in the Console. The database has no instance to size or upgrade as users grow; on Render, Fly Managed Postgres and Supabase you pick a plan or size. [Hosting and Postgres for your first 100 paying users](https://www.prisma.io/blog/choosing-hosting-and-postgres-after-your-first-100-users) has the database cost at 100, 1,000 and 10,000 users | | First paying users, any language | Prisma Postgres, Neon or Supabase for the database (any Postgres client); Render or Railway for the app | Prisma Postgres has no instance to size or upgrade and includes PgBouncer pooling on every plan, and its Starter plan is a $10 base with 1M operations included; like Neon and Supabase, it accepts any Postgres client. Prisma Compute runs TypeScript apps built for Node.js, Bun or Next.js; Render (paid web service from $7 a month) and Railway (Hobby $5 a month with $5 of usage) build Python, Go and other languages. Both hosts also offer their own Postgres: on Render the compute plan you pick sets the database's CPU and RAM, with PgBouncer pooling you turn on, on paid databases; on Railway, PgBouncer pooling is opt-in. Two providers, so two bills once both are on paid plans | | Small production app with a preview for each pushed branch other than the default | Prisma Compute + Prisma Postgres | Starter $10 base, 5M requests and 1M operations included. Once deploy on push is set up, every pushed branch other than the default one gets a preview with its own services and, for databases declared in the Composer module, its own new database; production data is not copied, and a push to the default branch deploys production | | REST, tRPC or GraphQL API + TypeScript frontend + Postgres from GitHub | Prisma Compute + Prisma Postgres | One project, one region, PgBouncer pooling included | | Leaving Netlify with a full-stack TypeScript app and Postgres | Prisma Compute + Prisma Postgres | The frontend, the API and the database deploy from one repository; [Netlify alternatives for a full-stack TypeScript app](https://www.prisma.io/blog/prisma-vs-netlify) has the feature-parity table | | Just hosted Postgres, free, standard tools | Prisma Postgres | PostgreSQL 17, 200,000 operations a month, 2 GB of storage and 50 databases on Free, any Postgres client | | Holds WebSocket connections open | Fly.io, Neon Functions, Railway, Render | Prisma Compute does not run WebSocket servers today; support is planned for early 2027 | | Python or Go API | Railway, Render, Fly.io for the app; Prisma Postgres for the database, or Neon or Supabase | Prisma Compute runs TypeScript apps built for Node.js, Bun or Next.js; those databases accept any Postgres client, and the three hosts also offer their own Postgres | | More than one region | Fly.io | Fly.io runs the app's Machines in more than one region, with a Managed Postgres cluster in one region you choose; one region per Prisma Compute service, from six | | Need point-in-time recovery today | Neon, Railway (opt-in), Render (paid databases), Fly Managed Postgres, Supabase (paid add-on) | Prisma Postgres has daily snapshots on paid plans, no PITR yet (coming in November 2026) | | Frontend needs a global CDN above all | Vercel + Prisma Postgres, or another Marketplace database | Prisma Compute is not a CDN or edge platform | | Lowest bill, and you run servers yourself | A VPS | Every managed option here charges for the management | ## Quick comparison [#quick-comparison] Rows in alphabetical order; we make Prisma Compute and Prisma Postgres. | | App + DB in one project | Previews: per pushed branch or per pull request | Idle cost | Same-region networking | Pooling | Backups / PITR | Postgres extensions | Price at small scale | Exit path | | ------------------------------------ | ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | --------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- | | **Fly.io** | In one organization: Managed Postgres runs in the organization's private network and is attached to an app | Per pull request via GitHub Actions; no database in the guide | Autostop; no CPU or RAM charge while stopped | Per organization | Included | Automated backups; point-in-time restore with `fly mpg restore --pitr-time` | pgvector; PostGIS if enabled at provisioning | $2.19 Machine + $38 Managed Postgres a month, plus $0.28 per GB of database storage ([Fly.io pricing](https://fly.io/pricing), as of October 2026) | `pg_dump` | | **Neon** | Backend functions next to the database (Neon Functions, four AWS regions); UI on another host | Copy-on-write branch with the parent's data, for example one per Vercel preview deployment through the Neon-Managed Vercel integration | Scales to zero after 5 minutes; no base fee | Functions in the database's region; UI depends on its host | PgBouncer, `-pooler` string | Instant restore on every plan; history window up to 7 days on Launch and up to 30 days on Scale | pgvector, PostGIS, TimescaleDB (Apache-2 features) and more | Free $0; Launch $0.106 per CU-hour for the database; Functions billed separately on paid plans (on Launch: $0.10 active and $0.025 waiting per Capacity-Hour, $0.60 per million invocations); plus your UI host ([Neon pricing](https://neon.com/pricing) and [plans](https://neon.com/docs/introduction/plans), as of October 2026) | `pg_dump` | | **Prisma Compute + Prisma Postgres** | Yes; TypeScript on Bun, no WebSocket servers today (planned for early 2027) | Per pushed branch other than the default one, once deploy on push is set up: its own services and a new database for each one the module declares; production data not copied | App scales to zero; database per operation | One of six regions per service | PgBouncer included | Daily snapshots on paid plans, 7 or 30 days; PITR coming in November 2026 | pgvector, pg\_search, pg\_trgm and other standard extensions; no PostGIS or TimescaleDB | Free: app and database, no usage billing. Starter $10 base, 5M requests and 1M operations included, memory, active vCPU and bandwidth metered ([Prisma pricing](https://www.prisma.io/pricing), as of September 2026) | `pg_dump`; the Composer module is a TypeScript file in your repo, not a runtime | | **Railway** | Yes, a Postgres template Railway maintains; backups, PITR, HA and pooling opt-in | Per pull request, once turned on in project settings | Sleeps 5 to 10 minutes after last outbound traffic with Serverless enabled; otherwise runs all month | Per environment | PgBouncer add-on you enable on the Postgres service | Volume backups by hand or on a schedule you turn on; opt-in PITR for Postgres, about 4 weeks | None added to the default template; pgvector, PostGIS and TimescaleDB as separate templates | Free $0 with $1 of credit a month after a 30-day trial; Hobby $5 with $5 of usage, then $10 per GB RAM and $20 per vCPU a month ([Railway pricing](https://railway.com/pricing) and [plan reference](https://docs.railway.com/pricing/plans), as of October 2026) | `pg_dump` | | **Render** | Yes, managed | Per pull request on a Pro workspace ($25 a month) or higher, once turned on in the Blueprint: for every pull request against the Blueprint's linked branch in automatic mode, or only when the pull request title includes `[render preview]` in manual mode; no data copied | Free spins down after 15 minutes; paid runs all month | Per region | PgBouncer on paid databases | PITR on paid databases, 3 or 7 days | pgvector, PostGIS, TimescaleDB (no Community features) and more | $7 web service + $6 Postgres a month ([Render pricing](https://render.com/pricing), as of September 2026) | `pg_dump` | | **Supabase** | Backend only (Edge Functions) | Per pull request; no production data by default | Free pauses after a week idle; paid runs all month | Depends on your app host | Shared pooler; dedicated on paid plans | Daily, 7 days on Pro; PITR add-on $100 a month | Over 50 preconfigured, including pgvector and PostGIS | Free $0; Pro from $25 a month, plus your app host ([Supabase pricing](https://supabase.com/pricing), as of September 2026) | `pg_dump` | | **Vercel + Marketplace database** | No; Marketplace database | Per push to a non-production branch; a database per preview depends on the integration | Functions per use; database on its own plan | Depends on the database region | From the provider | From the provider | From the provider | Hobby $0; Pro $20 a month plus the database plan ([Vercel pricing](https://vercel.com/pricing), as of September 2026) | `pg_dump` | ## The seven platforms, A to Z [#the-seven-platforms-a-to-z] Each entry has the same headings, and each competitor ends with how it compares with Prisma Compute + Prisma Postgres. We make Prisma Compute and Prisma Postgres; the other six were checked against their own docs on 29 September 2026, and the details that later updates changed were checked again on 8, 12 and 14 October 2026. ### Fly.io [#flyio] **Best for:** an app whose Machines run in more than one region, with a Managed Postgres cluster in one region in the same organization, or one that holds WebSocket connections open. **What it does:** runs Machines in 17 regions, most of which also host Fly Managed Postgres, with high availability, backups and pooling on every database plan. A Managed Postgres cluster is created in one region you choose, while the app's Machines can run in several; the cluster's replica is a standby in the same region for high availability, and Managed Postgres has [no read replicas](https://fly.io/learn/fly-vs-railway/). The cluster runs in the organization's private network, and attaching it to an app sets the connection string as a secret on that app. **Scaling behavior:** Machines autostop when idle and autostart on request; a stopped Machine pays only for its root filesystem. **Pricing:** a shared-cpu-1x 256 MB Machine at $2.19 a month plus Managed Postgres Basic at $38 and database storage at $0.28 per GB, Machines billed by the second. [Fly.io pricing](https://fly.io/pricing), as of October 2026. **Trade-offs:** Managed Postgres plans start at $38 a month, and the review-apps guide creates an app per pull request but no database. Managed Postgres restores to a point in time with [`fly mpg restore --pitr-time`](https://fly.io/docs/flyctl/mpg-restore/). **Compare:** [Fly.io vs Prisma Compute](https://www.prisma.io/blog/where-to-host-typescript-frontend-node-api-postgres#4-flyio). **vs Prisma Compute + Prisma Postgres:** Fly.io runs the app's Machines in more than one region, with the Managed Postgres cluster in one region you choose, holds WebSocket connections open and runs any language, and its Managed Postgres includes high availability and pooling on every plan plus point-in-time restore; Prisma Compute + Prisma Postgres starts on a Free plan for the app and the database, where Fly Managed Postgres starts at $38 a month, and gives every pushed branch other than the default one a preview with a new database for each one the Composer module declares, where Fly's review-apps guide creates no database. ### Neon, plus a host for the frontend [#neon-plus-a-host-for-the-frontend] **Best for:** branches with production-shaped data per pull request, point-in-time restore, and no monthly floor. **What it does:** serverless Postgres billed by the CU-hour (its pricing page now calls it Lakebase Postgres). Neon Functions (generally available since 2026-09-17, also on Free) run Node.js 24 HTTP handlers next to the database, including WebSockets and SSE, in four AWS regions today; Neon's full-stack guide keeps the UI on Vercel, Netlify or another frontend host. **Scaling behavior:** compute scales to zero after 5 idle minutes, up to 16 CU on Launch; an always-on API pays for every hour awake. **Pricing:** Free $0 with 100 CU-hours and 1 GB of storage per project, up to 20 GB across all projects; Launch $0.106 per CU-hour and $0.35 per GB-month with restore up to 7 days; Scale $0.222 per CU-hour with up to 30 days. Functions are billed separately: on Launch, $0.10 per active and $0.025 per waiting Capacity-Hour plus $0.60 per million invocations, and Free includes 10 active and 400 waiting Capacity-Hours and 1 million invocations per project a month. [Neon pricing](https://neon.com/pricing) and [plans](https://neon.com/docs/introduction/plans), as of October 2026. **Trade-offs:** the frontend needs a second host, and extra branches ($1.50 per branch-month) and restore history ($0.20 per GB-month) add up. **Compare:** [Neon vs Prisma Postgres for app hosting in one place](https://www.prisma.io/blog/neon-vs-prisma-postgres-app-hosting-in-one-place) and the [pricing comparison](https://www.prisma.io/blog/prisma-postgres-vs-neon-pricing-2026). **vs Prisma Compute + Prisma Postgres:** Neon has point-in-time restore on every plan, copy-on-write branches with the parent's data, and Functions that hold WebSocket connections and run on cron triggers; Prisma Compute also runs the server that serves the frontend, so a web app and its database run in one project and region, and Prisma Postgres bills per operation instead of by compute hours. ### Prisma Compute + Prisma Postgres [#prisma-compute--prisma-postgres] **Best for:** a TypeScript frontend and Node API deployed from one GitHub repository next to their database, in one project. Neither product needs Prisma ORM. **What it does:** Prisma Compute, generally available since August 2026, runs TypeScript HTTP services (Node.js, Bun or Next.js) next to Prisma Postgres. Any Postgres client works, whether `pg`, Drizzle, Kysely or `psql`. With Prisma Composer you describe your whole app in TypeScript: `npx prisma dev` runs it on your laptop, and `npx prisma deploy` provisions the services on Prisma Compute and the databases on Prisma Postgres, applying the committed migrations to any database declared with `postgres()` and a Prisma ORM contract before its service starts. Both commands read the app's entry module from the `composer` section of `prisma.config.ts` (`entry: './module.ts'`). An existing repository adds a declaration (a `service.ts` per server plus one `module.ts`) and makes two changes to each Node.js or Bun server, three if it talks to Postgres: read the port from `service.port()` and bind 0.0.0.0, turn other `process.env` reads into service inputs or dependencies, and, in a server that talks to Postgres, build the client from the injected `db.url`. A Next.js app uses the `nextjs` build adapter with `output: 'standalone'` instead, and its standalone server binds the port itself. A coding agent can do this from the [porting guide](https://www.prisma.io/docs/composer/porting-an-app) prompt. **Scaling behavior:** the app scales to zero when idle; the database bills per operation, and there is no instance to size or upgrade: Prisma scales the database for you. **Pricing:** Free $0 for app and database, no usage billing, no credit card. Starter $10 base with 5M requests and 1M operations included; memory ($0.006 per GB-hour), active vCPU ($0.064 per vCPU-hour) and bandwidth ($0.025 per GB) metered from the first unit. [Prisma pricing](https://www.prisma.io/pricing), as of September 2026. **Trade-offs:** Point-in-time recovery is coming in November 2026; until then, paid plans keep daily snapshots, taken on days when the database has activity. Railway, Render, Fly.io and Neon Functions run WebSocket servers; Prisma Compute does not today, and support is planned for early 2027. One region per service from six, a Bun runtime and 60 seconds to send the first byte. [Composer limitations](https://www.prisma.io/docs/composer/limitations) lists what the declaration does not cover. **Compare:** [Where to host a TypeScript frontend, Node API and Postgres](https://www.prisma.io/blog/where-to-host-typescript-frontend-node-api-postgres), and for a move off Netlify, [Netlify alternatives for a full-stack TypeScript app with Postgres](https://www.prisma.io/blog/prisma-vs-netlify). ### Railway [#railway] **Best for:** the container you have, in any language, next to Postgres, with an environment per pull request once PR environments are turned on in project settings. **What it does:** builds your repository into a long-lived service, with Postgres as a template service in the same project on the environment's private network, PgBouncer as an add-on, and point-in-time recovery for Postgres (about 4 weeks). **Scaling behavior:** with the Serverless setting enabled, a service sleeps 5 to 10 minutes after its last outbound traffic and wakes on the next request. **Pricing:** a 30-day trial with $5 of credit and no credit card, then a Free plan for one project at $0 a month with $1 of usage credit a month; Hobby $5 a month with $5 of usage included, beyond which usage is billed per second, at about $10 per GB of RAM and $20 per vCPU a month. [Railway pricing](https://railway.com/pricing) and [plan reference](https://docs.railway.com/pricing/plans), checked 2026-11-12. **Trade-offs:** Railway maintains its Postgres template; backups, point-in-time recovery, high availability and PgBouncer pooling are opt-in in [its docs](https://docs.railway.com/databases/postgresql) (checked 2026-10-08). Sleeping is opt-in per service: without the Serverless setting, a service runs and bills RAM and vCPU all month. **Compare:** [Railway vs Prisma Compute](https://www.prisma.io/blog/where-to-host-typescript-frontend-node-api-postgres#2-railway). **vs Prisma Compute + Prisma Postgres:** Railway builds the repository in any language Railpack supports, or from its Dockerfile, holds WebSocket connections open and offers the opt-in Postgres features above; Prisma Compute needs a Prisma Composer declaration and two changes to each Node.js or Bun server, three if it talks to Postgres, and in return gives every pushed branch other than the default one, not only pull requests, a preview with its own services and a new database for each one the Composer module declares, and scales an idle app to zero without a setting. ### Render [#render] **Best for:** managed Postgres with point-in-time recovery next to a container you keep as it is. **What it does:** builds from GitHub and runs web services next to managed Postgres in one region. Hobby workspaces get single-service previews, turned on per service; a full preview environment per pull request, copied without its data, needs the Pro workspace and a `previews.generation` setting in the Blueprint. **Scaling behavior:** Free web services spin down after 15 idle minutes; paid instances run all month at a fixed price. **Pricing:** the smallest paid web service (512 MB) is $7 a month and the smallest paid Postgres (256 MB) is $6; the Pro workspace adds $25 a month, and Free Postgres databases expire after 30 days. [Render pricing](https://render.com/pricing), as of September 2026. **Trade-offs:** pooling and PITR need a paid database, and PITR keeps 3 days on Hobby and 7 on Pro. **Compare:** [Render vs Prisma Compute](https://www.prisma.io/blog/where-to-host-typescript-frontend-node-api-postgres#3-render). **vs Prisma Compute + Prisma Postgres:** Render runs WebSocket servers and APIs in any language next to managed Postgres, with point-in-time recovery on paid databases; Prisma's Free plan has no time limit, where Render's free Postgres expires after 30 days, and Prisma Compute scales an idle app to zero on every plan and gives every pushed branch other than the default one a preview with a new database for each one the Composer module declares, where Render's full preview environments need the Pro workspace. ### Supabase, plus a host for the app [#supabase-plus-a-host-for-the-app] **Best for:** Postgres with auth, storage and Edge Functions from one vendor, with the frontend elsewhere. **What it does:** managed Postgres with a shared pooler and Edge Functions on Deno; it does not host frontends. [Supabase Compute](https://supabase.com/compute), which runs backend services, is a private alpha (us-west-2 only, not for production). A branch per pull request starts without production data; a seed file fills it. **Scaling behavior:** paid compute runs all month at the size you pick; branches bill $0.01344 per branch-hour; Free projects pause after a week of inactivity. **Pricing:** Free $0 with a 500 MB database size quota, summed across the organization's projects (each Free project has a fixed 2 GB disk) and no backups; Pro from $25 a month with daily backups kept 7 days; the PITR add-on, for Pro, Team and Enterprise projects, is $100 a month per 7 days of retention. [Supabase pricing](https://supabase.com/pricing) and [backups](https://supabase.com/docs/guides/platform/backups), as of November 2026. **Trade-offs:** a second host for the app, and a second bill unless the app runs on Vercel and you create the Supabase project from the Vercel Marketplace, which bills it through your Vercel account; the direct connection is IPv6 unless you buy the IPv4 add-on. **Compare:** [Switch from Supabase to Prisma Postgres](https://www.prisma.io/docs/guides/switch-to-prisma-postgres/from-supabase). **vs Prisma Compute + Prisma Postgres:** Supabase bundles auth, storage and Edge Functions with Postgres and sells point-in-time recovery as an add-on; Prisma Compute also runs the app server and the API, so the app and Prisma Postgres run in one project from one vendor, and Prisma's Free plan includes 2 GB of storage. ### Vercel, plus a Marketplace database [#vercel-plus-a-marketplace-database] **Best for:** a frontend that needs a global CDN above everything else. **What it does:** builds the frontend and its functions from Git with a preview deployment per push to a non-production branch. Vercel Postgres is no longer available (existing databases moved to Neon in December 2024); Postgres comes from the Marketplace, where Prisma Postgres, Neon and Supabase are providers. **Scaling behavior:** Fluid compute bills active CPU and provisioned memory per use; the database bills on the provider's plan. **Pricing:** Hobby $0; Pro $20 a month with $20 of usage credit and one developer seat, active CPU from $0.128 per hour, plus the database plan. [Vercel pricing](https://vercel.com/pricing), as of September 2026. **Trade-offs:** two products, though a database you create from the Marketplace bills through your Vercel account, and a database per preview depends on the integration. **Compare:** [Prisma vs Vercel](https://www.prisma.io/blog/prisma-vs-vercel) and [Prisma Compute vs Vercel pricing](https://www.prisma.io/blog/prisma-compute-vs-vercel-pricing). **vs Prisma Compute + Prisma Postgres:** Vercel serves the frontend from a global CDN with a preview deployment per push, and lets you pick the database from the Marketplace, Prisma Postgres included; Prisma Compute runs a frontend served by Next.js, Astro, TanStack Start or your own Node.js or Bun server, and the API, next to Prisma Postgres in one project and region, and every pushed branch other than the default one gets a preview with a new database for each one the Composer module declares, instead of depending on the integration. ## Platforms with app hosting and Postgres in one place [#platforms-with-app-hosting-and-postgres-in-one-place] Four of the seven host the app and the database with one vendor: Prisma Compute with Prisma Postgres, Railway and Render in one project, and Fly.io in one organization, where a Managed Postgres cluster runs in the organization's private network and is attached to an app. On Railway, Render and Fly.io the database is a resource next to the app, read from a connection string. On Prisma it is a dependency the service declares in its Composer module, and the deploy provisions it and hands the service the connection: declared with `rawPostgres()`, it is a plain connection URL that `pg`, Drizzle, Kysely or any other Postgres client uses, and you run the migrations; on the optional typed path, with `postgres()` and a Prisma ORM contract, the deploy applies the committed migrations before the service starts. The cost is a declaration in the repo and a TypeScript-only runtime; the return is that production and every preview branch get the same wiring. Supabase and Neon run backend code next to the data. Supabase does not host frontends (its Compute private alpha runs backend services), and Neon's full-stack guide keeps the UI on Vercel, Netlify or another frontend host, so a web app on either has two hosts. With the frontend on Vercel and the database created from the Vercel Marketplace, that is one bill, through your Vercel account; with the frontend on another host, you pay that host as well. Vercel is the app host, with the database from a Marketplace provider. DigitalOcean App Platform also hosts the app and Postgres with one vendor, and it is not in the comparison table: it [deploys apps from Git repositories or container images](https://docs.digitalocean.com/products/app-platform/), and you [add a database to the app](https://docs.digitalocean.com/products/app-platform/how-to/manage-databases/), a dev database for development or a DigitalOcean Managed Database, which DigitalOcean recommends for production. On [DigitalOcean's pricing page](https://www.digitalocean.com/pricing/app-platform), a service container starts at $5 a month, and a 512 MiB dev database is $7 a month and not backed up by default; [Managed PostgreSQL](https://www.digitalocean.com/pricing/managed-databases) starts at $15.15 a month, with a [daily backup and restore to any point in the previous seven days](https://docs.digitalocean.com/products/databases/postgresql/details/features/). Previews take a [GitHub Actions workflow](https://docs.digitalocean.com/products/app-platform/how-to/deploy-from-github-actions/) you add, which deploys a separate app for each pull request (digitalocean.com, checked 2026-11-09). Northflank also hosts the app and Postgres in one project, and it is not in the comparison table: it [builds and deploys code in any language from GitHub, GitLab or Bitbucket](https://northflank.com/docs/v1/application/getting-started/introduction-to-northflank) and runs [PostgreSQL as an addon](https://northflank.com/docs/v1/application/databases-and-persistence/deploy-a-database) that workloads in the same project reach, with [backups](https://northflank.com/docs/v1/application/databases-and-persistence/backup-restore-and-import-data) on hourly, daily or weekly schedules you add. [Preview environments](https://northflank.com/docs/v1/application/release/set-up-preview-blueprints) come from a preview blueprint you set up: a pull request or a push to a matching branch creates one, and the blueprint gives it a new database, forks one from a snapshot or [shares an existing one](https://northflank.com/docs/v1/application/use-cases/create-preview-environments). On [Northflank's pricing page](https://northflank.com/pricing), the free Sandbox includes 2 services, 2 jobs and 1 database, with up to $20 a month of resources on Northflank Cloud, and paid usage is billed by the second: on Northflank Cloud by resource, and in your own cloud account by the vCPU on the nodes Northflank manages, while your cloud provider bills the infrastructure. Northflank's [pricing docs](https://northflank.com/docs/v1/application/billing/pricing-on-northflank) say that every user must add a payment method before creating resources, whatever the plan, to verify their identity, and that the free tier should not be used for production (northflank.com, checked 2026-11-09). ### Considering Neon but want app hosting too? [#considering-neon-but-want-app-hosting-too] Neon Functions (generally available since 2026-09-17, also on Free) run Node.js 24 HTTP handlers next to the database, including WebSockets and SSE; Neon's full-stack guide keeps the UI on Vercel, Netlify or another frontend host (neon.com, checked 2026-10-08). Functions are available today for Neon projects in four AWS regions. To keep the frontend, the API and Postgres with one vendor instead, Prisma Compute with Prisma Postgres, Railway, Render and Fly.io each host all three. Compared with Neon plus a separate frontend host, Prisma Compute with Prisma Postgres runs a frontend served by Next.js, Astro, TanStack Start or your own Node.js or Bun server, the API and Postgres from one provider, in one project, on one bill. The Free plan costs $0 for the app and the database, with no credit card and no time limit, and an idle app scales to zero and costs nothing. Once deploy on push is set up, every pushed branch other than the default one gets a preview with its own services and, for databases declared in the Composer module, its own new database; production data is not copied, whereas a Neon branch starts by default with its parent's data. If the app reads `DATABASE_URL`, the preview is only as separate as that value. [Neon alternatives with app hosting and Postgres in one place](https://www.prisma.io/blog/neon-vs-prisma-postgres-app-hosting-in-one-place) compares Neon with Prisma Compute and Prisma Postgres, Railway, Render and Supabase. ## Managed Postgres hosting options that scale [#managed-postgres-hosting-options-that-scale] Six things decide whether the database keeps up when traffic grows. * **Database sizing.** Prisma Postgres autoscales: there is no instance to size or upgrade. Neon autoscales within a range you set, up to 16 CU on Launch. Railway scales a service up to your plan's limits, and you resize the Postgres volume. On Fly Managed Postgres, Render and Supabase you pick a plan or instance size; changing it on Render means a few minutes of downtime (a few seconds with high availability), and on Supabase usually under 2 minutes. * **Cold starts.** Prisma Postgres has no cold starts; Neon by default scales to zero after 5 idle minutes and reactivates on the next query, generally within a few hundred milliseconds. * **Connection pooling.** Prisma Postgres, Neon and Fly Managed Postgres include a pooler; Render has one on paid databases; Supabase has a shared pooler, dedicated on paid plans; Railway adds PgBouncer when you enable it. * **Backups and point-in-time recovery.** A daily snapshot restores last night; PITR restores the minute before the bad migration. Neon, Railway (opt-in, about 4 weeks), Render (paid databases), Fly Managed Postgres, Supabase (paid add-on) and DigitalOcean Managed PostgreSQL (every plan, 7 days) have PITR. Prisma Postgres keeps daily snapshots for 7 or 30 days on paid plans and has no PITR yet; it is coming in November 2026. * **Migrations.** On Prisma, a `postgres()` database with a Prisma ORM contract gets its committed migrations applied before the service starts; a `rawPostgres()` database is yours to migrate. Elsewhere, a release command or CI step runs them over the direct connection string. * **Spend limits.** Prisma's paid plans include a spend limit; on the others, find the usage alert or hard limit before you add a card. ## Where Prisma is the wrong choice [#where-prisma-is-the-wrong-choice] * **Your API holds WebSocket connections open.** Fly.io, Railway, Render and Neon Functions run those; Prisma Compute does not today (support is planned for early 2027). * **You are not writing TypeScript.** Prisma Compute runs TypeScript apps built for Node.js, Bun or Next.js; a Python or Go API belongs on Railway, Render, Fly.io or a VPS. * **You need more than one region, or point-in-time recovery today.** Each Prisma Compute service runs in one of six regions, and Prisma Postgres has no PITR yet (it is coming in November 2026). * **You want the repository deployed with no declaration.** Railway and Render build the code as it is, and on Fly.io `fly launch` writes a `fly.toml` and, for most languages and frameworks including Node.js, a Dockerfile into the repository for you to keep; Prisma needs a Composer declaration today and two changes to each Node.js or Bun server, three if it talks to Postgres. Deploying an existing repository without a Composer file is planned for early 2027. * **Your frontend's main requirement is a global CDN.** Put it on Vercel with Prisma Postgres or another Marketplace database. The full list of limits lives in one place, [Where it has trade-offs](https://www.prisma.io/docs/compute/faq#where-it-has-trade-offs) in the Prisma Compute FAQ. ## Frequently asked questions [#frequently-asked-questions] ### Can I host my existing GitHub repo on Prisma Compute? [#can-i-host-my-existing-github-repo-on-prisma-compute] Yes, once the repository carries a Composer declaration: a `service.ts` for each server and a `module.ts` that composes them, plus two changes to each Node.js or Bun server, and a third if it talks to Postgres. A Node.js or Bun server reads its port from `service.port()` and binds 0.0.0.0, and its other `process.env` reads become service inputs or dependencies; a server that talks to Postgres declares a `rawPostgres()` dependency and builds its client from the injected `db.url`. A Next.js app instead uses the `nextjs` build adapter with `output: 'standalone'`, whose standalone server binds the port itself. A coding agent can make these changes from the [porting guide](https://www.prisma.io/docs/composer/porting-an-app) prompt. Run your build, then deploy with `npx prisma deploy`, which loads the module named by `entry` in the `composer` section of `prisma.config.ts` (`entry: './module.ts'`), packages the build output and does not build for you. For deploy on push, connect the repository and add the `prisma/cloud-deploy-action` workflow; a connected repository without the workflow deploys nothing. ### Do I need Prisma ORM to use Prisma Compute or Prisma Postgres? [#do-i-need-prisma-orm-to-use-prisma-compute-or-prisma-postgres] No: Prisma Postgres runs PostgreSQL 17 and any Postgres client works, whether `pg`, Drizzle, Kysely, `psql` or Prisma ORM. Prisma Compute pairs with Prisma ORM for the typed database client but does not require it. ### Which managed Postgres options have point-in-time recovery? [#which-managed-postgres-options-have-point-in-time-recovery] Neon (every plan), Railway (opt-in), Render (paid databases), Fly Managed Postgres (`fly mpg restore --pitr-time`), Supabase (add-on) and DigitalOcean Managed PostgreSQL (every plan, 7 days) have point-in-time recovery. Prisma Postgres does not yet (it is coming in November 2026) and restores from daily snapshots on paid plans. ## Sources and check dates [#sources-and-check-dates] | Vendor | Pages | Checked | | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Prisma | [Pricing](https://www.prisma.io/pricing), [Compute pricing](https://www.prisma.io/docs/compute/pricing), [Compute limitations](https://www.prisma.io/docs/compute/limitations), [Deploy on push](https://www.prisma.io/docs/compute/deploy-on-push), [Port an existing app](https://www.prisma.io/docs/composer/porting-an-app), [Service input](https://www.prisma.io/docs/composer/service-input), [Composer databases](https://www.prisma.io/docs/composer/databases), [Backups](https://www.prisma.io/docs/postgres/database/backups), [Connection pooling](https://www.prisma.io/docs/postgres/database/connection-pooling), [Postgres extensions](https://www.prisma.io/docs/postgres/database/postgres-extensions), [Prisma Postgres](https://www.prisma.io/docs/postgres), [Compute FAQ](https://www.prisma.io/docs/compute/faq#do-i-need-prisma-orm-to-use-compute), [Billing](https://www.prisma.io/docs/console/more/billing), [Prisma Postgres announcement](https://www.prisma.io/blog/prisma-postgres-the-future-of-serverless-databases), [CLI deploy](https://www.prisma.io/docs/cli/deploy), [Composer getting started](https://www.prisma.io/docs/composer/getting-started) | 2026-09-29; pricing, deploy on push and extensions 2026-10-08; porting guide 2026-10-08 and 2026-10-12; service input 2026-10-12; Prisma Postgres and Compute FAQ 2026-10-21; pricing, deploy on push and backups 2026-10-26; deploy on push and Compute FAQ 2026-10-28; pricing, Prisma Postgres, Billing and the Prisma Postgres announcement 2026-10-30; pricing, Prisma Postgres and Compute FAQ 2026-11-02; Prisma Postgres and Compute FAQ 2026-11-06; pricing, Prisma Postgres, CLI deploy and Composer getting started 2026-11-09; Prisma Postgres, Compute FAQ and Composer databases 2026-11-12 | | Railway | [Pricing](https://railway.com/pricing), [Plan reference](https://docs.railway.com/pricing/plans), [Environments](https://docs.railway.com/environments), [Backups](https://docs.railway.com/reference/backups), [Point-in-time recovery](https://docs.railway.com/volumes/point-in-time-recovery), [Serverless](https://docs.railway.com/reference/app-sleeping), [PostgreSQL template](https://docs.railway.com/databases/postgresql), [What Railway manages](https://docs.railway.com/databases#what-railway-manages), [Connection pooling](https://docs.railway.com/databases/postgresql-pgbouncer), [Private networking](https://docs.railway.com/guides/private-networking), [Scaling](https://docs.railway.com/deployments/scaling), [Railpack](https://docs.railway.com/builds/railpack) | 2026-09-29; PostgreSQL template, What Railway manages, point-in-time recovery and pricing 2026-10-08; pricing, plan reference, Backups and What Railway manages 2026-10-14; Environments 2026-10-26 and 2026-10-28; Scaling and What Railway manages 2026-10-30; pricing and Railpack 2026-11-02; What Railway manages 2026-11-06; pricing, plan reference and Environments 2026-11-12 | | Render | [Pricing](https://render.com/pricing), [Preview environments](https://render.com/docs/preview-environments), [Service previews](https://render.com/docs/service-previews), [Postgres backups](https://render.com/docs/postgresql-backups), [Connection pooling](https://render.com/docs/postgresql-connection-pooling), [Free instances](https://render.com/docs/free), [Private network](https://render.com/docs/private-network), [Postgres extensions](https://render.com/docs/postgresql-extensions), [Creating and connecting Postgres](https://render.com/docs/postgresql-creating-connecting), [Native runtimes](https://render.com/docs/native-runtimes) | 2026-09-29; Free instances, Postgres backups and extensions 2026-10-08; Preview environments 2026-10-26 and 2026-10-28; Creating and connecting Postgres 2026-10-30; pricing and Native runtimes 2026-11-02; Preview environments, Connection pooling and Creating and connecting Postgres 2026-11-06; pricing, Preview environments and Service previews 2026-11-12 | | Fly.io | [Pricing](https://fly.io/pricing), [Managed Postgres](https://fly.io/docs/mpg/), [Attach an app](https://docs.fly.io/postgres/create-and-connect), [mpg restore](https://fly.io/docs/flyctl/mpg-restore/), [Autostop and autostart](https://docs.fly.io/launch/autostop-autostart/), [Regions](https://docs.fly.io/reference/regions/), [Review apps](https://docs.fly.io/blueprints/review-apps-guide/), [Private networking](https://docs.fly.io/networking/private-networking/), [Scale the number of Machines](https://docs.fly.io/launch/scale-count/), [Fly.io vs Railway](https://fly.io/learn/fly-vs-railway/), [Managed Postgres replicas (Fly.io support)](https://community.fly.io/t/mpg-cluster-cross-region-failover/28724) | 2026-09-29; Managed Postgres and mpg restore 2026-10-08; pricing, Managed Postgres and Attach an app 2026-10-12; Attach an app, Review apps and Scale the number of Machines 2026-10-26 and 2026-10-28; Managed Postgres 2026-10-30; pricing, Managed Postgres, Fly.io vs Railway and the support answer on replicas 2026-11-09 | | Supabase | [Pricing](https://supabase.com/pricing), [Backups](https://supabase.com/docs/guides/platform/backups), [Branching](https://supabase.com/docs/guides/deployment/branching), [Connecting to Postgres](https://supabase.com/docs/guides/database/connecting-to-postgres), [Edge Functions](https://supabase.com/docs/guides/functions), [Extensions](https://supabase.com/docs/guides/database/extensions), [Compute and disk](https://supabase.com/docs/guides/platform/compute-and-disk), [Database size](https://supabase.com/docs/guides/platform/database-size) | 2026-09-29; pricing, backups and extensions 2026-10-08; Compute and disk 2026-10-30; pricing 2026-11-02; pricing and backups 2026-11-06; pricing and Database size 2026-11-12 | | Neon | [Pricing](https://neon.com/pricing), [Plans](https://neon.com/docs/introduction/plans), [Scale to zero](https://neon.com/docs/introduction/scale-to-zero), [Connection pooling](https://neon.com/docs/connect/connection-pooling), [Neon Functions](https://neon.com/docs/compute/functions/overview), [Functions runtime limits](https://neon.com/docs/compute/functions/reference/runtime-limits), [Full-stack apps](https://neon.com/use-cases/full-stack-apps), [Postgres extensions](https://neon.com/docs/extensions/pg-extensions), [Branching](https://neon.com/docs/introduction/branching), [Neon-Managed Vercel integration](https://neon.com/docs/guides/neon-managed-vercel-integration), [Autoscaling](https://neon.com/docs/introduction/autoscaling), [Connect from any application](https://neon.com/docs/connect/connect-from-any-app) | 2026-09-29; pricing, scale to zero, Functions, full-stack apps and extensions 2026-10-08; pricing and plans (Functions billing) 2026-10-12; pricing and plans (Functions Free allowance) 2026-10-14; Branching and Neon-Managed Vercel integration 2026-10-26; pricing, scale to zero and Autoscaling 2026-10-30; Connect from any application 2026-11-02; pricing (history window) 2026-11-12 | | Vercel | [Pricing](https://vercel.com/pricing), [Fluid compute pricing](https://vercel.com/docs/fluid-compute/pricing), [Postgres on Vercel](https://vercel.com/docs/postgres), [Environments](https://vercel.com/docs/deployments/environments), [Prisma Postgres integration](https://vercel.com/marketplace/prisma), [Git deployments](https://vercel.com/docs/git), [Marketplace storage](https://vercel.com/docs/marketplace-storage), [Neon integration](https://vercel.com/marketplace/neon), [Supabase integration](https://vercel.com/marketplace/supabase) | 2026-09-29; Postgres on Vercel 2026-10-08; Git deployments 2026-10-26; Postgres on Vercel, Prisma Postgres integration and Git deployments 2026-10-28; Marketplace storage, Neon integration and Supabase integration 2026-11-02; Marketplace storage 2026-11-06 | | DigitalOcean | [App Platform](https://docs.digitalocean.com/products/app-platform/), [App Platform pricing](https://www.digitalocean.com/pricing/app-platform), [App Platform pricing docs](https://docs.digitalocean.com/products/app-platform/details/pricing/), [Databases in App Platform](https://docs.digitalocean.com/products/app-platform/how-to/manage-databases/), [Managed Databases pricing](https://www.digitalocean.com/pricing/managed-databases), [PostgreSQL features](https://docs.digitalocean.com/products/databases/postgresql/details/features/), [Managed Databases](https://docs.digitalocean.com/products/databases/), [Deploy using GitHub Actions](https://docs.digitalocean.com/products/app-platform/how-to/deploy-from-github-actions/) | 2026-11-09 | | Northflank | [Pricing](https://northflank.com/pricing), [Pricing on Northflank](https://northflank.com/docs/v1/application/billing/pricing-on-northflank), [Introduction to Northflank](https://northflank.com/docs/v1/application/getting-started/introduction-to-northflank), [Deploy a database](https://northflank.com/docs/v1/application/databases-and-persistence/deploy-a-database), [Backup, restore, and import data](https://northflank.com/docs/v1/application/databases-and-persistence/backup-restore-and-import-data), [Set up preview blueprints](https://northflank.com/docs/v1/application/release/set-up-preview-blueprints), [Create preview environments](https://northflank.com/docs/v1/application/use-cases/create-preview-environments) | 2026-11-09 | ## Update history [#update-history] * 2026-09-30: first published; competitor prices checked against the vendor pages on 2026-09-29. * 2026-10-05: Neon Free storage updated from 0.5 GB to 1 GB per project, up to 20 GB across all projects, after Neon raised the limit; the Pricing line in the Neon section was re-checked against Neon's pricing and plans pages on 2026-10-05. * 2026-10-07: added a "Leaving Netlify" row to the Quick recommendation and a link to the Netlify alternatives post from the Prisma entry; no prices or vendor facts changed. * 2026-10-07: Prisma Postgres Free storage updated from 500 MB to 1.01 GB, matching the pricing page. * 2026-10-08: the comparison table and platform sections are now in alphabetical order; Railway's Postgres row now says Railway maintains its template, after Railway's docs changed on 2026-10-07; Neon Functions are described as generally available; a Postgres extensions column was added; Railway, Neon, Fly.io and extension facts were checked on 2026-10-08. * 2026-10-14: Prisma Postgres Free storage updated from 1.01 GB to 2 GB, matching the pricing page. * 2026-10-12: the Fly.io row now says Managed Postgres runs in the organization's private network and is attached to an app, instead of putting app and database in one project; the Fly.io Machine price changed from $1.94 to $2.19 a month after Fly.io's price update of 2026-10-01, and Managed Postgres storage ($0.28 per GB) is listed; Neon Functions charges are listed apart from the database's CU-hour price; porting steps now say the port and `process.env` changes apply to each Node.js or Bun server and the Postgres client change only to a server that talks to Postgres, while a Next.js app uses the `nextjs` build adapter with `output: 'standalone'`, whose server binds the port itself. * 2026-10-14: the Railway price cell now lists Railway's Free plan ($0 with $1 of credit a month after a 30-day trial), and the Railway backups cell says volume backups are taken by hand or on a schedule you turn on; the Neon Functions Free allowance is now stated per project; Railway's pricing page and docs and Neon's pricing and plans pages were checked on 2026-10-14. * 2026-10-19: the Supabase section and the one-vendor paragraph now say Supabase Compute, which runs backend services, is a private alpha (us-west-2 only, not for production), checked against supabase.com/compute on 2026-10-19. * 2026-10-19: the Railway previews cell now says PR environments must be turned on in project settings; the Fly.io line in "Where Prisma is the wrong choice" says `fly launch` writes a `fly.toml` and, for most languages and frameworks, a Dockerfile into the repository; the Supabase and Vercel trade-offs and the one-vendor paragraph no longer say two bills when the app runs on Vercel and the database is created from the Vercel Marketplace, which bills it through the Vercel account; checked against Railway's, Fly.io's and Vercel's docs on 2026-10-19. * 2026-10-21: the Prisma Compute + Prisma Postgres entry now says under "What it does" that neither product needs Prisma ORM and any Postgres client works, from the Prisma Postgres docs and the Compute FAQ checked on 2026-10-21. * 2026-10-22: pointed the Railway trade-offs link at Railway's PostgreSQL page and the "What Railway manages" source link at that table in Railway's docs source, because Railway's databases overview page returns 404; the Railway statements are unchanged and were checked against both on 2026-10-22. * 2026-10-24: point-in-time recovery for Prisma Postgres now has a date, November 2026, wherever this post says it is not available yet; until then, paid plans keep daily snapshots. No other facts changed. * 2026-10-26: the Prisma entry's trade-offs now open with the November 2026 date for point-in-time recovery; "Considering Neon but want app hosting too?" now says what Prisma Compute with Prisma Postgres offers a team moving off Neon: the frontend, the API and Postgres from one provider, in one project, on one bill, $0 on the Free plan, and a preview with a new database for each pushed branch other than the default one, without production data; the previews column is renamed "Previews: per pushed branch or per pull request", and its Neon, Prisma, Render and Vercel cells now say what creates a preview (for Render, automatic or manual mode); the Prisma trade-offs say snapshots are taken on days with database activity; the Fly.io section says a Managed Postgres cluster is created in one region while the app's Machines can run in several. Checked against Prisma's pricing, deploy on push and backups pages and Railway's, Render's, Neon's, Vercel's and Fly.io's docs on 2026-10-26. * 2026-10-27: the situation table and the Fly.io, Railway, Render and Vercel comparisons with Prisma Compute now say a preview is for each pushed branch other than the default one, and the situation table adds that a push to the default branch deploys production. Checked against Prisma's deploy-on-push docs on 2026-10-27. * 2026-10-28: the opening now says previews are per pushed branch or per pull request, matching the previews column; the quick recommendation says Prisma Compute and Prisma Postgres come from one provider, on one bill; the quick recommendation, the multi-region row, the Fly.io "Best for" line and the Fly.io comparison now say Fly.io runs the app's Machines in more than one region while a Managed Postgres cluster runs in one region; and the excerpt names the previews the same way as the opening. Prisma's deploy-on-push docs and Compute FAQ, Railway's environments page, Render's preview environment page, Fly.io's Machine scaling, Managed Postgres cluster and review-apps pages, and Vercel's Postgres, Git deployments and Prisma Postgres Marketplace pages were checked on 2026-10-28. * 2026-10-29: the WebSocket row of the situation table, the Prisma row of the comparison table, the Prisma trade-offs and "Where Prisma is the wrong choice" now say Prisma Compute does not run WebSocket servers today and that support is planned for early 2027; "Where Prisma is the wrong choice" also says deploying an existing repository without a Composer file is planned for early 2027, and the Prisma scaling line says there is no database instance to size or upgrade. Prisma's Compute limitations page and Compute FAQ were checked on 2026-10-29. * 2026-10-31: "Managed Postgres hosting options that scale" now opens with database sizing: Prisma Postgres has no instance to size or upgrade and no cold starts, and the Neon, Railway, Fly.io, Render and Supabase lines say how each sizes a database; the situation table adds a row for first paying users and spells out that a preview is for each pushed branch other than the default. Prisma's pricing, Postgres and billing docs and those vendors' pricing and docs pages were checked on 2026-10-30. * 2026-11-03: the situation table adds a row for first paying users in any language, with Render or Railway for the app and Prisma Postgres, Neon or Supabase for the database; the Python or Go row and the quick recommendation name the same databases; the Supabase and Neon paragraph now states the condition first: one bill with the frontend on Vercel and the database created from the Vercel Marketplace, with any other frontend host billing you as well. Prisma's pricing, Postgres and Compute FAQ pages, Railway's pricing and Railpack pages, Render's pricing and native runtimes pages, Neon's connection guide, Supabase's pricing page and Vercel's Marketplace storage, Neon and Supabase pages were checked on 2026-11-02. * 2026-11-06: the Supabase pricing line no longer says point-in-time recovery needs a minimum compute size, after Supabase made the add-on available on all compute sizes for Pro, Team and Enterprise projects; the situation table and "Where Prisma is the wrong choice" now describe the Prisma Compute runtime as TypeScript apps built for Node.js, Bun or Next.js; the "First paying users, any language" row says how Render sizes its own Postgres and how Render, Railway and Prisma Postgres pool connections; the Vercel section lists the Marketplace Postgres providers in the same order as the opening; the Render previews cell says automatic mode covers every pull request against the Blueprint's linked branch; and the "What Railway manages" source link points at Railway's docs, because the GitHub copy now returns 404. Supabase's pricing and backups pages, Render's preview environments, connection pooling and Postgres connection pages, Railway's databases page, Vercel's Marketplace storage page and Prisma's Postgres docs and Compute FAQ were checked on 2026-11-06. * 2026-11-09: "Platforms with app hosting and Postgres in one place" adds short entries for DigitalOcean App Platform and Northflank, which also host an app and Postgres with one vendor; neither is in the comparison table, and the seven compared platforms keep their rows and order. The backups line under "Managed Postgres hosting options that scale" and the FAQ on restoring to a point in time now also list DigitalOcean Managed PostgreSQL, which restores to any point in the previous 7 days on every plan. DigitalOcean's and Northflank's pricing pages and docs were checked on 2026-11-09 and are listed under Sources and check dates. * 2026-11-09: the "First paying users, any language" row now starts with the database (Prisma Postgres has no instance to size or upgrade, includes PgBouncer pooling on every plan, and its Starter plan is a $10 base), then covers the app hosts and their own Postgres, and ends with two bills once both providers are on paid plans; the Fly.io entry says every Managed Postgres plan includes high availability, and that the cluster's replica is a standby in the same region, with no read replicas; the situation table, the Prisma entry and the FAQ on existing repositories now show `npx prisma deploy` (and, in the Prisma entry, `npx prisma dev`) with no `module.ts` argument, since the Prisma CLI reads the entry from the `composer` section of `prisma.config.ts`; the Northflank note says how paid usage is billed on Northflank Cloud and in your own cloud account, that Northflank's pricing docs ask every user to add a payment method before creating resources, whatever the plan, to verify their identity, and advise against using the free tier for production; that line replaces the earlier wording on whether the Sandbox needs a card. Prisma's pricing, Postgres, CLI deploy and Composer getting started pages, Fly.io's pricing, Managed Postgres and Fly.io vs Railway pages and a Fly.io support answer, and Northflank's pricing page and pricing docs were checked on 2026-11-09. No other facts changed. * 2026-11-12: the "First paying users, any language" row now names the database first, Prisma Postgres, Neon or Supabase from any Postgres client, then Render or Railway for the app; the Prisma entry's "Best for" line says neither product needs Prisma ORM, and the one-vendor paragraph describes the plain connection URL a `rawPostgres()` database gives any Postgres client before the optional Prisma ORM path; the Neon backups cell gives the restore history window (up to 7 days on Launch, up to 30 on Scale); the Supabase pricing line says the Free plan's database size figure is a billing quota, not the disk size, and the Free disk is 2 GB; the Railway "Best for" line says PR environments are turned on in project settings, and the Railway pricing line separates the 30-day trial from the Free plan's $1 of monthly credit and says usage beyond Hobby's included $5 is billed per second, and the plan reference links point at Railway's current docs address; the Render entry says single-service previews are turned on per service and a full preview environment needs a `previews.generation` setting in the Blueprint. Neon's pricing page, Supabase's pricing and database size pages, Railway's pricing, plan reference and environments pages, Render's pricing, preview environments and service previews pages, and Prisma's Postgres, Compute FAQ and Composer databases pages were checked on 2026-11-12.