# WeWeb database compute hours

**URL:** <https://community.weweb.io/t/weweb-database-compute-hours/21711>\
**Category:** Ask us anything\
**Created:** [October 16, 2026, 7:09am UTC](https://community.weweb.io/t/weweb-database-compute-hours/21711 "2026-10-16T07:09:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![christoffer](https://avatars.discourse-cdn.com/v4/letter/c/e56c9b/32.png) [@christoffer](https://community.weweb.io/u/christoffer)\
**Post date:** [October 16, 2026, 7:09am UTC](https://community.weweb.io/t/weweb-database-compute-hours/21711/1 "2026-10-16T07:09:13Z")

</div>

I really like WeWeb’s approach of bringing logic, interface, and database together in one platform. Sure, I’m putting all my eggs in the WeWeb basket, but in my experience, having one potential point of failure is better than relying on several separate services connected by flimsy APIs.

So far, after about a week of building and testing, my experience has been good. The WeWeb database’s startup and load times aren’t the fastest, but they’re fine for now.

The main concern is the CU-hour limits on the Cloud plans. I’m about to use up all the CU-hours included in the Grow+ plan after just over a week of internal building and testing. The other limits in the Grow+ have barely been noticeable. This means Scale+, with extra CU-hours on top, seems like the only realistic option for a real-world system. That would cost an extra $200 per month compared with connecting to Supabase.

I can really see the benefits of an integrated database, but in my view, the compute costs can quickly outweigh the benefits!

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [October 16, 2026, 2:12pm UTC](https://community.weweb.io/t/weweb-database-compute-hours/21711/2 "2026-10-16T14:12:05Z")

</div>

> [@christoffer](#):
>
> I’m about to use up all the CU-hours included in the Grow+ plan after just over a week of internal building and testing.

Ah yes, depending on the use case, the current limits can get triggered quickly. Part of this comes down to our database auto-suspend settings: how long the database stays active before automatically suspending. Suspending sooner can reduce CU usage, but more frequent wake-ups can make the app feel slower. We’re still working on that balance, and the team is exploring ways to give you more control over this setting.

Could you send me a link to your project in a private message? I’ll ask the team to look into it.