Whenever i see these cloud apps that seem like a good idea, I just think of spiralling costs similar to the likes of firebase written about on HN before.
Their pricing page doesn't show anything about usage limits and if it is "per site" or "per domain" or "per project".
Pricing is per-developer-seat; we don't limit the number of apps you can build or publish.
Usage limits are pretty soft right now (depends heavily on what you do in your code and how hard you're hammering our servers), but the general intention is to charge you more as you scale up your team, rather than because you got a few thousand users.
It is this lack of clarity (published limits) that scares many of us. It basically says that we won't know when we'll be cut off or shut down, but we'll find out when it happens!
So if we build something that becomes wildly successful, we could suddenly be in a world of hurt if our site is deemed too heavy and we're throttled or worse. It would be like Pokemon Go - big explosion, lots of tiny pieces, customers gone.
I urge you to have some kind of professional plan with guaranteed tiers. Otherwise, only naive people or people who really don't care about the future will use it (outside of the prototyping case everyone else is mentioning).
On the other hand, it would be the perfect tool for someone on upwork or the like to do a gig ultra fast, leaving the client to deal with all the future pains. But since most projects end up not huge and successful, that might be just fine!
So as long as I build the next Twitch on my own you guys will just charge me $50 per month? That’s freaking awesome! It’ll save me $5300 per month in hosting already!
Does Anvil render server-side or is it client-side only?
My issue is if being used for websites, on average our sites get ~50k visitors a month or even spikes with that amount.
The same goes for complexity of the system, for simple html sites it will not matter much but for very dynamic apps this will require a lot of CPU time.
Reading the docs, it says the Forms run on the client, so most rendering should run too. Client-side rendering - while it has its disadvantages - shouldn't be worse for the CPU time than server-side, though. What's your concern?
Their pricing page doesn't show anything about usage limits and if it is "per site" or "per domain" or "per project".