[nikolasburk]

Our pricing for Prisma Postgres indeed presents a bit of a mental shift compared to traditional database providers:

We charge for query volume, not for compute!

We believe that ultimately this is a more intuitive way for developers to think about database cost.

Generally, our goal is that developers need to only think about _queries_ — we'll take care of everything else to make sure those queries can run efficiently. Developers shouldn't need to worry about compute, scaling, downtime, etc.

[gigatexal]

How about the scenario where I do a select … where … on a view and that view is defined to have 5 CTEs on different tables and then a final select doing some complex stuff there.

Is that billed as one query or 6?

[sorenbs]

That would be billed as a single query. We think this is a much simpler way to reason about your cost compared to counting rows scanned, CPU time consumed or something more granular like that.

If your query is very expensive, it will take longer to complete, and that will be a signal to you the developer to simplify your query or identify an index that can help speed it up. Prisma Optimise will help you identify and improve such queries.

[gigatexal]

While I think as an arm-chair business wonk y’all should count it as 6 queries and not 1 as a payer and consumer I’m even more likely to use it now that you count us as only a single query. :-)