Build secure applications with IT governance
Softr gives teams the security, access controls, and governance they need to build and run business apps with confidence.


Security as a default. Not an afterthought
Access to our Trust Center containing our SOC 2 Type II report, Security Policies and Penetration Testing results are available on request.
SOC Type II
99.9% Uptime
GDPR
Centralize governance
Control who can build, manage, and access sensitive data across your organization.
Workspaces & teams
Manage teams with dedicated workspaces and permissions.
Workspace roles
Control who can build, publish, manage settings, and access data.
Application audit logs
See who changed what and when across your applications.
Database audit logs
Track changes to tables, fields, and database structure.
Data security & protection
Protect your data, control who can access it, and manage authentication across your apps and workspace.
Data hosting & protection
Control where your data is hosted and how it’s protected across storage, transfer, and connected sources.
EU or US data residency
Host your data in the EU (Germany) or US.
Encryption in transit & at rest
Protect data both in transit with 256-bit TLS and at rest with encryption.
Protected files & credentials
Use temporary URLs for file access, while keeping integration credentials and API keys encrypted and off the frontend.
Proxied data queries
Query connected sources through Softr without copying the underlying data.
Authentication & access for your app users
Control what each user can see and do, down to the record level.
Sign-in options
Let users sign in with email and password, magic link, social login, or SSO.
Multi-factor authentication
Add another layer of verification with authenticator apps, SMS, or email.
Roles & permissions
Group users by role, team, or data, then control which pages, blocks, actions, and records they can access.
Data & network restrictions
Restrict which records users can access across the app, and limit app access by IP address.
Authentication & identity for your team
Connect Softr to your identity provider to centralize authentication and automate access across your workspace and apps.
Single sign-on (SSO)
Authenticate your team and app users through your identity provider with SAML 2.0 or OpenID Connect.
Identity provisioning
Automatically provision and deprovision users with SCIM.
Multi-factor authentication
Require an additional authentication factor for workspace access.
Workspace access controls
Control what workspace members can access and manage with roles.
Reliability
Built on AWS with high availability, redundancy, and 24/7 monitoring, Softr keeps the apps your business depends on running smoothly.
99.9% uptime
Redundant AWS infrastructure with 24/7 monitoring.
Automated backups
Regular backups and disaster recovery keep data recoverable.
Real-time status page
Live system health and incident updates you can subscribe to.
Scales with you
Handles growing users and data without performance drops.
Frequently asked questions
Is Softr SOC 2 compliant?
Softr is SOC 2 Type II compliant. A Type II report means an independent auditor tested the security controls over a period of time. A Type I report only confirms the controls existed on a single date.
Where does Softr store customer data?
Softr stores and hosts all user data in Europe, specifically in Germany. That supports GDPR requirements and data residency for European customers, and it applies to the data inside Softr Databases as well as user accounts.
Is Softr GDPR compliant?
Softr hosts all user data in Germany, inside the EU, so data doesn't leave the region in normal operation. Softr's permission model also lets you limit which staff and which app users can reach personal data, at both page level and record level.
How does Softr control which users can see which data?
Softr applies access control at three levels. User groups decide which pages, blocks, and action buttons a person can reach. Global data restrictions apply at record level, so a user only loads the rows their group is allowed to see. Action permissions decide which buttons each group can use, including conditional rules on individual records. Groups can be static, or dynamic and assigned automatically from a field in your database.
How do I verify app permissions are correct before I publish?
Softr includes a preview that runs the app as any user you select. You check exactly what each group sees before publishing, without creating real test accounts and logging in and out. The same preview works before you deploy a change to an app that's already live.
Can our database credentials or API keys be exposed to end users?
No. Softr runs database connections and operations server-side, so credentials and queries never reach the user's browser. A user can't intercept a network request to extract an API key or bypass a permission rule. Credentials for workflow integrations are stored on Softr's servers and aren't exposed to app users.
What authentication methods does Softr support, and on which plans?
Softr supports email and password sign-in on every plan. Pro adds one-time codes and Google sign-in. Business adds two-factor authentication and domain-restricted sign-up. Enterprise adds SSO over SAML and OpenID, which covers Okta, JumpCloud, and other standard identity providers, plus SCIM for automatic user provisioning and deprovisioning.
Can we control who is allowed to sign up for an app?
Yes. Softr offers open sign-up, domain-restricted sign-up, and invite-only access. Domain-restricted sign-up limits accounts to email domains you approve and is available on Business. Softr also supports mandatory logouts as a session guardrail.
Does the Vibe Coding block introduce a security risk?
No. The Vibe Coding block is scoped to a single UI component rather than your app's infrastructure. Softr parses the generated code and extracts its data actions into a visual panel, where you apply user group permissions to each action. The block inherits the app's existing data restrictions, and any webhook it calls can be locked so only your app can trigger it.
If we connect an AI assistant over MCP, does that create a second way into our data?
No. MCP access runs under the identity of the person using it. User groups, page and block visibility, action permissions, and global data restrictions all apply unchanged. An agent can do what that user could do in the interface, and nothing beyond it. There's no separate set of API permissions to configure, audit, or keep in sync.
Report a vulnerability, get rewarded
Our bug bounty program is open to independent researchers by invite. Responsible disclosures are reviewed, prioritized by severity, and rewarded.