Budibase Self-Hosted

Build operational apps and automations on customer-hosted infrastructure.

6 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Official all-in-one Docker image or Docker Compose; Kubernetes options

  2. Operated by

    Your team

    Customer manages containers, persistent storage, credentials, backups and upgrades; account/license connectivity remains relevant.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial all-in-one Docker image or Docker Compose; Kubernetes options
InfrastructureServers / containers
The reviewed self-hosted Docker option runs a persistent application/worker stack with CouchDB, Redis and object-storage components. Classified servers; workflow triggers do not imply function-based serverless.
Licensing modelOpen Source / Open Core
Budibase documents GPLv3 core packages, MPL client/component packages and BSL paid-feature packages. The broad self-hosted listing therefore includes restricted feature code alongside the open-source base.
LicenseGPLv3 core, MPL client/component packages and BSL paid-feature packages; edition terms apply

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

The OIDC guide configures an installation-specific callback, issuer configuration, client ID and secret for user sign-in, with automatic user creation on first OIDC login. Requiring all users to use SSO is documented separately as an Enterprise feature.

Self-hosted user OIDC versus paid enforced-SSO policy; restrict IdP app assignments and preserve verified-email linking · Source ↗ · Enterprise SSO enforcement ↗ · Reviewed 2026-11-20

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official all-in-one image/Compose example requires generated secrets and a persistent data volume. The documented latest image reference moves; pin a selected release and plan backup and external dependencies.

Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (select a released image tag; latest moves) · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The all-in-one Docker guide says 2 processing cores and 6 GB RAM should suit most use cases, while explicitly making resource needs usage-dependent. Persistent application/database/object-store data and any external data sources need separate storage and capacity planning.

All-in-one Docker recommendation, not an HA or 1-TB throughput guarantee · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The v4.0.0 repository describes Budibase overall as GPLv3, with MPL-licensed packages for generated apps and paid feature packages under BSL. Self-hosted plan upgrades use an account-portal licence key and validation connectivity; confirm current feature quotas and paid entitlements.

Package-specific terms and self-hosted licensing; generated apps are distinguished from the builder · Source ↗ · Self-hosted licence activation and renewal ↗ · Licence connectivity ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The publisher-designated GitHub release checked was v4.0.0, published 2026-11-10. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.

Upstream Budibase/budibase release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

This entry excludes Budibase Cloud. Current documentation requires outbound HTTPS for license activation/validation, and some authentication/AI capabilities depend on vendor services. Package licenses differ; paid features are not covered by the core open-source license.

Category fit

Internal tools
Internal app, form and automation development with connected data; plan and component licensing determine available features.

Compare within Internal tools

  • Appsmith Self-HostedBuild internal applications with visual widgets, queries and JavaScript on customer-operated infrastructure.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
    • Azure
    Customer-operated · Open Source / Open Core
  • CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • CortezaLow-code platform for business records, workflows and configurable CRM applications.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Grist Self-HostedRelational spreadsheet platform for collaborative business data and configurable operational applications.
    • AWS
    • Azure
    Customer-operated · Open Source / Open Core
  • Mendix on KubernetesCommercial low-code application runtime operated in customer Kubernetes infrastructure.
    • AWS
    • Azure
    • Google Cloud
    • STACKIT
    Customer-operated · vendor control plane · Commercial Only
  • NocoDB Self-HostedSpreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Railway
    Customer-operated · Source Available

Showing 8 of 10 other listings in Internal tools. These products address related workflows; read their category-fit notes before comparing scope. See all of Internal tools →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Budibase self-hosting on DigitalOcean ↗ · DigitalOcean

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The project documents its one-click Budibase server in a customer DigitalOcean Droplet and requires at least 4 GB RAM. This is separate from Budibase Cloud. Keep the internal database port private and review backups, updates and the selected image before production use.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory