Beyond building blocks: Build everything your business runs on

Before Softr, building business software without code meant being handed a canvas.

The tools of that era were powerful. Bubble, Webflow and others gave you a blank page and full control: place every element, set every margin, wire every interaction, pixel by pixel. If you knew what you were doing, you could build almost anything.

But most people running a business didn’t know how, and didn’t want to learn. The interfaces were technical. A simple client portal meant hours of layout work before you even reached the parts that mattered. It was like being asked to make a birthday card in Photoshop.

We started Softr in 2020 with a different idea. We wanted to give a billion business users the power to build the tools they need, and we knew a canvas wouldn’t get them there. So we gave them Lego instead.

Lego, not a canvas

We built Softr on one observation. Roughly 80% of all business software is the same. On the surface, the same components appear again and again: tables, lists, forms, detail pages, charts, navigation. Underneath, every app needs the same foundations: a database, user logins, roles and permissions, business logic, hosting and security. A client portal, an intranet, a CRM and an inventory tracker look different, but they’re built from the same parts.

Those parts are also where the hard, risky work lives. Get a permission wrong and the wrong person sees payroll. Get authentication wrong and your client data is public.

So we did that work once, for everyone, and turned it into bricks. Instead of drawing a table pixel by pixel, you added a table block and pointed it at your data. Instead of writing access rules, you chose which user groups could see a page. Instead of setting up a database, a login system and a permissions model, you clicked a few times and had all three, connected and secure. The same abstraction applied all the way down, from the interface to the database, business logic, roles and permissions.

People started calling us the Canva for web apps. They compared Softr with Bubble and Webflow the way you’d compare Canva with Photoshop: not as powerful at the pixel level, but dramatically faster and simpler for what most people actually need. Teams built in an afternoon what used to take weeks, in a fraction of the time of any alternative.

And what they built didn't stay small. A tool for one team turned into the client portal every customer logs into, the ERP the whole company runs on, the partner portal vendors depend on, the intranet every employee opens in the morning. Today more than 1 million builders and tens of thousands of organizations, from small businesses to teams at Netflix, Google, Stripe and UPS, run real operations on Softr, with their employees, customers and partners relying on those apps every day.

When we ask customers what they love most about Softr, the answer often isn't a feature at all. It's something we hear in their own words, again and again: "What I love about Softr is that I can't break things."

That sentence is the whole point of Softr. When your operations are at stake, breaking things is not an option.

The last 20%

Lego came with a trade-off we always understood. Bricks get you 80% of the way quickly and safely. But a brick only comes in the shapes someone designed. The last 20%, where your process doesn’t quite fit a table or your clients need to see things a particular way, is where you felt the walls.

We knew that, so we added AI. The Vibe Coding block let you describe a custom component, such as a calculator, a bar-code scanner, an interactive screen no block could produce, and drop it into your app, connected to your data and governed by the same permissions as everything else. It was a custom-molded brick for the shape you couldn’t find in the box.

We kept the standard bricks as the default on purpose. They’re simpler, they’re harder to break, and since most software is built from the same components, we assumed AI would be the exception: something you reached for when you needed something more unique.

We were wrong about that, in two ways we didn’t see coming.

What we didn’t know

The first surprise was how people wanted to build. As models improved month after month, our users increasingly relied on Softr’s AI Builder rather than spending time clicking through individual settings, even simple ones. They wanted to describe what they needed and have AI build it for them, whether through Softr’s AI Builder or, once we launched MCP, directly from Claude, ChatGPT, and Cursor. Talking to software was no longer just a feature. It was becoming the way people expected to work.

The second surprise was what people would use AI for. We designed the Vibe Coding block for the rare unique screen. Instead, builders used it for almost everything, including the standard tables, forms and lists a block could already handle. App after app filled up with vibe-coded blocks.

At first, it slightly surprised us, but it also made sense. As LLMs became better at building frontends, describing what you wanted in a sentence became faster and easier than configuring it manually, even with just a handful of clicks. And the result wasn't just a rough approximation. AI could now generate exactly the table users had in mind, down to the last column, filter, and interaction.

Our users weren’t rejecting the 80%. They had found a faster way to build it, and they were getting the last 20% at the same time.

When we looked closely at those apps, we noticed something else. While generating screen after screen, builders never tried to vibe code their permissions. They didn’t reinvent authentication or rebuild the database. These were apps their teams and clients depended on, and they kept relying on Softr for everything that kept them running safely. They used AI for everything they could see.

Easy, safe, and now exact

For as long as people have built software without code, they’ve had to choose. The canvas gave you exactly what you wanted, if you had the skill and the time. Lego gave you speed and simplicity, within the shapes of the bricks.

Our bricks were solving two problems at once.

The first was making software easy to build. Blocks turned common components into something a business user could configure instead of draw. For a person working by hand, that was the best abstraction available, and it’s why we beat the canvas.

The second was making software safe to run your business on. Every brick sat on a foundation that enforces who can log in, who sees what, how data flows and where everything runs, so no choice a builder made could expose their data.

AI now solves the first problem better than bricks ever could. You don’t configure the familiar 80% piece by piece, and you don’t draw the unique 20% pixel by pixel. You describe what you need and you get it, all of it. Your app fits 100%.

The second problem is the one Softr has always solved, and it’s the one that must never be improvised. That’s the foundation, the trust layer: your data, authentication, roles and permissions, business logic, workflows, integrations, hosting and audit trail. It’s engineered once and enforced everywhere.

The choice between Photoshop and Canva is over. You get the precision of the canvas and the ease of something even simpler than Lego: a conversation.

Introducing new Softr

So we rebuilt how you build on Softr.

You describe the app you need, and Softr builds the complete system: the database, the user roles and permissions, the workflows and integrations, and a frontend that’s now completely custom. If your team needs a dispatch board that works like a map, or a client view that looks nothing like a table, you just ask for it. You don’t have to work out which block gets you closest anymore.

The part we were most careful about is everything your operations depend on: the business logic, database and security. AI doesn’t write it from scratch, but builds on top of Softr’s strong backend foundation. It runs on the same Softr infrastructure thousands of businesses already rely on every day. Everything that touches your data, business logic, access and permissions goes through that foundation, where your user groups and data restrictions are enforced, so no change to a screen can change who's allowed to see or edit what.

You still can’t break things in Softr. You just aren’t limited by it anymore. A bad prompt might make your app ugly, but Softr’s guardrails make it much harder to compromise its security or expose sensitive data.

The hard part starts after launch

Getting an app on screen is no longer the hard part. Every AI app builder can do that now. The hard part is what happens once your team, your clients and your partners start depending on it.

Vibe coding platforms generate the entire application, backend included. Every change becomes a code change. Your data lives in a PostgreSQL database, and your permissions are defined in code or SQL policies.

For a developer, that's normal. For a business user running operations on it, it's a non-starter:

• You can’t check it. If you can’t read the rules, you can’t confirm that a client only sees their own projects, or that a contractor can’t open payroll.
• You can’t change it yourself. Adding a role or tightening access means prompting the AI again and hoping it edits the right thing without breaking something else.
• You don’t notice what’s missing. When researchers scanned 1,645 vibe-coded apps, they found 170 with databases open to anyone. The access rules had never been set up, and the people who built those apps had no easy way to tell.

Softr was built the other way around. We vibe code your frontend. We don't vibe code your backend.

Your data, permissions, business logic and workflows aren't generated code. They run on Softr's secure, proven foundation, and you can see and manage every part of it visually. Your data sits in a database that works like a spreadsheet. Access is controlled through user groups and data restrictions you can open, read and change in a few clicks. Business logic and workflows are laid out step by step. Every rule is enforced on our servers, not in the interface, so the rules you set are the rules your app follows.

That changes what a change means. Redesigning a screen can't touch who sees what. Changing who sees what is a setting, not a code change you have to verify. Your teammates can understand the app without asking AI to explain it, and IT can see exactly what's running and who can access it.

AI builds your app. The foundation keeps it secure, and you stay in control of who can access what, how your business rules work, and how your app evolves as your business grows.

We've been building toward this all year

The Vibe Coding block showed that generated code could live safely inside a governed app. Agents brought AI into how your apps run. MCP let you build from the AI tools you already use while everything stayed inside Softr. Our work with IT leaders defined how business teams can own their apps while IT keeps control. Each step was a foundation for this launch.

If you already run on Softr, nothing breaks. Your apps keep working, and the standard way of building with blocks remains available if that's what you choose to work with.

Build everything. Break nothing.

Six years ago, we handed business users Lego instead of a canvas, so they could build the tools they need without touching the parts that could hurt them. The bricks got millions of people 80% of the way there, faster than anything else, and thousands of companies ended up running their operations on what they built.

With AI, nobody has to build brick by brick anymore. We're keeping the foundation that made Softr safe to run a business on, and giving you everything you can build on top of it.