Database computing and record limitations

Hello,
I’m trying to building an internal tool for our organization, we have been using softr so far but the database record limitation is very low.
I have been recommended to use bubble for more complex internal tools and web apps, but I needed to know a few details regarding the built in database of bubble, so my questions is as follows:

  • As we are trying to integrate data and automations for all our works, we expect the data records as whole to be around 1 million record per 2 years period, with the max a one table can reach during those 2 years to be around 400k rows, the records doesn’t include files, only text and numbers, so can bubble database limit handle this?
  • and based on the above, does bubble have the computing power to load this kind of data without being slow?
  • and if needed is it easy to migrate data from bubble database to external database like supabase?

and what do you recommended for my use case?

sorry my questions are running long, but I needed to know this details before is started t ensure everything will work smoothly, appreciate your feedbacks.

  • Bubble doesn’t have a hard limit on records — 1M is doable. Just make sure your database is structured well. Performance issues usually come from poor data design, so consider things like satellite fields and other Bubble-specific optimisations (not traditional relational DB thinking).
  • On computing power: depends on how you load data. If you avoid loading everything at once and skip complex searches on-page, you’ll be fine for most use cases.
  • Yes, you can migrate data out. Either build a workflow that sends data to an external endpoint (e.g. Supabase) or just export it manually. If you go the workflow route, watch your WU usage — that’s where costs can creep up.
2 Likes

Thanks alot, appreciate your response, was very concise and informative