Budibase

Key features

• Visual app builder Screens are assembled from drag-and-drop components such as tables, forms, cards, and charts, with navigation, theming, and role-based visibility. Templates and prebuilt blocks give teams a starting layout for common internal apps.[1]

• Built-in database Apps can store records in the built-in Budibase DB with tables, relationships, file attachments, and CSV import and export, so simple tools need no external database at all.[1]

• External data connections Apps also connect to outside data including PostgreSQL, MySQL, SQL Server, MongoDB, CouchDB, Oracle, Google Sheets, Airtable, S3, and REST sources, letting one screen combine internal and third-party records.[1]

• Workflow automations Automations trigger on record events, schedules, webhooks, or app actions and chain steps such as creating rows, sending messages, and calling APIs. Cron-style scheduling and webhook triggers cover recurring and event-driven operations.[1]

• Access control and SSO Role-based access, OAuth2 and OpenID Connect, and Google, Azure AD, Okta, and Auth0 integrations gate who can view and change each screen and record. Single sign-on itself is a paid-tier capability, starting at Premium.[1][2]

• Public API and integrations A REST public API described by an OpenAPI specification lets external systems read and write app data, and integration connectors such as Zapier, Slack, and email tools link automations to the wider stack.[1]

• AI-assisted building An AI agent can generate apps, screens, and data structures from a description, with the output remaining editable in the visual builder. AI builder requests are metered separately from plan seats.[1]

• Cloud or self-hosted deployment Teams deploy on Budibase Cloud or self-host with a single Docker image, Docker Compose, or Kubernetes, with a guided Azure path. Audit logs, backups, and uptime SLAs vary by plan, with the strongest guarantees on Scale and Enterprise.[1]

Who will love it

• Ops and IT teams with a backlog of internal apps Teams drowning in requests for dashboards, approval flows, and admin screens get a purpose-built path: one reviewer reported deploying services on Azure much quicker than before. The combination of builder, database, and automations covers the standard internal-tool backlog.[1][2]

• Cost-sensitive teams that can self-host The free self-hosted core includes unlimited apps, automations, and users, so a team with Docker or Kubernetes capacity gets substantial tooling for infrastructure cost alone. Paid tiers add SSO, support, and compliance rather than unlocking the builder itself.[1][2]

• Regulated teams needing EU hosting and audit trails EU-hosted cloud, SOC2 and ISO posture, GDPR and DPA support, audit logs, and directory sync on higher tiers suit teams that must show where data lives and who touched it. These are plan-gated, so they fit buyers already budgeting for Premium or above.[1][2]

Who should avoid it

• Teams needing deep custom logic or bespoke UX Budibase assembles standard business interfaces well but is not a full-code framework: highly custom interactions, complex domain logic, and polished customer-facing products will strain the component model. Those teams should budget for custom development instead.[1][2]

• Buyers expecting everything in the free tier SSO starts at Premium, AI builder requests are a paid add-on, and enforced SSO, long audit retention, and air-gapped deployment sit in Enterprise. Teams that need those capabilities must price a paid plan, not just the free core.[1]

• Teams wanting white-glove support and mobile polish Inspected reviewers raised pricing concerns, an unpleasant mobile experience, and limited support on lower tiers. Teams whose staff work primarily on phones, or that need strong vendor support from day one, should verify both before committing.[1]

Community signals

Compatibility