
# Budibase Self-Hosted

Build operational apps and automations on customer-hosted infrastructure.

Canonical page: https://launchinyourcloud.com/directory/budibase/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Budibase Self-Hosted

Build operational apps and automations on customer-hosted infrastructure.

- Listing: https://launchinyourcloud.com/directory/budibase/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3 core, MPL client/component packages and BSL paid-feature packages; edition terms apply
- Licensing model: open-source
- Installation: Official all-in-one Docker image or Docker Compose; Kubernetes options
- Architecture: Customer-operated app/worker services with database, cache and object storage dependencies
- Operations: Customer manages containers, persistent storage, credentials, backups and upgrades; account/license connectivity remains relevant.
- Product website: https://budibase.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

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.


### Category fit

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

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.budibase.com/docs/digitalocean (checked 2026-11-12). 


### Cloud deployment evidence

- Budibase self-hosting on DigitalOcean (digitalocean): https://docs.budibase.com/docs/digitalocean
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official Docker installation: https://docs.budibase.com/docs/docker

- Hosting options: https://docs.budibase.com/docs/hosting-methods

- Self-hosted license connectivity: https://docs.budibase.com/docs/self-hosted-licensing

- Network and AI service dependencies: https://docs.budibase.com/docs/whitelisting

- Official package licensing: https://github.com/Budibase/budibase/blob/master/LICENSE

- Product capabilities: https://github.com/Budibase/budibase

### Licensing sources

- https://github.com/Budibase/budibase/blob/master/LICENSE

### Infrastructure sources

- https://docs.budibase.com/docs/docker


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. 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. Scope: Self-hosted user OIDC versus paid enforced-SSO policy; restrict IdP app assignments and preserve verified-email linking. Source: https://docs.budibase.com/docs/openid-connect (reviewed 2026-11-20). Supporting source: Enterprise SSO enforcement — https://docs.budibase.com/docs/enforced-sso.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.budibase.com/docs/docker (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/budibase/budibase. Artifact reference: select a released image tag; latest moves.

- Minimum footprint / sizing: Documented. 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. Scope: All-in-one Docker recommendation, not an HA or 1-TB throughput guarantee. Source: https://docs.budibase.com/docs/docker (reviewed 2026-11-20).

- License pricing: Documented. 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. Scope: Package-specific terms and self-hosted licensing; generated apps are distinguished from the builder. Source: https://github.com/Budibase/budibase/blob/v4.0.0/LICENSE (reviewed 2026-11-20). Supporting source: Self-hosted licence activation and renewal — https://docs.budibase.com/docs/tenant-management. Supporting source: Licence connectivity — https://docs.budibase.com/docs/self-hosted-licensing.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream Budibase/budibase release record; commercial editions and deployment packages may differ. Source: https://github.com/Budibase/budibase/releases/tag/v4.0.0 (reviewed 2026-11-14).






