For context, it looks like Puffin web browser's architecture is to run on the server side and render in a virtual appliance -- something like a "remote desktop"

For context, it looks like Puffin web browser's architecture is to run on the server side and render in a virtual appliance -- something like a "remote desktop". This would be a category of apps called "DaaS" or "Desktop as a Service": https://www.google.com/search?q=daas+%22desktop+as+a+service%22 https://www.google.com/search?q=daas+%22desktop+as+a+service... So, resource limits like cpu would be inevitable because Puffin's servers are the ones running Javascript, etc. The remaining question is how Puffin is communicating those limits to potential users. Instead of being hidden, you have to be transparent about it to discourage unreasonable users from signing up and leaving complaints. Interesting that the blurb on the app's description says: "* Users can pay a subscription for unlimited use." With dangling that "unlimited" feature to encourage people to pay, Puffin set themselves up for so-called "abusers". Companies never seem to learn their lesson on advertising "unlimited" features.