Get started
Install on your own or home server
What it takes to run Moorhold on a physical server you look after yourself, in an office or at home. It uses the same signed installer as the cloud routes, run by hand.
You can install Moorhold yourself now with the signed release 2026.11.4 and an access key. Moorhold is in early access: self-install is new, and the first installs outside our own team are happening now. If a step or a screen does not match what you see, email hello@moorhold.dev.
This route needs more from you than a cloud server: you look after the hardware, the network and the router. If that is not for you, the IONOS or Hetzner install guide is simpler.
At a glance
- Server
- Your own hardware and connection
- Where your data lives
- Your office or home
- How many steps
- About 8 steps, a few commands, and router settings
What you'll have at the end: Moorhold running on your own address, such as data.yourorg.example, with one sign-in for the portal and its tools. The full profile includes the dashboards tool and the data catalogue. The core profile, for an 8 GB server, leaves those two out.
What you need
The server
- Memory: 12 GB for the full profile (dashboards and the data catalogue included), or 8 GB for the core profile, which leaves out the dashboards tool and the catalogue. From release 2026.10.16, the portal's Assets page on a core server searches its own tables, marts, pipelines and checks by name and description. The installer checks and stops if the server has less than 11 GiB (full) or 5.5 GiB (core). On a full server with less than about 24 GB of memory (the 12 GB size included), or a core server with 8 GB, 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.
- Processor: x86-64 (Intel or AMD). ARM servers aren't supported, and the installer stops on one.
- Disk: at least 100 GB, ideally an SSD. More if you keep backups or a large data lake on the same disk.
- Operating system: Ubuntu 24.04 LTS or Ubuntu 26.04 LTS (26.04 from release 2026.10.1). The installer also accepts Debian 12, though the install guide is written for Ubuntu. On any other system it stops before it installs anything. A fresh server install is simplest; a desktop install (Ubuntu, Kubuntu and similar) works too, with a few checks first.
The network
- A domain where you can add two DNS records, for example
data.yourorg.exampleand*.data.yourorg.example. - Either a public IPv4 address that reaches the server, with TCP ports 80 and 443 open to the internet, or a Moorhold relay: a small cloud server of your own that passes connections on to this one. A relay is meant for carrier-grade NAT, blocked ports and routers without NAT loopback. It's optional. We've tested it in containers, not on a real cloud server.
From us
- A Moorhold access key. An organisation's first key waits only if it's held for review by a person at Moorhold, so allow for that.
Before you start: home and office networks
Moorhold needs to be reachable on its name, by your users, by Let's Encrypt and from your own network. The installer checks this before it asks for certificates, says plainly what it found, and recommends a Moorhold relay when your network needs one. You can also check by hand first:
- CGNAT. Some providers, especially fibre and mobile broadband, share one public address between many customers (carrier-grade NAT). If the WAN address your router shows is in
100.64.0.0/10, or differs from the address a "what is my IP" site reports, port forwarding cannot work. Use a Moorhold relay, ask your provider whether they offer a public IPv4 address, or use a cloud server instead. - Ports blocked. Some residential providers block incoming port 80 or 443. Use a Moorhold relay: it needs no inbound port at home at all.
- A changing address. Most home connections get a new address now and then. Ask for a static address, or use a dynamic DNS service that updates both records (the name and the wildcard) when it changes. Until DNS catches up, Moorhold is unreachable.
- Hairpin NAT. Some routers cannot reach their own public address from inside the network, so
https://data.yourorg.exampleworks from outside but not from your desk. Turn on "NAT loopback" or "hairpin NAT" in the router if it has it; otherwise use a Moorhold relay, and every device works on the same name, inside and outside. - Power. A power cut stops Moorhold and its databases mid-write. A small UPS that lets the server shut down cleanly is worth having.
- Exposure. You are putting a server on the internet. Forward only ports 80 and 443, to this server only. Keep SSH off the internet, keep the system updated (
unattended-upgradesis on by default on Ubuntu), and keep the server on its own network segment if your router allows.
How the install goes
Current release: Moorhold 2026.11.4, published at get.moorhold.dev.
You do these in order, on the server and in your router and DNS settings:
- Install Ubuntu Server 24.04 or 26.04 LTS, and give the server a fixed local address.
- Forward TCP ports 80 and 443 from your router to the server. Leave every other port closed.
- Point two DNS records at your public address: your name and its wildcard.
- Download the installer and check it against its published checksum.
- Run the installer, and paste your access key when it asks. Choose the core profile on an 8 GB server. It checks the signed release, generates every password and key on the server, starts Moorhold and gets its certificates.
- Set up a relay, but only if the installer's network check recommends one.
- Open Moorhold on your address and finish the first run.
- Check it opens from outside your network, with a trusted certificate.
Follow the install guide in the docs
The install guide has every command, the installer's checksum and what to do when a step fails. It also covers:
- the checks to make first on a desktop install (Ubuntu Desktop, Kubuntu and similar) rather than Ubuntu Server;
- how to switch to a trusted certificate if you installed with a staging one, as an earlier version of this page suggested;
- how to check the release's signature yourself.
A relay, if your network needs one
A Moorhold relay is a small cloud server of your own, on Hetzner Cloud or IONOS Cloud. Your DNS points at the relay; it passes each connection on to this server over an encrypted WireGuard tunnel that this server opens, so you need no port forwarding at home, and every device reaches Moorhold on the same name whether it's on your network or not. The relay never holds a certificate or sees a request: TLS ends on your server, and the relay passes each visitor's own address on to your server. The relay is optional. We've tested it in containers on our own machines, not on a real cloud server, so if you try it, tell us how it goes. The install guide has the relay steps.
First run
- Go to
https://data.yourorg.example/setupand enter the one-time setup code the installer printed. - Set the admin password: at least 16 characters.
- Connect your organisation's sign-in (Microsoft Entra ID, Google or Okta), or skip it.
- Choose how to get to your first dashboard: the sample data, if it's on the server, or your own data.
First-run setup describes these steps in more detail; they are the same on your own server.
After the install
Backups
A new install takes encrypted backups of its databases every day, on the same machine. Keep a copy of the backup key somewhere else, and test a restore before you rely on the server: a single machine at home has no other copy. The install guide says where to read the key. Ask us at hello@moorhold.dev if you need help with them.
Newer releases
To update the server to a newer release, see Upgrading. It says which release to use, and that release's notes say how. From release 2026.10.16, an update that an admin has approved shows its progress in the portal, in a window that names each step and keeps checking while Moorhold restarts. The update to 2026.10.16 itself shows that window only once Moorhold has restarted. If they don't cover the release your server runs, email hello@moorhold.dev and we'll help.
Your network
If your public address changes, update both DNS records. If you change routers, forward ports 80 and 443 again. With a relay, neither applies: DNS points at the relay, and your server dials out to it.
If something goes wrong
The install guide says what to do when the installer stops or something doesn't open.
If you get stuck, email hello@moorhold.dev and say which step you reached. Please do not send passwords, keys or other secrets.