Can anyone please help me answer some of the following questions:
I was told that my Starter plan has 100GB of bandwidth. You can refer to this link: Pricing and plans | Bubble Docs. If I upload 200GB of videos and regularly play on my website, then, will it exceed allowed Bandwidth for my current plan?
What is the difference between Workload Units and Bandwidth please?
When I plays a video file on my Bubble app (Through a video player Plugin), then, will it be counted as Bandwidth or Workload Unit? All my videos are hosted on Bubble storage
Is it possible to buy Extra Bandwidth?
I use Bubble to collect videos from Students and then Teachers watch those videos for grading. Can you please offer me a better solution, a solution that may be better than using Bubble’s extra storage?. I know that Bubble uses CDN and it helps to load things very fast.
I’ve never actually noticed this, and thought that as WU were added, there should be no other constraints on traffic… Come on Bubble, you said you just wanted to give one thing to think about that encompasses everything (WU) but then add this…
Playing files would likely not consume bandwidth as files are not distributed through Bubble but through AWS.
@fede.bubble can someone from the team explain what this is about? There were never any announcements about Bandwidth.
Is this just for file storage? Is it bandwidth for my entire app? If it’s for an entire app why do I have to pay more as a solo developer?
Edit: More questions I want answerd:
What happens when my app hits your bandwidth limit?
What affects bandwidth?
Again… I already pay for WU Tiers and overages. I’m a solo dev who doesn’t need features from other plans so this looks like you’re singling folks like me out and trying to get me to pay more for shit I don’t need.
I’m confused, too. The documentation distinguishes between file storage and bandwidth, as shown by the link in the original post. However, when I visit the pricing page (Pricing | Bubble) and click “See full comparison” and then scroll down, I see the file storage limits per tier but no mention of bandwidth limits per tier.
Workload is how much work your app does, and bandwidth is how much work it takes to send it to users. We’re already charged workload for page load so who knows.
As we haven’t encountered these bandwidth limits, I’d hope they’re arbitrarily large such that you don’t need to worry about them.
I use Wasabi regularly and find it good! Use @redvivi ’s plugin to connect a Wasabi bucket.
Remember when Bubble said that they wanted to make their pricing simpler? Since then we have had the introduction of terms that require an encyclopedia of knowledge to understand which still aren’t actually clear.
Where can we measure bandwidth within our apps? Surely this would be as essential as all the half working tools for measuring WUs.
Thanks! I’ve not checked that section in a while but I do not recall any announcements about bandwidth. Also there’s way too little (close to none) information or clarity for something that affects costs and sounds like it affects performance.
Concern would be that there is no way to track it, nor is there any mention of it on the pricing page. It doesn’t show transparency when things like this are slyly introduced on one page that not everyone would likely check. It should be mentioned everywhere that pricing and plans are mentioned, not a hidden afterthought. Users should also be able to track it to give confidence that it actually is being calculated correctly.
Essentially what was already said: it’s a limit to protect Bubble from very rare edge cases where apps could incur in extremely high amounts of bandwidth. But I’ve been told the limits are set really high to the point that it’s almost a theoretical limit at that point.
If it’s a theoretical ceiling, then why the huge difference in bandwidth between tiers? We’re talking more than twice between starter and growth then another 2 times increase after.
Why must a solo dev like myself be “theoretically disadvantaged” for not wanting to pay for features that I don’t need?
I sound like I’m whining but a lot of the value from developing in Bubble goes back to the non-profit organizations I build for. I have to think ahead if I am expected to increase my costs for whenever I may hit these edge cases when I scale.
I’ll ask but I would imagine it has to do with the typical bandwidth usage in each tier. For each tier this limit should be so high that very few apps will run into it
Why is it not public though? Full transparency is not something that should be avoided. It just adds to the unknown when building on Bubble. There is absolutely zero reason for it to not be public.
which still aren’t actually clear.