Pricing for high fan-out + high cache hit use cases
Hey folks, I recently started experiment partially moving a project of mine to use convex and I'm a bit reluctant to fully move over due to the pricing structure.
We are building realtime-ish online game rooms (think e.g. Poker) and have tried many technologies to globally share the game state (manual websockets, SSE, supabase realtime, and most recently convex) and Convex has been the most compelling option by far but it feels slightly unfair that each user connected to the game room (in the case of Poker that's 9 users all getting the exact same game state) gets charged a full function call despite it being cached by the first client to request it.
Are there any plans to revise the function calls pricing model around these high fanout high cache hit use cases?
2 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
yes! there is a planned second sku called "the scale plan" which prices out caching benefits. higher scale sites need this plan
since we haven't publically shipped this yet, we normally just work this out on a 1:1 basis with our existing customers when they get adoption