Tl;tr:
- Scalability means how many users or how much data your system can handle before performance issues arise.
- No-code tools have limitations like server capacity and data handling, but proper setup can mitigate these issues.
- Many successful tools and various apps, show that no-code can handle large user bases.
- As your no-code app grows, you can integrate external databases or add code to extend scalability
- Initially using no-code helps validate your product. Once you have paying users, you can gradually rebuild parts in code to overcome limitations.
A year ago, I found myself in the same situation you might be in now. I had to decide whether to build our startup's product using no-code tools or go the more expensive route with full-code development.
And despite my extensive research, I couldn't find a definitive answer. But in the end we chose no-code and successfully scaled our product to hundreds of users.
Here, I want to share my honest opinion on why no-code is scalable and why, in the grand scheme of things, it doesn't really matter.
What does scalability mean?
Before we dive in, let's clarify what scalability means.
According to Wikipedia:
“Scalability is the property of a system to handle a growing amount of work. One definition for software systems specifies that this may be done by adding resources to the system." (Wikipedia).
I think that definition sums it up pretty well. In the context of no-code and product development, scalability often refers to "how many users can we accommodate before the system slows down?", "how much data can we process before hitting limits?", or "Can we build it now and forever on no-code?". These are crucial questions for many when it comes to building products with no-code.
Is no-code scalable?
So, is no-code scalable? If you ask me: yes, it is.
We already see numerous examples of no-code apps, such as marketplaces, platforms, and apps handling thousands of users.
However, this question keeps coming up, and it's true that scalability with no-code involves a few considerations:
Set the basics of your app right
Since no-code tools operate with code in the background and are hosted on shared servers, you only get a fraction of the server capacity. If you want more server capacity, you'll usually have to pay more.
But you can prevent this or at least delay it with the correct setup and structure of your database and workflows.
Infuse full-code to make your app scalable
Thanks to APIs and the ability to extend no-code apps with code, which many no-code builders offer, you can easily infuse code to make your app more scalable.
One popular solution is to use an external database in combination with your no-code tool. This could be a database like Xano or even a more complex one like an SQL database.
Choose the right tool for your use case
It always depends on your use case.
Navigating through the jungle of no-code tools, it's worth investing time to find the right tool for your needs. For example, Bubble.io is suitable for more complex tools with extensive workflows and API integrations, whereas Softr is ideal for simpler tools fueled by Gsheets, Excel, or Airtable as a database.
Choosing the right tool from the beginning can make or break your scalability.
Examples of scalable no-code solutions
While exploring the question of scalability some time ago, I discovered several impressive examples that demonstrate the scalability and complexity achievable with no-code tools:
Civilization VI on Webflow
One standout example is from Sarkis Buniatyan, who built Civilization VI entirely in Webflow. He used 12,400 elements, 1,800 styles, 1,200 assets, and 400 interactions, making it one of the largest Webflow projects ever published.
Aviation app with no-code
Another favorite example is Julián Valentín's aviation app, which simulates communication between an airport tower and pilots. The app is entirely built with Bubble.io and serves as a great example, even if it’s complex for those unfamiliar with flight communication (like me).
But it's not just the complexity that stands out in some apps; there are also noteworthy examples in terms of data handling:
Escape the City - job portal with no-code
This job platform app was also built with Bubble.io and handles 500k users, which means it’s also managing significant user and data loads with no-code.
Another post on the official Bubble.io forum mentions an app with 50.5 million records and 4.2 billion workflows, making it one of the largest no-code apps as of the end of 2021, although it doesn't provide a URL for reference.
At Naviu, we’ve also built several foundations for large-scale apps, like Training OS, which handled 300+ users right after launch.
Why scalability shouldn’t worry you
It's good that you're thinking about scalability, but it shouldn't be a major concern.
Here’s how we saw it when we decided to go with no-code:
Imagine you're building your product or MVP with no-code (read here how to build your MVP with no-code). You launch it, and people show interest. You onboard more and more users until you maybe reach some limitations of your no-code app.
At this point, you decide to extend it with code to improve performance. Now, you're in a great position: you have paying users, you know your product works, and you have achieved product-market fit.
You can now rebuild parts or all of your product in code, saving money since you don't need to plan from scratch. Plus, your paying users can help finance this transition.
In the end, this means you can take advantage of all the benefits of no-code until you have a proven product, and then easily rebuild it without a huge investment.
Final words
As you can see from these examples, no-code can indeed be scalable. The real question is about your use case and how you structure the underlying infrastructure and setup of your no-code product.
In the end, if you have a validated no-code product with paying users, you can gradually replace it to eliminate limitations. The benefits of no-code will and should outweigh the concerns about scalability.
Contributors
