Watched Softrâs Database webinar. Great to gain insight into the products roadmap. Very excited to see how things develop. As an Agency new to Softrâs platform, itâs important for us to have clarity so we can confidently recommend and build in Softr, on behalf of our clients. A few questions I have areâŚ
Is the ability to link records across databases within a workspace on the roadmap - similar to SmartSuite? This would enable Softr customers to better utilize the 1,000,000 records per Workspace. Apart from building multiple apps in one workspace Iâm not sure how we would ever utilize all 1,000,000 records. Weâd be limited to the 200,000 records per database per app. Why not provide 1,000,000 records total per Workspace across all apps within that workspace?
What is the pricing for apps that reach the 200,000 record limit. Do we have have to upgrade to an Enterprise plan, which I understand is much more expensive than the Business plan and comes with other features that may not be required. There needs to be a clear upgrade path so people can invest confidently.
Will Databases support specific fields like Addresses - similar to how SmartSuite does?
Is the ability to specify field character limits and mark a field as required on the roadmap?
It would also be nice to get clarity on Database limits - How many fields are allowed per table? How many tables are allowed per database?
Thanks in advance for any insight you can provide. Iâm hoping to implement Softr and Databases for a large project, but I am treading cautiously, as itâs my reputation on the line for recommending Softr to my clients.
Appreciate it @jimba, especially since you are a relatively new Softr user. To be honest, it is hard to be a âtrueâ fan for the reasons you mentioned. There have been countless other reasons that I wonât mention here. But, I am compelled to remind Softr how they used to treat their loyal customers:
Hi @TobyMacLeod thanks for tuning in! Iâll do what I can to answer your questions, and then will direct your post to some others that could fill in the rest.
We plan to allow linked records across databases but donât have a timeframe on it yet.
Youâll have to upgrade to enterprise to go above the 200k limit per database. Our enterprise pricing is totally custom, and is very fair. Donât be afraid to reach out to get a price quote so you can see the specifics.
At the moment, there is no cap on the amount of fields required. If we run into problems in the future with this, we may implement.
Thatâs good news @stenkate. My specific question was if the sync would apply to dynamic legacy blocks as well. The new ones are nice, but lack the styling options that older blocks have.
My asumption is that the sync is a backend database integration which syncs to Softrâs internal (for us invisible) database, so it will apply to all blocks.
Thatâs right, but the devil is in the details. For instance, when Softr announced their plans for an in house database, they forgot to mention it wouldnât be included in legacy plans
Thank you to everyone who joined yesterdayâs event. Your energy and questions were fantastic! We couldnât tackle them all live, so weâve grouped the most common ones below and added answers. Hope this clears things up - let us know if you have any other questions.
Question: When will a public API be available and how will integrations with tools like Zapier, Make, REST endpoints, Power BI, and other platforms work? Answer: Weâre aiming to release our public API within the next 4 weeks. Once itâs live, youâll be able to connect any platform that uses a REST API to Softr Databases. Weâll follow up in the weeks after launch with official integrations into automation platforms - for example, a Zapier trigger for âNew Row Addedâ in Softr Databases.
Question: Will Softr Databases support enterprise-grade security such as MFA, SSO, and granular permissions at all tiers? Answer: We already supports MFA (business tier) and SSO (enterprise tier). Additional permissions will be added to Softr Databases over time.
Question: Which existing blocks and UI features (e.g., Kanban, formulas, totals, copy-paste) will be compatible with Softr Databases, and when? Answer: All of our new blocks - List, Table, Details, Calendar, Charts, and more - already support Softr Databases. Some older blocks, such as Inbox and Kanban, donât yet. A new Kanban block will be released soon and will work with Softr Databases. Weâll continue updating the remaining blocks to ensure full compatibility.
Question: How will Softr Databases connect with or replace sources like Airtable, Google Sheets, and SmartSuite, and how easy is migration/synchronization? Answer: Our goal is to make migration as easy as possible. Today you can import data via CSV upload. In the next 2â4 weeks, we plan to launch one-click import from Airtable, bringing over all your data, formulas, linked records, and more. After that, weâll add import options for other platforms (smartsuite, etc). Note that imports are one-off, not continuous syncs; if you need real-time sync, connect Softr directly to your preferred data source. Otherwise, you can import into Softr Databases and run your app from there.
Question: What are the record, storage, and pricing limits for scaling to hundreds of thousands or millions of records? Answer: Current limits are listed on our pricing page (Plans and pricing - Softr). For larger needs, please contact our support team. Softr Databases is built for performance and scale - it can handle tens or even hundreds of millions of records, and weâll work with you to craft an appropriate plan.
Question: When will native workflows/automations (e.g., scripts, email actions) be available, and what will they support? Answer: Native workflows will arrive with our Workflows product in the next 2â3 months (or sooner). Workflows is a standalone product that integrates deeply with both Softr Interfaces and Softr Databases. Using all three together provides a full-stack experience with flexibility, speed, and performance. While Databases itself wonât include scripting, Workflows will offer hundreds of actions - sending emails, posting Slack messages, filtering, looping, and more.
Question: How can we connect Softr Databases to analytics tools (e.g., Power BI) and create totals or filtered views for reporting? Answer: This will be possible via our public API with Softr Databases. Using this, you can bring your data into Softr, to create these views or totals.
Question: Will there be a simple way to export or download Softr Databases for backups and disaster-recovery purposes? Answer: Yes. Version history and CSV export are on the roadmap for the coming weeks and months as the product matures. Our immediate focus is getting your data into Softr and giving you a great experience; next, weâll add the options you need to use Softr Databases as your primary data source, including full data export.
Question: Will Softr Databases support automatic record linking and relational features similar to Airtableâs linked records? Answer: Yes! Softr databases already supports linked records, lookup fields, rollups, and many other field types.
Question: Will Softr Databases only work with Softr? Answer: No. Softr Databases can also be used as a standalone data source. Once the public API is available, youâll be able to connect it to any app, automation, or agent you need.
Question: What about the other data sources you support (Airtable, HubSpot, Notion, etc.)? Will they continue to work well? Answer: Absolutely. Weâre actively investing in these connections through our new Data Synchronizer, which keeps a secure, cached copy of your external data on Softrâs servers. This upgrade delivers:
Faster load times â the cache eliminates most round-trips to slower or rate-limited APIs, so views and filters feel instant.
Improved reliability â if an external API hiccups, your Softr app keeps running against the cached data until the connection is restored.
Standardized data â Softr can now apply consistent formatting across all sources (currencies, dates, numbers, and more), plus refresh that data in the background so your app stays up-to-date without needing a page reload.
In short, every data source you already rely on will continue to work - only faster and more robustly - while Softr Databases gives you an additional, high-performance option whenever you need native speed or massive scale.
To those who got this far, thanks for reading and we hope this was helpful!
See what I mean? The in-house database does not apply to all dynamic blocks. In my experience and from the fact that Softr wants new feature adoptions, old ones do not get updated, let alone supported. So I wouldnât expect in-house database and legacy dynamic block integration anytime soon.
Can you advise if you are going to offer âadd onsâ for more data. For example one of the restrictions I find with Airtable is the max number of records for a growing business is quickly reached. While your new softr database limits are higher, they still have quite tight restrictions, IMHO. So, for example, while the Business column has 200,000 records limit per database (I am not sure if that means per table or for all the tables in ine database) but will there be the abilility to add on, say further 100,000 records, for an extra $ XXX per month? If not, this is something that needs addressing I feel. I have quickly outgrown airtable and currently deciding whether to use softr database. I would like to but need to futureproof it. Thanks.
Also, are workflows still on target for next month ? Data is limited without this.
And thanks for the Q&A, really appreciate you taking the time to answer the questions. A lot of other No code companies could differently learn something here. You/Softr are extremely good at informing your customers what next on the roadmap etc.
I have multiple times experienced other no code solutions, not willing to let the customers know about the roadmap. You guys have a different approach on that, thank you for that.
Yes, weâd like to build native triggers in Zapier and Make. Donât have a specific timeline for that though. The public API for Softr Database will be coming first.
From my experience so far, creating linked records when building a database from scratch is easy and works. However, if you import records using CSV to populate database tables and then want to establish linked record relationships using existing data you run into a problem. When you change a field type to a linked record field (linking it to another table) you lose all of the data in the field.
Am I missing something? Is this a capability that needs to be added?
Iâm checking with my team to make sure, but I believe you have it right. For a more indepth import that keeps your relationships between records, thatâs where our 1-click with airtable import comes in⌠Hoping to have that ready within a couple weeks time (if not sooner)
We have some areas that weâre working on to improve with CSV import so the relations will stay in tact, but until then, the experience youâre having is expected at the moment.
+1 would love if there was a way to keep relationships.
I would love the following âtemporary solutionâ, that would make it slightly easier for us.
Right now in Softr, the linked recordâs actual data contains e.g [{"id":"record id","label":"Primary field"}], which results in the blobs.
When imported from airtable, the show the primary key in plain text compared to how you store it. So, if we would then change the type of the imported field to a linked record, whatever is inside would default to blank. A fix would be to instead check if the imported data (seperated by comma) equals to the first field of the table you are trying to link it to (which should be the primary key). If so, then link those records. The time complexity of the search might be large though Anyways, hope that makes sense. Thanks.
Anyways, hope that makes sense. Thanks.