Currently the breakdown for synced row capacity is as follows…
Starter: 2,500
Pro: 25,000
Business: 50,000
Synced record limits have now become a discussion point with every business when I’m scoping a project with intent to build in Noloco.
I understand synced rows have implications for Noloco, but so many people rely on 3P data sources (e.g. Airtable, SmartSuite, etc). And even if a tool can avoid reaching capacity for, say 2 or 3 years, that might make you feel like you’re great to go. But the point is that they will indeed hit it after 2 or 3 years at which point you have to
delete or archive old records from your database, or
move to enterprise so you can get a custom synced row capacity
Many of my clients are okay for now (though one of them is definitely going to need Enterprise), but again the main point is that in maybe 2 or 3 years, none of them will be okay.
Perhaps there are other approaches here that can solve this scaling challenge, but right now increased sync row limits seem reasonable (compare with Softr’s Business plan, which allows for 200,000 records).
To be as constructive as possible, maybe one other approach is enabling data-source sync conditions. So when you use Airtable for example, you can define in the data settings the conditions under which a row should sync in the first place. That way, the “cleaning” or “archival” approach can be automated such that any records that are 1 year old (for example) don’t sync into the app.
But even that is purely a functional solution, and I reckon for many it is not an effective business solution as you then lose the ability to interact with the aforementioned data in your app, since it’s “archived” (no longer syncing).
Working in Financial Services in the UK, we have to retain data for a minimum of 7 years, sometimes 32 years
I’m not far off our Noloco limit now so decisions to be made here at some point. I made a feature request for exactly what you suggested above, not ideal but the only way I could see a way around it.
Using sql we wanted to run a query for whats synced from out external database, rather than grabbing everything. We currently have data back to 2015 syncing to Noloco, its never used, even for reporting but we have no way to stop it. I may need to think of archiving the data off to an archive table on the sql hosting, its an option but messy
That’s a great example. I’ll also run into a similar issue as one of my clients has stringent data requirements, I think stretching back several years.
I used Stacker before I found Noloco, and that had an option to filter at source the data you wanted to bring in, which could be very helpful for the above scenarios.
Also at the time I was cloning Stacker apps for clients, but all data was in one Airtable base, so filtering data at source was also very helpful for that case.
It’s not the same thing but it would be also very helpful if you introduce a fixed price for a number of extra rows as overages, just like you do in file storage or user limits. That way, we would have the liberty to purchase extra rows without needing an upgrade.
YES! That’s exactly where I got that idea from. I also came from Stacker, that was the first app builder I learned. Would love to see that feature in here.
…yes, and without the ambiguity of a custom contract/negotiated plan. Having the upfront transparency would be so helpful so we can know exactly how much we’ll need to pay for X more rows, and can plan accordingly.
Though in my mind this is a supplemental solution, paired with an increase in base row capacity across all plans (ideally haha ).