Softr Review (Verified October 2026)

Softr is a strong choice for a client portal or internal tool when your data and access rules fit its plans. Budget $119/month for Pro if you need custom roles, or $99/month with annual billing; the $25 monthly Basic plan suits a much smaller app. This Softr review evaluates public product pages, documentation, and prices verified on October 4, 2026.

Softr Review: What You Are Buying

Softr is a web app builder that puts a configurable interface over business records, with logins, permissions, and automation in the same platform. You connect an existing source, such as Airtable or Google Sheets, or store the records in Softr Databases, its own database product. Then you assemble lists, tables, forms, and detail pages around the actions people need to take. Its AI tools help construct or extend that system; the visual editor lets you change it afterward. For an operator, the useful purchase is a controlled place where clients or staff can work with your data without using the underlying database editor. Softr’s public product page

Review basis: Public product pages, help documentation, and the live pricing page, including both billing settings and the expanded comparison. The workflows below are proposed configurations and computed budgets. They are not reports of a signed-in trial, a deployed client project, or measured performance.

Who Softr Fits, and Who Should Pick Something Else

Softr fits an operator whose work already has recognizable records, roles, and repeatable actions: clients checking project status, employees updating deals, or partners submitting a profile. Its appeal is that the app can follow the business process you already understand.

The decision turns on four criteria: source compatibility, access controls, user and record costs, and who will maintain the application. A builder that satisfies three but misses the fourth can become an expensive detour. For example, a low subscription price does little for a nontechnical owner who cannot maintain the logic the app requires.

These are different billing units and scopes, not equivalent app quotes. A Softr workspace subscription, a Bubble project plan, and Retool builder/user charges should be compared against the same intended workflow.

Pick Softr when a business owner can specify who should see each record and what they should be able to change. It is especially convincing for a service company that wants an app around existing operations rather than a new software product with unusual behavior.

Softr Alternatives: Three Reasons to Choose Another Builder

Bubble is the more relevant shortlist entry when you are building a custom product rather than a portal around existing records. Its platform combines AI generation and visual editing for web and mobile apps. Web-only Starter is $32 month to month or $29/month with annual billing. The tradeoff is that application activity consumes workload, Bubble’s measure of server work, and additional capacity or overages can change the bill. Choose it for the application you need to design; skip it when a controlled record interface is enough. Bubble’s platform and pricing documentation describe those choices.

Glide Classic deserves a comparison when your day revolves around spreadsheet records, forms, and operational updates. It provides a component-based interface, a data editor, and workflows. Its Business plan’s $199/month annual rate includes 30 users and 5,000 updates, with additional usage charges. Do not use the prices on Glide’s general pricing page for this comparison: that page currently sells GlideOS, a separate product with its own subscription. Evaluate the Classic product against the Classic pricing page.

Retool is the stronger candidate when the hard part is querying databases and APIs and someone can own that technical work. Its pricing page lists database/API connections, a query library, and staging and production environments on Team. That plan costs $10 per builder plus $5 per internal user per month with annual billing. It is not an external-client portal quote: external applications begin on Business. For an operator determined to work without a technical maintainer, that maintenance requirement is a reason to prefer Softr. Retool pricing and features

For the wider shortlist, use the best no-code app builder comparison. If your priority is generating a custom application with AI, the best AI app builders in 2026 covers that different buying decision.

Softr Examples: Three Workflows Worth Building

Softr is most useful when each screen removes a specific handoff: a client asking for an update, a salesperson requesting a record change, or a partner emailing a directory correction. These examples illustrate supported building pieces, not completed deployments.

Client Portal: Give Clients Their Records and Clear Actions

Softr makes sense for a client portal when clients need project information and a few permitted actions, while your staff needs a broader operational view. Start with the records clients repeatedly ask about, rather than copying your entire internal workspace into a portal.

For a small agency, that might mean Clients, Projects, and Requests. Link each project and request to its client. A client sees project status and submits a request; a manager sees the client’s workload; staff update the relevant operational records. Softr’s public portal page describes project and task views, document sharing, forms, dashboards, and resource hubs. Individual features and integrations still depend on the plan. Softr client portals

The underlying distinction is between seeing a page and seeing the right records on that page. A login establishes who someone is. Page and block visibility decide which screens or sections appear. Record restrictions decide which client’s projects appear inside those sections. None of those descriptions should be treated as a substitute for the others.

Softr documents server-side visibility checks and conditional record filtering. Its global data restrictions can restrict viewing across data-backed blocks, dropdown options, and inline filters. Global View restrictions are available on every plan, including Free. Global Create, Edit, and Delete restrictions require Business or above. Pro supplies custom groups and more advanced local permission controls, but that does not make every global write control a Pro feature. User groups and global data restrictions

Softr Airtable: Keep the Source of Truth Where It Belongs

Softr can provide the client-facing interface while Airtable remains the source your staff manages. If your records already live there, moving them just to create a portal adds work you may not need. If you are starting from scratch, Softr Databases gives you native tables, typed fields, and relationships; its documentation describes CSV and Airtable imports. Softr Databases overview

Softr’s source catalogue also includes Google Sheets, Notion, HubSpot, Salesforce, Microsoft Excel, monday.com, ClickUp, Coda, SmartSuite, Xano, Supabase, PostgreSQL, MySQL, SQL Server, MariaDB, BigQuery, and REST API connections. The source-selection documentation includes further options such as Snowflake, Zoho CRM, and Baserow. That catalogue is a list of supported connections, not a promise that every plan includes each one. Softr integrations and choosing a data source

The source can set the minimum plan before user count matters. The current pricing page highlights Airtable, Notion, and Google Sheets on Free and Basic. Supabase’s dedicated documentation requires Pro or higher. Native SQL connections and the REST API data source require Business or Enterprise; the billing documentation places Snowflake and BigQuery on Enterprise. Supabase, SQL, REST API, and plan documentation

Keep one operational rule: choose where records will be maintained, then build the interface around that decision. A directory copied into a second source without a clear owner becomes two places to correct every change.

1. 1

   Define ownership in the records

   Identify the field that links each project or request to its client. For a simple single-contact example, Softr’s documentation describes matching a record’s email field to the logged-in user’s email. Where several people share an account, design the relationship and membership rules before building the pages.

2. 2

   Connect a narrow client view

   Select the database and table in the block’s Source settings, map the fields the client needs, and apply the record rule. Use page and block visibility for the relevant audience. Do the same for related records and selectable options, not just the first list.

3. 3

   Configure each allowed change

   Decide whether the client can submit a request, edit an existing record, or only read it. Configure the relevant action’s permissions. If the requirement is a global rule governing create, edit, or delete across the app, budget for Business.

4. 4

   Check comments separately

   Global data restrictions do not apply to the Comments block. Use Settings > Comments to configure who can view or comment. Check the client experience and the staff experience with representative records before inviting the broader audience.

These are configuration instructions drawn from the permission documentation and Comments documentation, not steps exercised in a signed-in account for this review.

Plan judgment: Pro is the practical starting point for a branded portal with separate Clients, Managers, and Staff groups if its source, record counts, and local action controls fit. Business becomes necessary when the design requires global write restrictions or a Business-only data source. A small read-only portal can use a lower plan if its simpler roles and counts fit.

Internal CRM: Make Record Updates and Follow-ups Consistent

Softr fits an internal CRM when the main job is managing contacts, companies, deals, and a shared follow-up process. Its public CRM page describes lead capture, contact and transaction records, comments, contracts and invoice status, feedback, and reporting. It gives you building pieces for that workflow; you still decide what the process is. Softr CRM builder

Consider a service firm with Sales, Finance, and Managers. Sales needs contact details, deal stage, owner, and the next action. Finance needs the relevant invoice status. Managers need the overall pipeline. Those are proposed roles, not evidence that a template automatically delivers your company’s policy.

Use a table for the records and detail pages for context. Make the next action visible alongside the deal rather than forcing staff to reconstruct it from messages. Restrict the page, block, record, and action access according to the job each group must perform.

For predictable follow-ups, use a workflow: when an agreed deal-status change occurs, notify the responsible person and update the appropriate record. Softr Workflows supports record-change and app-action triggers, conditions, branches, loops, and scheduling, with connections to tools including Gmail and Slack. Those capabilities are subject to each plan’s action allowance and integration availability. Softr Workflows

The operational advantage is consistency. Everyone sees the same definition of a deal stage and the same place to record the next action. Adding AI before establishing that structure can produce polished summaries of inconsistent records.

Illustrative monthly budget: For 12 business-domain app users who are not builders, plus the two included builders, Pro costs $119 + (2 × $3) = $125/month. That assumes the three custom groups, data source, native record limits, and workflow allowance fit. It excludes AI add-ons, other software subscriptions, additional domains, and tax. Softr’s user billing rules

If those 12 employees sign in with personal Gmail addresses, Softr classifies them as Client users. Do not count people by job title and assume the same invoice: Softr uses the business email domain relationship to the workspace’s builders.

Where to skip it: If the difficult work is a complicated database query rather than defining the operating process, compare Retool with a technical owner involved. If you want a custom software product whose CRM is only one component, compare Bubble. Buying Softr does not remove the need to design either the business process or the data relationships.

Partner Directory: Separate Discovery From Publication

Softr is a convincing partner-directory choice when visitors need a searchable list and your staff needs a controlled application process. Its Partner Directory template supports public or gated listings, search and filters, partner submissions, listing management, and customer contact requests. It can also be embedded into an existing site. Softr Partner Directory template

An industry association might keep Partners, Applications, and Contact Requests. The public listing shows approved partners and the fields a prospective customer needs. An application goes into review. A partner’s login gives access to the appropriate profile information or change-request process. Staff keep internal assessment notes out of the public listing.

The distinction that matters is submission versus approval. A partner should not gain publication rights merely because they can submit a form. Define the review status and who can change it. The template page describes using a workflow to notify the team when a partner’s status becomes Requested, for example by email or Slack. That is a useful starting workflow, not proof that your approval policy is already complete.

Softr Templates: Use the Structure, Review the Assumptions

Softr’s directory template comes with a connected Softr Database and sample data. Replace the samples with your own records or connect the intended external source, then review user groups, permissions, and branding.

Treat the template as a proposed data structure and page layout. Check whether its statuses mean the same thing your staff means, whether public fields are truly public, and whether a returning partner should edit a listing directly or submit a reviewed change. Those are operating decisions a template cannot make for you.

Plan judgment: Basic can suit a small directory using default visitor/logged-in distinctions and counts within its allowance. Pro becomes the likely minimum when you need separate Partner and Reviewer groups, more client logins, or removal of Softr branding. Business is the minimum for global write restrictions or relevant Business-only sources. Public visitors are different from the authenticated app users in Softr’s pricing definition; count the partners who will log in, not just the number of partner listings.

Softr AI: Choose the Feature for the Job

Softr’s AI features operate at different levels: building the app, creating a custom interface block, answering questions about a block, enriching database fields, or taking actions across an app and connected services. Choosing the right level matters more than putting an assistant on every page.

AI Co-Builder: Draft the Application Structure

Softr’s AI Co-Builder can create database tables and relationships, sample data, pages, native blocks, action buttons, role-based visibility, and a starting theme. Its documented entry point is Create new app > Generate with AI. The resulting pieces remain editable in the visual editor. AI Co-Builder documentation

For the agency portal above, a useful proposed prompt would describe the users and allowed actions: clients view their own projects and submit requests; managers oversee accounts; staff update operational status. That gives the builder the operating rules behind the screens.

The output still needs review. Softr explicitly says conditional branching in multistep forms must be configured manually in the Logic tab, and complex multistep automations may need manual adjustments. It also identifies system pages that cannot have custom blocks added through AI. Those are concrete reasons to leave time for configuration, without inventing a failure rate or a promised launch time.

Vibe Coding: Extend One Interface Block

Softr’s Vibe Coding Block creates custom static or data-connected interfaces from prompts. You can connect its data in Source, configure generated actions in Actions, and control who sees it through Visibility. Version history and direct code editing provide ways to revise the block. Vibe Coding documentation

An illustrative use is a partner-progress view that the standard layout does not express well. Generate that view, connect it to the intended table, and review its permitted actions. A custom-looking button is still an action with permissions to configure.

Do not confuse this feature with the pricing line for manual custom-code additions. Softr’s Vibe Coding documentation says its credit allowance is available on every plan, including Free; the current pricing page places custom code on Pro. They describe different paths for extending the interface.

Ask AI: Answer Questions About the Visible Block

Softr’s Ask AI reads the live records a user is permitted to see within a supported dynamic block. The documented setup is Actions > Add Topbar > Ask AI, followed by configuring instructions, suggested prompts, and appearance. It is available on all plans and consumes AI credits. Ask AI documentation

For a manager’s deal table, a proposed question is which visible deals need follow-up. For a client’s filtered project list, it is which visible items need attention. The access filter defines the records the assistant can analyze.

There are two hard scope limits: Ask AI is block-level, and it does not support blocks connected to a REST API data source. Static blocks are also unsupported. Paying for Business to connect an API does not make Ask AI work on that source. An app-wide App agent is a different feature with different configuration, not an app-wide mode of Ask AI.

Database AI Agents: Enrich Fields in Native Tables

Softr’s Database AI Agents fill supported text-like fields in Softr Databases. They can summarize, tag, extract information from PDFs, and enrich records using web search. You choose manual or record-change triggers and can add Only run if conditions. Preview shows an output and estimates the credit cost of that run. Database AI Agents documentation

For partner applications, an illustrative use is extracting a short service description from the submitted material and leaving it for staff to review. Run it when an application is ready for review rather than every time any field changes. That reduces unnecessary processing without assuming a fixed credit saving.

This is native database field enrichment. The documentation says agents cannot write to system fields such as IDs and timestamps, or calculated Formula and Rollup fields. If you want a reliable derived value, decide whether it belongs in an explicit calculation rather than generated text.

Softr Agents and Workflow AI: Conversation or Repeatable Automation

Softr Agents are separate from those database-field agents. An App agent talks to users in selected apps; a Schedule agent runs unattended. Agents can use uploaded files or links as knowledge and configured tools to read or write records, send messages, or call connected services. Softr Agents documentation

An App agent’s access to the connected app follows the chatting user’s interface permissions. A table with no exposed block is outside that app-derived access. A form constrains the fields it can create. Separately connected third-party tools have their own authentication and tool permissions, which you must configure.

For a client portal, begin with answering questions about the client’s projects and the allowed request process. Add write actions only when the intended behavior is clear. Softr provides confirmation settings for interactive tools; Schedule agents have no live user and do not offer that confirmation option. A scheduled report and an interactive client approval are different operating situations.

For a predictable status-change notification, prefer a workflow whose steps you define. AI actions can summarize or categorize within that automation. Use an agent when the value comes from interpreting a request and choosing tools, then inspect its Runs information, which includes calls and credit usage.

Budget implication: AI features share the workspace’s monthly pool. Credit consumption depends on the model, task, input/output size, and relevant tool or knowledge activity. Fifty credits is not fifty questions or fifty enriched records. Included credits reset monthly without rollover; add-on credits roll over for one month. The live pricing page says add-ons are available even on Free. Running out pauses AI features, while manual no-code editing can continue. Softr pricing and AI credit documentation

Softr Pricing: Monthly Rates, Annual Rates, and the Plan That Fits

Softr’s $19 Basic, $99 Pro, and $329 Business prices are effective monthly rates with annual billing. On October 4, 2026, changing the live page to Monthly showed $25, $119, and $395. Annual base payments are $228, $1,188, and $3,948 respectively. Live Softr pricing

The records column below refers specifically to Softr Databases. It shows both the total across your workspace and the ceiling in one database. Do not apply those native storage allowances to an external Airtable base or Google Sheet.

These are the current base allowances in Softr’s pricing comparison. Enterprise does not publish fixed quantities for those fields; custom does not mean a promised unlimited allowance. Displayed prices exclude tax.

Free: Validate the Data and Access Model

Softr Free includes up to three builders, five combined app users, 5,000 native records across the workspace, and 1,000 per database. Its monthly allowances include five AI credits and 500 executed workflow actions.

Use it to determine whether the source, records, and screen structure fit the job. Its default audience groups are Visitors and Logged-in users. View restrictions being available on Free is useful, but it does not give you Pro’s custom group allowance. A premium signup trial and the ongoing Free plan are different offers; Softr says the Free plan is free forever.

Basic: A Small App With Simple Audience Rules

Softr Basic costs $25/month or $19/month on annual billing. It includes one builder, five Team users, five Client users, 50,000 workspace records, 10,000 per database, ten AI credits, and 2,500 workflow actions per month.

Basic adds a custom domain, conditional form logic, and automated database backups. It keeps the default visitor/logged-in group model, and there is no app-user add-on. It can fit a lightweight internal tool or a small directory with simple permissions. It is a poor starting assumption for a portal whose specification already names several custom roles.

Pro: The Likely Starting Plan for an Operational Portal

Softr Pro costs $119/month or $99/month with annual billing. It includes two builders, ten Team users, 50 Client users, 500,000 workspace records, 50,000 per database, 50 AI credits, and 10,000 workflow actions per month.

Pro adds three custom user groups, advanced permissions and actions, comments, removal of Softr branding, email one-time-code and Google sign-in options, and custom code/API capabilities. The three-group allowance makes it a plausible fit for Clients, Managers, and Staff, provided the rest of the design fits.

Additional Team users cost $3 each per month, up to 50 Team users total. Additional Client users cost $1 each per month, up to 250 Client users total. Those are separate categories; spare Client capacity does not replace Team capacity. Softr’s plan and user documentation

Business: Buy the Source or Control You Need

Softr Business costs $395/month or $329/month with annual billing. It includes three builders, 30 Team users, 100 Client users, 1,000,000 workspace records, 200,000 per database, 100 AI credits, and 25,000 workflow actions per month.

Business adds ten custom groups, filtered user syncing, two-factor authentication, domain-restricted signup, and the relevant global write restrictions. It also lists an installable progressive web app, or PWA, a web app people can add to their device, plus push notifications and priority support/onboarding. Native SQL and REST API data-source access also make this the minimum plan for some small applications.

Additional Team users cost $5 each per month, up to 100 Team users total. Additional Client users cost $2 each per month, up to 500 Client users total. User volume alone is not the decision rule: a small SQL-backed application can require Business while a larger portal on an eligible source can still fit Pro. Plan documentation

Enterprise: Get a Quote for the Required Specification

Softr Enterprise is priced on request, with custom record, user, and AI-credit limits. Its published offering includes SSO through SAML/OpenID, SCIM user provisioning, audit logs, custom agreements and service-level agreements, advanced governance, and a customer success manager. The billing documentation also places Snowflake and BigQuery here.

If one of those is a requirement, request a quote for the actual source, user categories, and controls. Do not assume the Business base price plus an invented enterprise surcharge.

Work Out the Bill With Users, Builders, and Actions

Softr counts unique app-user email addresses across published apps once. Deactivated users do not count. Builders can also use apps without consuming the app-user allowance. Team users share a business email domain with a workspace builder; free-email domains such as Gmail count as Client users.

That classification can change a budget before the number of people changes. Extra users on Pro and Business are billed monthly even when the base plan is annual. Softr checks counts daily and documents a seven-day grace period before the initial excess-user charge. Free and Basic cannot buy additional app-user capacity. User accounting and billing

An agency with 20 Client users and five nonbuilder Team users fits Pro’s included user allowances. At the monthly base rate, $119 ÷ 20 = $5.95 per client per month. That is a normalized portal cost for this illustrative configuration, not Softr’s per-client list price. It assumes the other requirements fit and excludes extras.

At 100 Client users and 12 nonbuilder Team users, the same Pro workspace needs 50 extra Client users and two extra Team users. The calculation is $119 + (50 × $1) + (2 × $3) = $175/month. With an annual base subscription, the monthly equivalent becomes $99 + $56 = $155, or $1,860 over a year if those counts remain constant. The extra-user portion is still charged monthly. Documented user rates

An extra builder also changes the bill: Basic charges $6/month, Pro $12/month, and Business $24/month on monthly billing; the corresponding annual-billing rates are $5, $10, and $20. Paid plans include one custom domain; additional domains cost $15/month or $13/month with annual billing. Keep any external database subscription and AI add-on outside the base quote.

Workflow capacity counts executed actions, not simply completed business events. Triggers and flow controls do not consume that allowance. If a hypothetical workflow executes three chargeable actions for each of 900 events, it uses 2,700 actions, exceeding Basic’s 2,500 allowance. The live pricing FAQ says workflows pause at the limit until it renews or you upgrade. Softr pricing

What Softr Announced in August 2026

Softr’s official August 5, 2026 announcement introduced separate Team and Client user categories and usage-based expansion, including automatic extra-user billing after a seven-day grace period. It said existing paying customers and customers on the stated trial could retain their current plans; Mariam also clarified that monthly legacy subscribers would continue paying for their legacy plans. Free workspaces could remain Free, with a window to subscribe to legacy pricing ending at midnight Eastern on August 20. Softr’s own announcement

For a new buyer, use the current plan table above. For an existing subscriber, compare the actual workspace subscription before changing it. The announcement does not make every historical user allowance part of the new plans.

The Softr Limitations That Can Change the Purchase

Softr’s main purchasing limits are specific enough to check before building. The most consequential ones concern permission scope, data connections, and the way usage is counted.

Basic cannot represent several custom app roles. It has Visitors and Logged-in users; custom groups start on Pro, with three included. If your design distinguishes Clients, Staff, and Managers, the Basic price is not the relevant starting budget. This is a feature gate even for a small audience.

Native records have two ceilings. Workspace capacity and capacity in one Softr Database are separate. A large workspace number can conceal the database-level upgrade trigger. Model the number of records in the database you intend to use, rather than adding all databases together and stopping there.

An API action and an API-backed data source are different purchases. Pro supports the Call API action; the REST API data source requires Business or Enterprise. The REST source also cannot supply the application’s Users, and Ask AI does not support it. This combination matters for a portal on a custom backend: the connector, login source, and conversational feature cannot be treated as one checkbox. Call API action, REST data source, and Ask AI

Global restrictions do not cover Comments. Softr states that exception explicitly. Comments are stored in the app and have their own view/comment settings. If your portal mixes internal notes with client communication, configure those controls separately; a global record rule is not evidence that the discussion is restricted correctly. Global restrictions and Comments controls

AI generation leaves some operating logic to you. Conditional multistep form branching needs manual configuration, and complex workflows may need adjustment. Use the generated structure as a starting point, then check the path a real request takes from submission to completion. Co-Builder limitations

Exhausting an allowance changes behavior. Workflow exhaustion pauses workflows; AI-credit exhaustion pauses AI features. They are different counters, and neither is simply the number of business outcomes completed. Put an owner on monitoring both before making automated follow-ups essential to your operation.

Connected data keeps its own constraints. Softr’s source-selection docs explain that external systems have rate limits and that more dynamic blocks, users, and actions create more demand on the connection. They also describe requests passing through Softr’s servers, stored connection credentials, and caching. Keeping Airtable as the source does not mean information never passes through Softr. Budget and design for the external source as well as the app. Its source-comparison estimates are not published plan caps or measured guarantees for your application. Choosing a data source

Verdict: Start With the Access Model, Then Buy the Plan

Softr is worth shortlisting when the application is a portal or internal operating tool around structured data and someone inside the business can own its rules. Pro is the likely starting point for a branded app with custom roles; Basic can be enough for a smaller, simpler configuration. Business earns its higher cost when it supplies a required source, global write control, or native database capacity.

The decision rule is explicit: choose the lowest plan that supports your source and access model, then verify both user categories and both native record ceilings. If default roles suffice and Basic’s counts fit, use Basic. If custom roles are required and Pro’s gates and allowances fit, use Pro. If SQL, a REST data source, global write restrictions, or the larger single-database allowance is necessary, price Business. If enterprise identity, governance, or custom capacity is required, get the Enterprise specification and quote.

Choose another builder when the app’s unusual product behavior is the central challenge, or when technical database work dominates the project. Bubble and Retool serve those respective buying situations; Glide Classic is worth comparing for spreadsheet-centered operations.

The Monday move: Build one representative workflow during the available evaluation period, using the intended data source. Check the client and staff views, related record selectors, comments, and permitted changes. Count nonbuilder Team and Client users separately, count records in each native database and across the workspace, then model the action and AI allowances. Consider annual billing only after that configuration fits. Pro’s annual base saves $240 over twelve monthly base payments, but that saving cannot correct a wrong plan choice.

Softr FAQ

Which is better, Glide or Softr?

Softr is the stronger starting shortlist choice for a portal organized around client access and business records. Glide Classic is worth comparing for spreadsheet-driven operational apps built from interface components. Compare the workflow and usage rules, not just the appearance. GlideOS is a separate product and subscription, so its general pricing page should not be used as Classic pricing.

Can I use Softr for free?

Yes. Free includes five combined app users, 5,000 records across native Softr Databases with a 1,000-per-database ceiling, and five AI credits per month. It also includes up to three builders and 500 workflow actions per month. A free prototype still has to fit those limits and the plan’s audience controls. Current allowances

What is cheaper than Softr?

It depends on the Softr plan and the job. Bubble Web-only Starter at $32/month is below Softr Pro’s $119 monthly base, but above Basic’s $25. Bubble also meters workload and requires a paid plan for live launch. Retool Team’s per-builder and per-internal-user rates can produce a smaller internal-tool bill, but Team excludes external apps. Compare the total supported configuration, not the lowest headline. Bubble’s rates and Retool’s rates

What companies use Softr?

Softr publishes customer stories, including Massachusetts Institute of Technology (MIT) Project Manus. Its account describes a makerspace portal using Softr, Airtable, and the university’s single sign-on system. That is vendor-published customer evidence, not a test performed for this review, and it does not establish the capacity of today’s self-serve plans. MIT Project Manus customer story

Is Softr a legit company?

Softr has a public product, maintained help documentation, published subscription terms, and named customer stories. Those provide evidence of an operating software platform. Whether it is the right purchase for you depends on the required source, permissions, user categories, and allowances; a customer logo alone cannot answer that question.

What are the pros and cons of using Softr?

The advantages are connected business data, built-in app components, authentication, permission controls, native workflows, and editable AI-generated structure. The drawbacks are plan-dependent roles and sources, separate native record ceilings, limited Ask AI scope, the Comments exception to global restrictions, and usage allowances that can pause automation or AI. It is a good fit when those documented boundaries match the workflow.

How much does Softr cost?

Free is $0. Basic is $25/month or $19/month billed annually; Pro is $119 or $99; Business is $395 or $329. Enterprise is on request. Extra users, builders, domains, AI add-ons, an external data subscription, and taxes can change the total. These rates were verified on October 4, 2026. Softr pricing

Is Softr free forever?

Softr says its Free plan is free forever. That describes the ongoing limited plan, not permanent access to every premium feature from a signup trial. Free retains its user, record, AI-credit, and workflow allowances. Softr’s pricing FAQ

What are the key differences between Softr and Airtable?

In this workflow, Airtable can remain the database your staff manages, while Softr supplies the app interface clients or other users interact with. Softr also has its own native databases, so Airtable is optional. Keeping Airtable adds the source’s own subscription and connection constraints to the decision. The native Softr Database record allowances are not Airtable storage allowances. Softr’s source-selection guide

Get the AI Business Workflow Audit Checklist

Map the records, access rules, handoffs, and automation needs before committing to a builder.