Hi,
Greetings Webbers!
I want to know if there is a parallel in the webweb+Supabase stack regarding “Updates” in glide and “Workload units” in bubble.
Basically the full stack platforms like Bubble/Glide have these “extra unpredictable” charges that they charge per operation for CRUD operations, certain workflow actions or for making API calls via certain integrations. I understand its the cost of technology and also the fact that these are full stack solutions.
But since weweb+supabase is a splitstack solution, will this be the case for weweb+Supabase also? Like under what circumstances will i end up paying “extra” and above the monthly subscription charges.
With WeWeb today, there is no hidden “workload unit” or “update” system like in Bubble or Glide.
Instead, usage on the WeWeb side is mainly tied to more classic web hosting metrics such as bandwidth and sessions, very similar to how traditional web hosting works.
In practice, this means:
You are not charged per CRUD operation, workflow step, or per API call on the front end.
You only start to care about hosting limits when your app reaches a meaningful level of traffic (number of users / sessions and the volume of data transferred).
On top of that, because the stack is split, anything related to database reads/writes, auth, storage, etc. is billed directly by Supabase under their own transparent limits and pricing.
PS - We are working on a new full‑stack experience that will bring more of the backend side into WeWeb itself.
Because of that, there may be new usage metrics or pricing dimensions introduced for that full‑stack offer, but there is no finalized public information to share yet on how those will be counted.
