Softr review

What is Softr?

Softr is a visual application builder aimed at business portals and internal tools. It brings together connected data, a built-in database, permissions, and workflows. Instead of starting with an empty codebase, you assemble screens from platform blocks and use AI assistance where it helps.

Its appeal is practical: give people a useful place to view information, submit something, or move a business process forward. We would start with the records and access rules the application needs, then decide which screens expose them. That approach plays to Softr’s strengths and makes it easier to judge whether the app fits the available building blocks.

What’s changed in 2026

Softr introduced Agents in August for in-app and scheduled business tasks. They can act within application permissions, which makes access design part of the automation decision. A helpful agent still needs the right boundaries around the information and actions it can use.

September added MCP access for building apps, databases, blocks, and workflows with compatible tools. Softr says this building route does not consume its AI credits. That is a useful distinction, but it does not make every connected tool or every operation free. Together, these additions expand Softr beyond assembling screens: the platform now offers more ways to build and carry out business work in the application itself.

What it’s like to use

Softr can feel approachable when the job matches a familiar business pattern. A client portal or internal CRM gives the blocks a clear purpose, and the editor helps turn that purpose into usable screens. Nontechnical teams can make meaningful progress without designing every component from scratch.

The easy first screen does not remove the need to understand the information behind it. Decide who should see a record, who can change it, and what should happen afterward. This is often more important than choosing a layout. It also helps to keep the first workflow narrow: demonstrate that a real person can complete the intended task before expanding the app. Support can be helpful, but the experience is uneven enough that critical decisions should not depend on an immediate answer to every technical question.

Where it falls short

Platform blocks provide structure, but they also shape what is convenient to build. An unusual interaction or deeply specialized process can demand more work than a standard portal. Advanced permissions and custom code are paid-tier features, so a requirement that looks small may affect the plan you need.

Reliability and troubleshooting deserve attention once customers depend on the app. Some builders find the workflow stable and productive; others struggle with interruptions, usage visibility, and delayed help. We would check how to recognize and recover from a failed business process before making it central to daily operations. A visual editor does not remove that responsibility. If direct source-code ownership is a priority, compare a different development model rather than assuming platform blocks provide an independent application codebase.

Pricing and credits in practice

Free supports five app users, three builders, 5,000 records, and 500 workflow actions per month. It includes five monthly AI credits. That is a useful small-app starting point, with real limits on the audience and automation.

Basic costs $25 per month, or $19 per month billed annually. Pro is $119 monthly or $99 per month billed annually. Business is $395 monthly or $329 per month billed annually. Check the official pricing page for the exact allowances and the requirements of your intended audience.

The subscription name alone does not describe the full fit. Builders, team users, client users, records, actions, and AI credits are distinct considerations. A portal can become more expensive as more people need access, even if its screens barely change. Map those needs before upgrading, and distinguish MCP building from the AI credit pool rather than assuming every AI action has the same billing treatment.

Who should use it (and who shouldn’t)

We would shortlist Softr for a small business that already knows the data and process it wants to expose through a portal. It is also useful for internal tools where a consistent set of blocks is an advantage and the team wants to maintain the app visually.

Compare Bubble for a broader visual workflow environment, WeWeb for deeper control and a source-export path, or Base44 for another AI-assisted business-app option. Teams whose requirements are mostly unusual interactions should examine the difficult features early. The right choice is the platform that makes the ongoing process manageable, not simply the one that creates the first screen fastest.

Bottom line

Softr is a sensible choice for portals and internal tools with clear data and access rules. Its blocks, workflows, and newer agents can reduce setup work, while the limits on users and automation make capacity planning essential. Choose it for a well-defined business process and leave time to verify permissions, reliability, and maintenance.