Get started
Run Moorhold on AWS
Moorhold works on Amazon Web Services, for teams that already run on AWS. It uses the same installer as every other provider, and takes more steps in the console.
AWS has EU and UK regions, so your server and your data can stay there. But Amazon is a US company. If your organisation has sovereignty or data protection requirements, check with your own advisers that AWS meets them. This is not legal advice.
At a glance
- Server
- m7i.2xlarge (8 vCPU, 32 GB)
- Where your data lives
- An EU or UK region you choose
- How many steps
- About 25 steps (estimate) and 2 pastes
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.
Use an m7i.2xlarge (8 vCPU, 32 GB), for example in London (eu-west-2).
Machine types as published on 5 October 2026 (AWS m7i.2xlarge (Vantage)). Providers change what they offer; check before you buy.
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.
How it works
Get an access key
Create one at account.moorhold.dev. See Get an access key.
Launch an instance
In the EC2 console, choose your region, then Launch instance. Choose the Ubuntu 24.04 image and the m7i.2xlarge type, with at least 100 GB of disk (gp3).
Allow web traffic
In the security group, allow HTTP (port 80) and HTTPS (port 443) from the internet, so people can reach Moorhold and the server can get its certificate. You do not need to allow SSH.
Paste the cloud config
Under Advanced details, paste this into User data, then launch:
Current release: Moorhold 2026.11.4, published at get.moorhold.dev.
#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-keyFor an 8 GB server, change --profile fullto--profile core. The installer is pinned to 2026.11.4 and checked against its sha256 before it runs. The key goes in a root-only file in memory, never on a command line, and is deleted once the images are pulled. The release lock it downloads is signed with key 7F6D12F3F6217F9C (public key).Give it a fixed address
Allocate an Elastic IP and associate it with the instance, so its address does not change when it restarts. The installer gets its certificates as soon as DNS points at the server, so do this and the next step promptly.
Point your domain at it, and open Moorhold
As in the IONOS install guide, from the domain step: two DNS records (your name and its wildcard), then the one-time setup code from the EC2 serial console or Session Manager, and the first-run steps at
/setup.
If you get stuck, email hello@moorhold.dev and say which step you reached. Please do not send passwords, keys or other secrets.