Softr

Accepts natural language descriptions of app requirements and uses OpenAI (GPT, o3) or Anthropic (Claude) models to generate initial app structure, including page layouts, form fields, database schema mappings, and UI block configurations. The AI operates on a metered credit system (5 free credits on Free tier, 10-100/month on paid tiers) with unclear token-to-credit conversion, generating scaffold code that users can then refine visually. Implementation uses prompt engineering to inject data source schemas and block library definitions into the model context, producing JSON-serialized app definitions that the visual builder can render.

Provides a WYSIWYG editor where users assemble applications by dragging pre-built UI blocks (forms, tables, charts, buttons, etc.) onto canvas pages. Each block is configured via property panels to bind to data sources, set conditional logic, and define user interactions. The builder compiles block configurations into web application code (HTML/CSS/JavaScript) that runs in Softr's SaaS runtime. Block library scope is undocumented, but likely includes CRUD operations, dashboards, and workflow triggers. No custom code injection or CSS overrides are mentioned, constraining design flexibility to pre-built block capabilities.

Allows connecting to any HTTP-accessible backend via REST API without pre-built integrations. Users configure API endpoints, authentication (API keys, OAuth), request/response mapping, and data transformation. API calls are triggered by form submissions, workflows, or data binding. Implementation uses HTTP client library to make requests from Softr's backend, with response parsing and error handling. Automatic schema discovery is not available for REST APIs (unlike Airtable/Sheets); users must manually configure field mappings.

Allows building dashboards with charts, tables, and metrics to visualize data from connected sources. Chart types, real-time updates, drill-down capabilities, and customization options are mentioned as use cases but not detailed. Implementation likely uses a charting library (Chart.js, D3.js, or similar) to render visualizations from query results. Dashboards are built using the same drag-drop visual builder as other pages. Real-time data updates and refresh frequency are undocumented.

Allows admins to create user groups and assign users to groups, then configure which pages each group can access. Default groups are provided (Free/Basic tiers), and custom groups can be created (3 on Professional, unlimited on Business). Page visibility is controlled via group membership—pages can be hidden from specific groups. Implementation uses group membership checks at page render time to enforce access control. Fine-grained field-level permissions are not supported; access control is page-level only.

Allows collecting payments from app users via integrated payment processors (Stripe, PayPal, etc. — specific processors not documented). Payment forms can be embedded in apps, and payment data is processed through Softr's payment gateway. Payment success/failure triggers workflows (email confirmation, record creation, etc.). Pricing, payment method support, and transaction fees are undocumented. Implementation likely uses Stripe or similar payment API under the hood.

Publishes built apps to Softr's SaaS infrastructure and makes them accessible via public URLs. Apps are hosted on Softr's servers (region/CDN details undocumented) and served over HTTPS. Uptime SLA is only documented for Enterprise tier. Apps can be accessed via Softr's default subdomain (free) or custom domain (paid tiers). Implementation uses Softr's web server and application runtime to serve published apps. Deployment is automatic upon publishing; no manual deployment steps are required.

Connects to external data sources (Airtable, Notion, Google Sheets, HubSpot, monday.com, ClickUp, Coda, Supabase, MySQL, PostgreSQL, REST APIs) and exposes CRUD operations (create, read, update, delete records) through the visual builder. Data stays in source systems; Softr acts as a middleware presentation layer. Integration is configured via connection dialogs (API keys, database credentials) and data operations are bound to UI blocks at configuration time. Real-time sync frequency, transaction support, and batch operation capabilities are undocumented. REST API integration allows connection to any external tool via HTTP, but requires manual endpoint configuration.

Implements user authentication via email/password or SSO (SAML, OpenID on Enterprise tier) and enforces access control through user groups with role-based permissions. Users are assigned to groups (default groups on Free/Basic, up to 3 custom groups on Professional, unlimited on Business), and each group has permissions to view/edit specific app pages or data. Authentication state is managed via session tokens; logout clears access. Enterprise tier adds IP blocking and audit logging (coming soon). Implementation uses standard session-based authentication; OAuth and JWT details are undocumented.

Allows form builders to define conditional rules that show/hide form fields, change field types, or trigger actions based on user input or data values. Conditions are configured via visual rule builders (if-then logic) without requiring code. Implementation uses client-side evaluation of conditions against form state, enabling instant feedback as users interact with forms. Validation rules, multi-step forms, and file upload support are mentioned but not detailed. Conditional logic scope is limited to form-level operations; workflow-level conditions are handled separately via Softr Workflows.

Provides workflow automation triggered by form submissions, data changes, or scheduled events. Workflows execute a sequence of actions (send email, create record, update field, call webhook, etc.) without requiring code. Actions are metered: 500 on Free tier, 2,500 on Basic, 10,000 on Professional, 25,000 on Business. Metering definition is opaque—unclear if 1 action = 1 trigger, 1 step, or 1 condition. Implementation uses event-driven architecture where triggers (form submission, record update) invoke action sequences. Workflow state and error handling are undocumented.

Provides a proprietary database for storing application data with record limits: 5,000 on Free, 50,000 on Basic, 500,000 on Professional, 1M on Business. Schema flexibility, query language, indexing, backup/recovery, and transaction support are undocumented. Database is accessed through the visual builder (no SQL interface mentioned), and data can be read/written via forms and workflows. Unclear if Softr Database is the default storage or optional alongside external data sources.

Allows building multi-page applications where each page contains different blocks and content. Pages are connected via navigation menus, buttons, or conditional logic. Routing is handled by Softr's runtime (URL structure undocumented). Page-level access control is enforced via user groups—specific pages can be hidden from certain user roles. Page state and data passing between pages are undocumented. Implementation uses client-side routing (likely) to avoid full page reloads.

Captures form submissions and stores responses in Softr Database or connected data sources. Responses are unlimited on all tiers (Free, Basic, Professional, Business), making forms suitable for high-volume data collection. Submissions trigger workflows (email notifications, record creation, webhooks). Form response data is accessible via tables or reports (dashboards). Submission validation, file uploads, and multi-step forms are mentioned but not detailed. Implementation uses server-side form processing with validation before persistence.

Allows published apps to be accessed via custom domains (e.g., myapp.company.com) instead of Softr's default subdomain. HTTPS is provided automatically (likely via Let's Encrypt or similar). Custom domains are available on all paid tiers (Basic, Professional, Business, Enterprise) but not on Free tier. DNS configuration is required (CNAME or A record pointing to Softr's infrastructure). Implementation uses reverse proxy or CDN to route custom domain traffic to Softr's app runtime.