Bubble is a platform for apps of all sizes. Whether you’re launching a new idea or scaling a business, it’s our responsibility to support our users by growing in a sustainable way. In order to do so, we have a usage-based pricing model so users will only pay for the resources their app uses.
Our mission is to make software development more accessible — Instead of requiring users to monitor all of the various metrics in a traditional tech stack built with code, we introduced a single pricing metric to track resources needed for each app: workload.
In this video we will break down the concept of Workload and explain how it helps simplify the complex infrastructure behind your app. You'll learn how Bubble tracks server-side activities using Workload Units (WU), which aggregate various metrics like database searches and other server tasks, so you only need to focus on a single metric to manage your app's resources.
We'll explore examples of server-side versus client-side operations, highlighting what contributes to Workload and what doesn’t, giving you the tools to optimize your app's performance without unnecessary overhead. Whether you're new to Bubble or looking to fine-tune your app's efficiency, this video will equip you with the knowledge to build smarter.
Check out the full manual for a detailed list of activity types and their Workload costs.
Manual ➡ manual.bubble.io
* * * * *
Chapters 0:00 - What is Workload? 0:21 - Workload Units 1:31 - Understanding WU Starting Costs 2:18 - WU Example (Custom State) 4:08 - Client Side vs Server Side 4:28 - WU Example (Repeating Group) 5:08 - Conclusion
Built on Bubble
