This message was deleted.

Don’t stress out too much, you still have time. When you reach 80% you might want to contact Airtable support to increase the limit of 50k, not sure if that’ll work out but worth a try. Otherwise, duplicating your AT base and Stacker app for your new customers will still be a possibility, although harder to maintain consistently both bases/apps. It’ll also give you more time to figure out a more scalable solution.

@white-scooter-70446 can I duplicate the app and all fields across to a “server 2” so speak without having a mental breakdown? I have some automations that’d be a massive pain but otherwise yes thanks @sticky-night-20812 not a bad idea

You can duplicate both the AT base and the Stacker app, then change the App2 to link to the Base2 and everything should just work as-it. It gets harder if you use several bases with synced tables, but still doable.

@orange-computer-53672 To answer your question—we don’t have immediate plans for a write-enabled sql integration, but I’m pretty sure we’ll look into it at some point in the future. What Ambroise suggested should give you a decent amount of headroom. I personally haven’t tested any alternatives that support sql write, so I can’t really make any recommendations, though perhaps someone here might know a tool or two.

https://noloco.io has their own db solution that supports unlimited records – might be worth a look

Hmmm, Noloco looks surprisingly like stacker 🤔

Noloco will not solve anything by itself, since the 50k limit comes from Airtable. Although, migrating from airtable to Postgre would lift the limit, and then you can use Noloco. But maybe by the time you’ve done all this Stacker will have added support for writes in Postrgre and maybe the Stacker > noloco switch won’t be necessary.