Install on Hetzner Cloud
On this page
Hetzner Cloud is a good choice when its 16 GB machine is in stock, which often it isn't. It's owned and run in the EU, with data centres in Germany and Finland. This guide takes you from a new Hetzner server to Moorhold's setup page on your own address.
Before you start
Section titled "Before you start"You need:
- a Hetzner Cloud account;
- a domain where you can add two DNS records, for example
data.yourorg.exampleand the wildcard*.data.yourorg.example; - a Moorhold access key from account.moorhold.dev. An organisation's first key is approved by a person at Moorhold, so allow for that the first time.
See Requirements for the full list.
The server to choose
Section titled "The server to choose"The machine to choose is the CX43 (16 GB). It isn't always available in the EU locations, so check before you choose it. Before you start, open Add server in the Hetzner Cloud Console and check that the CX43 can be chosen in at least one location. If it can't, choose one of these instead, or use IONOS Cloud:
- CPX42 (16 GB);
- CCX23 (16 GB).
These are the 16 GB types the release's cloud config names for the full profile. On a full server with less than about 24 GB of memory (the 16 GB size included), more memory for a tool is refused: the portal says the server hasn't room, because Moorhold keeps 4.5 GiB spare above its apps' limits.
The release's cloud config names these types. Providers change what they offer, so check Hetzner Cloud before you buy.
Create the server
Section titled "Create the server"- In the Hetzner Cloud Console, open your project and select Add server.
- Choose a location: Falkenstein, Nuremberg or Helsinki.
- Choose the image Ubuntu 24.04.
- Choose the type CX43. If it can't be chosen in any location, choose the CPX42 or CCX23, or use IONOS instead.
- You can skip the SSH key. The server installs itself. If you set no SSH key, Hetzner emails you a root password, which you use once in the server's console to read the setup code.
- Under Cloud config, paste the cloud config below, with your two values filled in.
- Select Create & Buy now.
The cloud config
Section titled "The cloud config"This is the cloud config for the latest release, 2026.11.4. IONOS and Hetzner each have a file on
get.moorhold.dev, and both run these same commands. AWS has no file of its own and uses the same
cloud config. Paste it under Cloud config.
Replace the two values in angle brackets: your access key, and the address you'll use for
Moorhold, such as data.yourorg.example.
#cloud-config# Moorhold 2026.11.4 installer. Replace the two values in angle brackets.write_files: - path: /run/moorhold-install/access-key owner: root:root permissions: "0600" content: | <your access key>runcmd: - - bash - -c - | set -eu curl -fsSL --proto '=https' --tlsv1.2 -o /run/moorhold-install/install.sh https://get.moorhold.dev/2026.11.4/install.sh echo '31575b713ddee80dd36de3e5f1bb5e93da36a34f066ba145212ed37bf4ec6618 /run/moorhold-install/install.sh' | sha256sum -c - bash /run/moorhold-install/install.sh --hostname '<data.yourorg.example>' --profile full --access-key-file /run/moorhold-install/access-key- For an 8 GB server, change
--profile fullto--profile core. The core profile has no dashboards tool or catalogue. - The installer is pinned to 2026.11.4 and checked against its SHA-256 before it runs. The release lock it downloads is signed with Moorhold's release key, 7F6D12F3F6217F9C, and the installer checks that signature before it uses anything it downloads.
- The access key goes in a root-only file in memory, never on a command line. Security notes says where the server keeps its own copy.
- When get.moorhold.dev shows a newer release, use that release's cloud config instead. Each release's folder on get.moorhold.dev has its own.
The server then installs itself. It installs what it needs from Ubuntu's own archive, checks the release's signature, pulls Moorhold's signed images with your key, generates every password and key on the server, starts the stack and gets its certificates. None of those secrets is shown to you or leaves the server.
From 2026.10.16, a new server has the sample data only if the installer was asked for it. The cloud config above does not ask, so first-run setup offers Download the sample data. See First-run setup.
Point your domain at it
Section titled "Point your domain at it"- Copy the server's public IPv4 address from your provider's console.
- At your DNS provider, add two A records, both with the server's address as the value:
data(or the name you chose), for the portal;*.data, a wildcard for the tools. Moorhold publishes the dashboards tool, the catalogue and the orchestrator atsuperset.data…,datahub.data…andairflow.data…, behind the same sign-in.
If your DNS provider doesn't accept a wildcard, add three A records instead: superset.data,
datahub.data and airflow.data. With the core profile, only airflow.data is used.
The server needs ports 80 and 443 open to the internet, because it gets its certificates from Let's Encrypt.
Open Moorhold
Section titled "Open Moorhold"-
Open the server's console in the Hetzner Cloud Console (a browser window, not SSH) and sign in as root. If you set no SSH key, use the root password Hetzner emailed you. Read your one-time setup code:
Terminal window cat /etc/moorhold/secrets/MOORHOLD_SETUP_CODEIf the file isn't there, the server is still installing, so wait and try again. The code is never written to the install's log.
-
Go to
https://data.yourorg.example/setup, using your own address, and enter the code. -
Follow First-run setup to set your admin password and run your first pipeline.
From release 2026.10.16, the installer loads the sample data, Moorhold sample: AI Release Radar, only when it's asked to, and this cloud config doesn't ask. The first-run page then offers Download the sample data instead. From 2026.11.2, an admin presses it and the request is approved as they ask, so one admin is enough, however many admins there are.
If it doesn't open
Section titled "If it doesn't open"- Check that both DNS records are correct, and that ports 80 and 443 are open.
- The certificates may not be ready. Wait, then try again.
- Check in your provider's console that the server is running.
- If the portal opens but Superset doesn't, the wildcard record (or the three tool records) is probably missing.
- If
/setuprefuses the code, read the file again. A code works only until the admin password is set.
If you're still stuck, email hello@moorhold.dev and say which step you reached. Please don't send passwords, keys or other secrets.
Security notes
Section titled "Security notes"- The access key can only download Moorhold's software. It expires after 12 months, and you can revoke it at account.moorhold.dev.
- Your provider keeps a copy of the cloud config, so rotate the key after the install if that matters to you.
- When the registry accepts your access key, the installer keeps a copy that only root can read, in
/etc/moorhold/secrets/registry-access-key. Upgrades and reruns of the installer use that copy. Once the images are pulled, the installer deletes the file it read the key from, unless you added--keep-access-key-file. If you replace the key at account.moorhold.dev, give the server the new one withsudo moorhold access-key set. - To update the server to a newer release, see the release notes. From 2026.10.16, an update that an admin has approved shows its progress in the portal.
- Every other secret is generated on your server and never leaves it.
- A new install backs up its databases every day, on the same server. A cloud config install has no
terminal, so it doesn't print the backup key: it's in
/etc/moorhold/secrets/MOORHOLD_BACKUP_PASSWORD, readable by root only, andsudo moorhold backup keyprints it in a terminal. Keep a copy of the key off the server, and test a restore before you rely on it, because a backup on the same machine isn't a second copy.
Check the release yourself
Section titled "Check the release yourself"The cloud config checks the installer against its SHA-256 before it runs, and the installer checks the release's signature before it uses anything it downloads. To check the release's files yourself, on any computer, follow Checking by hand in Release files. That page also lists every file in a release and how each one is checked.