Application hosting

Hosting Budibase

A platform for building internal applications and workflows. Self-hosted deployments use several cooperating services rather than a single static website.

Min vCPU
Not specified
Min memory
Not specified
Min storage
Not specified

Understand the setup

Check runtime, storage and installation requirements before choosing a server.

See requirements

Budget your resources

Allow room for the operating system, database and your actual workload.

Open resource planner

Build your shortlist

Compare plan details and review which requirements still need checking.

Explore plans

Must have

Installation requirements

  • Docker Engine and Docker Compose.
  • Network communication between the application, worker, database, object store and proxy.

Recommended

Planning guidance

No further general recommendations are published for this version.

Capacity depends on your workload

The guide refers to Docker prerequisites and recommends Linux for production; it does not establish a fixed workload capacity or RAM minimum.

We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.

Deploy with

Supported paths

  • Docker Compose

The host must provide

Runtime

CouchDB
Database service in the documented stack
MinIO
Object storage in the documented stack
NGINX
Stack proxy

Storage

Persistent data

Preserve database and object-store volumes. Back up configuration and application data before upgrades.

Step by step

Plan a Budibase deployment

  1. Prepare configuration

    Use the maintained Compose, environment and LiteLLM configuration files.

    Official instructions
  2. Replace secrets

    Change the example environment secrets before starting a publicly accessible deployment.

    Official instructions

Security

Before you go public

  • Restrict internal service access.
  • Keep database and file-storage credentials private.

Cost

Beyond the server price

  • Budget for all stack services, persistent data and backups.

Matching plans

Explore hosting options

Hetzner Cloud

Hetzner Cloud CPX12 (Germany and Finland)

1 vCPU
2 GB RAM
40 GB Storage
20 TB Transfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
Hetzner Cloud

Hetzner Cloud CPX21 (US locations)

3 vCPU
4 GB RAM
80 GB Storage
2 TB Transfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
Hetzner Cloud

Hetzner Cloud CPX22 (Germany and Finland)

2 vCPU
4 GB RAM
80 GB Storage
20 TB Transfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
Hetzner Cloud

Hetzner Cloud CPX31 (US locations)

4 vCPU
8 GB RAM
160 GB Storage
3 TB Transfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
Hetzner Cloud

Hetzner Cloud CPX32 (Germany and Finland)

4 vCPU
8 GB RAM
160 GB Storage
20 TB Transfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
Hetzner Cloud

Hetzner Cloud CPX41 (US locations)

8 vCPU
16 GB RAM
240 GB Storage
4 TB Transfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
Hetzner Cloud

Hetzner Cloud CPX42 (Germany and Finland)

8 vCPU
16 GB RAM
320 GB Storage
20 TB Transfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
Hetzner Cloud

Hetzner Cloud CPX51 (US locations)

16 vCPU
32 GB RAM
360 GB Storage
5 TB Transfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
Hetzner Cloud

Hetzner Cloud CPX52 (Germany and Finland)

12 vCPU
24 GB RAM
480 GB Storage
20 TB Transfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
Hetzner Cloud

Hetzner Cloud CPX62 (Germany and Finland)

16 vCPU
32 GB RAM
640 GB Storage
20 TB Transfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
hosting.com

Shared hosting — Starter

5 Websites
15 GB Storage
  • NVMe
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.
Hostinger

Hostinger KVM 1 VPS

1 vCPU
4 GB RAM
50 GB Storage
4 TB Transfer
  • KVM vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • Docker Engine and Docker Compose.This prerequisite has no comparable published plan field.
  • Network communication between the application, worker, database, object store and proxy.This prerequisite has no comparable published plan field.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.