Softr’s largest datasource segment of users is Airtable. According to Softr, this is why they haven’t implemented real time sync with Airtable yet. Regardless of the size of the company, if a database is fast, powerful enough, and can scale, it will be preferable over a slow datasource. My guess is that this is what Softr would want for its in-house database and its users.
Or, prove me wrong and implement real time sync with Airtable before you release any more improvements to Softr’s database.
@Ben Airtable sync is currently the most real time as it used the API directly which is slow… Airtable’s Synced version will be available end of August. and obviously moving 10+ integrations into new Data layer and adding our own database in no way contradicts each other…
Its not obvious, but will depending on which integrations are implemented, in what order, and for how long it takes for each to be released. Not to mention how much each will cost and wait time. It becomes obvious, and more importantly evident, when we are using a feature that was proposed and it actually performs well.
It’s now September. Earlier we were told this would be released 2nd quarter 2025. Unless I missed something, this still has not been released.
@Ben rollout is in progress since August we are facing issues and fixing… it’s there without affecting apps.. we need to make sure we don’t break apps… we will let you know very soon… could take another week or two until fully rolled out
Hi, has this been implementned?
Is the only workaround, currently to do custom javascript coding to catch the event of the user action, and then dispatch an update? If that is the case, could I get custom code for free on my free plan? 
Would love an update on the refreshing data in a list block - thanks kindly.
Hi all! There is now a workflow step that you can run (Via Softr workflows) to refresh the page after a series of workflows run, while showing your users a wait screen making this all possible without code now!!!
@artur it is now November, and Airtable real time updates (A.K.A. Airtable DSV2) still has not been released (Q2 2025 was the original release date). While waiting this year, Softr’s in-house database, workflows,… AI and others have. Can you explain why it’s taken so long and more importantly why these other features were released already when the Airtable synchronizer is evidently way overdue for deployment?
@Ben the rollout is in progress we can’t make it faster at this stage… we just need to make sure we don’t rush and break apps. Hence this is taking time as we discover issues in background and fix them while we are rolling out in the background. In fact some of the entities like users, detail page’s record etc are already done via new approach it’s just not noticable until all is done…
Thanks for the update @artur. As a Business user, we would have been more excited about DSV2 had it been released prior to the “New Softr” earlier this year. Caching Airtable for real time updates has been around for quite a while actually. Also, legacy builders would have been more motivated to adopt and promote Softr’s new Datasource and Workflows had you grandfathered us in for the new corresponding plans, rather than requiring us to upgrade for them.
Big news this morning 
Here is the rub in this response:
Lets take Smartsuite users as an example (like me).
Smartsuite has an API call limit of 500000 calls per month, exceeding this limit is very costly, $15 per 1000 calls costly. SOFTR is in control of the API calls, when connected to Smartsuite, and according to Smartsuite, is the responsible party for trying to reduce API calls that are made (be more efficient). But…..
SOFTR has their own, competing database solution, with a vested interest to get users on said database solution, away from Smartsuite (or Airtable, or others). Making their API calls more efficient is counter intuitive, if the goal is to get users on SOFTR’s database solution…..
SOFTR knows, the user getting away from these outside database solutions, will reduce the user’s costs, so they think this is net positive for said users. But what they do not take into account, is that SOFTR (as far as I can tell) was started on the premise that you could connect and NO CODE build solutions to create a better public face, for databases like Smartsuite, and Airtable. This was their value proposition, what made SOFTR, SOFTR.
A lot of sweat equity is expended by SOFTR’s users, in building foundations through these outside database solutions, like Smartsuite and Airtable. Switching over from them to SOFTR’s in house database, is no walk in the park. Especially when apples to apples comparison between what SOFTR is offering, versus the others, is just NOT possible, yet.
What is my point?
As a SOFTR user, and a SOFTR fan, I can see WHY the play was made to create an in-house database solution, versus relying on the existing solutions to be the foundation of their (SOFTR’s and the user’s) apps and build-outs. And I hope, in the near future, it becomes the power house it could become. But to get there, SOFTR should leverage loyal, legacy users, to build the plan and vision out, instead of strong arming them into “upgrading”, or “saving costs”.
Thanks for sharing your opinion, but I want to note that your message contains many assumptions that could mislead others. By now, it should be apparent to all our users that Softr has ALWAYS put the customer at the forefront of every decision, whether product or pricing. Softr has the most generous pricing plans on the market for the value it provides.
There are always many considerations to take into account when making a pricing decision and how it applies to existing paying customers (technical, business, product, etc).
Softr’s mission has always been to be the best platform for building business apps - being the best interface builder on top of existing DSs has been the first step, by no means the main goal or the end goal.
Like mentioned in my email, 70%+ of new users who signed up with a business use case in mind couldn’t leverage Softr because they didn’t have an external, structured database or couldn’t build one with Softr. Our goal with the Softr Databases and Workflows launch has not been to convert existing data source users into Softr DBs, but to enable all other users mentioned above to build with Softr. In fact, we have always been open about our goal to continue investing heavily in our 3rd-party data source integration ecosystem, because almost every company stores data across multiple data sources for different reasons.
If Softr Databases work better for many of our existing customers, help reduce costs and complexity, and are the right choice for the task, then amazing —we are only happy to welcome everyone to migrate to Softr Databases. That’s why we opened them up to all existing users—not because we saw this as a way to get more revenue from existing customers, but because we want them to stay and build and grow with Softr long term.
So my ask is, as loyal customers who believe in Softr and want to be with us in the long run, help us improve and iterate our product and pricing. Please be more mindful of how you share your opinion, what you share, and how closely it aligns with reality—it impacts and sometimes misleads other users who come to this community to learn from you all.
Sorry, I have to wade in here, I absolutely LOVE Softr, it’s an amazing product but I have to agree with @Lockdown155 in this post and this one …
@Lockdown155’s response on this thread is to @Jjenglert’s response (which he copied in) - I don’t know how else they were supposed to take this response other than being ‘strong armed’ into upgrading - which they did and then it turns out they didn’t need to! He is trying to help you improve.
Communication is key 
Appreciate your time and feedback and want to directly answer to a comment you made above.
The API integration that Smartsuite uses is a centralized data modeling system that now powers all of our data sources. We are doing this to provide you, the builder, with the best experience possible.
Now it’s true that our data modeling system requires a lot of API calls in order to get a fast sync and to get a fast performance needed. But this is not unique to Smartsuite, as it is a unified model. What is unique to Smartsuite is that they have a low API limit, which with our advances on making our performance better has now clashed with the amount of API calls we make in order to deliver a better product for you.
Unfortunately, in your case, I think your app has grown to be big enough to warrant using another database that works with Softr better and doesn’t conflict in the way that it is for you with the API limits that you need. This is an unfortunate situation of how the tech has progressed (for the better I’d like to think), and how external providers have applied limits or updated their pricing which now conflicts with certain types of apps being built with this integration.
From a pricing perspective, I’ll say this, which is not an official company message, and is just my own personal take.
We’re trying to do the best we can, for you, for us, and with consideration to the competitive market that we are in… We are launching new products for the first time, which we’ve invested significantly in. We don’t know how they will be received. We hope well, but there is a lot of uncertainty with any new product.
Also, the market is changing quick. Pricing is being updated all over the board, and we’re continuing to do what we can to provide our builders with the best options available. This also means staying open to your feedback, and adjusting along the way.
So when we launched these new products for the first time, we priced them the best way that we thought at the time. Then, after time progressed, and we heard all of your opinions, we changed our minds from the input you all provided and other factors at hand. This wasn’t our plan, just where we ended up, and I hope you all continue to benefit from that as our customers are at the core of every decision we make.
@Mariam @Jjenglert Thank you for the prompt, professional replies. I want to start by saying, first and foremost: I come across as negative towards SOFTR, BUT it is not directed at the product itself, the product works, it does what it says it will do, and overall I am happy with what it has allowed me and my team to build (we could have never done it without SOFTR).
My frustrations are aired in the hopes that my message will be heard. That message being clear, and concise communications, especially when it comes to billing aspects, and plans is of UTMOST importance.
Legacy users are who SOFTR should work closer with to figure out what to charge, and how to charge it. Rather than rolling it out and asking questions later (like here in a forum).
Paying for software is not the issue, the issue is clearly understanding what you are paying for, and being given an opportunity to take advantage of new features, without consequences like losing capacities or features due to being on a Legacy plan.
Lastly, Ask AI and the AI integration in general works awesome, but if you (SOFTR) are going to charge in “credits” for the use of it, you MUST clearly define what a “credit” is valued at, and what it “costs” in said value to use it. You cannot expect users to “purchase” credits, without defining the value outright, before anything is built. If, due to the nature of how SOFTR must pay for usage of AI engines, you cannot define “credit” value, then charge for the feature in a different way.
I thank you guys for the response, and hope that my forthright comments and opinions do not cause any ill will. I want to see SOFTR succeed, and want to use SOFTR for my business success as well.
@Lockdown155, I couldn’t have said it better myself.
@Jjenglert, it’s not necessarily Softr’s fault how external integrations implement their APIs, but its definitely not on builders either, especially your legacy Softr clients.
@Mariam, when builders upgrade, paying significantly more for increased features and limits, they don’t expect to be forced to then upgrade for new features and lower limits on new corresponding plans. Softr always grandfathered new features and limits into legacy plans and it wasn’t until enough particular users complained about Softr not doing this with their new databases, AI, and Workflows, in the community, that you walked it back.
It’s fitting that you redirected to this post from your AI announcement, since it’s a reminder about the way Softr operates. For context, it lays out Softr’s approach to addressing issues and integration conflicts with its own features overtime. So as a loyal Softr builder since 2020, and a Business plan customer, my ask is that we can be clear and honest about our concerns with Softr in the community. That way Softr is aware of their clients’ needs and makes decisions based on them. Otherwise, as @Lockdown155 insightfully pointed out, they will churn like many have already done since I started.