Read and Write limits seem to be very low

I feel like some people might take this as a rant about the recent pricing changes but honestly, it’s not. I really like Appwrite, and I’m genuinely just trying to understand where it fits in now, especially compared to other platforms like Firebase.

The new pricing model introducing limits on database reads and writes makes sense—what the blog explained was fair, and I get that sustainability is important. But looking at it from a beginner or hobbyist dev’s perspective, the quotas on reads and writes in both the free and pro tiers feel kind of tight. Especially when you stack it up against something like Firebase, which, despite its own pricing quirks, still gives a lot more breathing room in terms of database usage.

Appwrite does a great job balancing this out by offering super generous limits on things like functions, bandwidth, storage, and user management. And that's honestly great. But here’s the thing when someone is just starting out and building their first or second app, the one thing they’re going to hit the most is the database. Most tutorials aimed at beginners don’t really talk about caching, efficient querying, or how to reduce reads/writes. So they end up burning through those limits without even realizing it. Meanwhile, 750k function executions per month feels like way more than a beginner or small project would use, especially early on.

So I was thinking maybe there could be more flexibility in how resources are allocated. Like, what if users could choose between boosting database ops or function executions depending on their project needs? Or maybe a daily quota system like Firebase has, which kind of helps distribute the load and makes limits feel less intimidating?

Again I just started with Appwrite a few weeks back so I don't know if this works differently than what I anticipate.

Just throwing it out there, but I feel like giving people the ability to tailor their usage a bit more could really help newer devs stick with Appwrite instead of jumping to something more familiar like Firebase just because they hit the read/write cap early.

Not complaining at all. I love what Appwrite is doing and how much it's grown. Just hoping this kind of feedback helps spark ideas that make it even better for everyone.