Thanks for the feedback! Honestly, we're still dialing in the tiers, what row limits would feel reasonable to you for your use case? Always helpful to hear what people actually need.
To be honest, I think 1M rows is starting point for any paid plan. Any data model of minimal complexity explodes fast, especially with cascading one-to-many relationships. If anything, it may make more sense to have a table-level, rather than a global, limit. Or put the limit on "trunk" tables.
That is a really good point one-to-many relationships blow up fast. The trunk table idea is interesting, would simplify how people reason about limits. Appreciate the feedback, genuinely helpful!
bdcravens|1 month ago
tbrannan|1 month ago