English
Budibase Hosting
Build internal tools, forms, and admin panels over your data with a low-code visual builder.
No setup fees-
One click deploy -
4 GB RAM Memory needed -
50 GB Disk Space Needed -
From 10 € Price
Official links
Budibase’s official links and original website
Budibase Website
More
Tech
- Docker image
- budibase/budibase:latest
- Default port
- 80
How Budibase works
Budibase combines an application builder, data connections, users, permissions, forms, screens, and workflow automation. Builders connect databases, APIs, business tools, or Budibase-managed data, then place reusable interface components on screens and bind them to queries, forms, actions, and role rules.
Automations react to events such as form submissions, data changes, schedules, or incoming requests. Steps can query data, transform values, call APIs, route approvals, or interact with supported services. LLM-enabled workflows are possible when compatible providers and credentials are configured, but no model or API allowance is included in the hosting plan.
Key Budibase features
Forms and reusable components support internal portals, approval queues, inventory tools, customer administration, and other operational interfaces. Data-source connectors let one application present information from several systems, while access controls determine which users may open, read, create, or modify each workflow.
External databases, APIs, business tools, authentication providers, LLMs, and automation destinations remain independent services. The hosted Budibase package cannot send application email, so email actions, invitations, verification, and recovery cannot be used. Some Budibase functionality or governance options may also depend on edition, configuration, or provider entitlements.
Budibase vs Retool
Budibase is an open-source platform for building internal tools and automating workflows with data, APIs, forms, components, and permissions. Retool is a commercial platform that connects production data to internal applications, workflows, forms, mobile interfaces, and AI functions, with vendor-managed governance and enterprise controls.
Retool may suit organisations wanting a mature managed platform, maintained integrations, central governance, compliance options, and commercial support. Budibase is compelling when teams want a self-hosted builder and are prepared to operate data connections, credentials, edition boundaries, user administration, workflow behaviour, backups, and upgrade testing.
Who uses Budibase
Operations teams use Budibase for approval portals, equipment registers, service requests, inventory views, and back-office dashboards. IT groups can replace fragile spreadsheets with role-controlled forms, while product teams prototype internal workflows around existing APIs and databases.
The platform is not a source of business data by itself, and it does not remove the need to secure connected systems. Query design, permissions, API limits, automation errors, and external-provider outages can affect an application even when the Budibase interface remains available.
Self-hosting Budibase: requirements and cost
Demand is driven by builders, published users, applications, screens, forms, queries, data volume, automation frequency, file uploads, external connections, and simultaneous requests. The catalogue records PostgreSQL and MariaDB as Not required; Budibase application data and packaged internal services still need coordinated persistence and recovery.
On AvaHost, Budibase uses Plan 3 at €10. The hosted Budibase package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. External databases, APIs, LLM providers, authentication services, business-system accounts, and automation destinations are not bundled. Application email is disabled, so mail actions, invitations, verification, and email recovery are unavailable. Validate edition-specific features before promising them to users.
F.A.Q
Budibase is recommended on Plan 3 at €10. Its 3 GB application minimum maps directly to the four-gigabyte public tier. Builder activity, published users, app count, queries, uploaded files, automations, external connections, and simultaneous requests can increase demand, especially when several internal tools share one installation.
A custom hostname can serve Budibase through automated HTTPS after DNS points to AvaHost. Test builder access, published applications, API calls, authentication callbacks, webhooks, and embedded links after the domain is attached. Update every external service that has stored the former URL before removing the old address from use.
No. Budibase can connect business databases, APIs, tools, and LLM providers, but the hosting plan does not supply those systems, accounts, quotas, or credentials. Each connection remains subject to its provider’s permissions, availability, and charges. Test least-privilege credentials and error handling before publishing a workflow to operational users.
Application email is disabled across AvaHost. Budibase email actions, invitations, verification, and email-based recovery are therefore unavailable in this deployment. Workflows may still use other supported APIs or services when separately configured, but their accounts and credentials are not included. Test every critical automation path and document a non-email operational fallback.