When I started building things with Bubble I always wondered if everyone was using best practices to not overload the server where my projects were. This has always been a concern. I always found myself imagining someone inexperienced programming an endless loop of actions that could crash or freeze the server.
Unfortunately, I have seen countless projects that used servers in a completely unnecessary way, with actions running every second. In a collective environment (in this case, shared servers) it is essential that everyone develops in a respectful manner. The problem is that “developing respectfully” is a concept that involves understanding technical details and most nocode/lowcode developers do not have this knowledge and, in some cases, because they don’t have any extra costs for it, they simply don’t care…
In short… charging based on how much the server is being used seems fair to me. And as @J805 said, it forces us to develop in a conscious way (since 99% of Bubble projects run on shared servers).
The problem for me is that this change was implemented without much documentation, there was a lack of transparency and to this day it is a cause for distrust, as monitoring this consumption is still a pain in the a**.
But honestly, I see Bubble working hard to improve this issue day after day. I think it’s just a matter of time until things get sorted out.