Okay - it helps to know more about the solution and especially the scale that we are dealing with. So let’s unpack this a bit more.
First and foremost, when asking for help, sharing details and design aspects as they relate to your requirements is very important if you want experts to help you. You need to provide more information concerning the requirements in cases like this.
Based on what little I know about your project, you want federated data services that fly above the base level of Airtable. Data federation is not something Airtable provides and suggesting it’s easy to do is not likely to make it so.
Second, I just want to be clear – you intentionally picked a platform (Airtable) to build a solution that requires more than a dozen bases for which you knew – or should have clearly understood – was incapable of performing cross-base roll-ups, right?
Don’t you think you (or your solution) may have expectations that are outside the realm of what Airtable designed bases to address? Is it possible you may have failed to assess the complete requirements before assuming these features would exist?
I think - as solution-builders - we all have some responsibility to fully assess the capabilities before launching the implementation strategy. Assuming you did, you must also embrace the idea that this capability …
… must be created using aftermarket tools and services. I would risk saying that this is typically done through integration logic but surely not in Script Blocks or Script Automations - the scale is simply too vast. Furthermore, the requirements and scale of the data is too vague to offer you any additional recommendations.
In my view, you need a consultant who has experience building umbrella services that span multiple bases and even multiple workspaces. I suggest posing this as a consultant-needed article complete with a process diagram and at least a requirements sketch.