#Inconsistency in pricing

4 messages · Page 1 of 1 (latest)

lone sinewBOT
#

You've gone full bot mode! Let me fetch that AI answer for you ASAP.

lone sinewBOT
# lone sinew You've gone full bot mode! Let me fetch that AI answer for you ASAP.

You’re right to notice this – there are two different kinds of “connection limits” being talked about, which is what makes this confusing.

  1. Prisma Postgres (managed database from Prisma)
    For Prisma Postgres itself, the docs state that the connection limit is fixed per plan and cannot be changed. On Starter, the pooled connection limit is:

    But when you connect via direct TCP (bypassing Prisma’s pooling), there is a separate, lower limit table where Starter is Max 10 connections. [Direct connections]

    So:

    • Using Prisma’s built‑in pooling to Prisma Postgres → up to 100 pooled connections on Starter.
    • Using direct TCP to Prisma Postgres → max 10 connections on Starter.

  2. Prisma Accelerate + your own database
    The Accelerate connection limit is configured in the Prisma Console. Autoscaling is only available when the Accelerate connection limit is set above 10, and this is only possible on Pro and higher; Free and Starter are capped at 10 and cannot be increased. [Autoscaling Accelerate]

    That’s why your Accelerate dashboard shows 10 and doesn’t let you change it on Starter.

Effective limits on Starter:

  • Prisma Postgres (with built‑in pooling): up to 100 pooled connections.
  • Prisma Postgres via direct TCP: 10 connections.
  • Accelerate with your own database on Starter: 10 connections, fixed; autoscaling and higher limits require Pro or above. [Autoscaling Accelerate]
opal ibex
#

So, you mean when I use starter plan: Prisma Postgres + Accelerate, Starter Plan, I get 100 connection size ? even on Dasboard it says max 10 and cannot be changed?

lone sinewBOT