Signed releases

Get Moorhold

Download Moorhold's current signed release and check it yourself. Free for solo use.

Current release

Moorhold 2026.11.4 Early access release

Published 17 November 2026. If Moorhold fails to start at boot it tries once more and keeps a record, and an update that was interrupted by a restart is settled once Moorhold is running again. An approved update is installed once the update that was running has finished, and robots.txt on the portal and published tools is served as two lines. One admin is enough for an update, an admin can approve their own proposal, and automatic updates and off-site backups are free on every server. Commands that change your server run one at a time and say which step they're on. The Moorhold app for Mac shows the terms before it sets anything up, asks whether to load the sample dashboard, checks for the network first, and can update Moorhold itself.

Latest version, for scripts: get.moorhold.dev/LATEST

Install it

Choose a guide below. The cloud guides give you a cloud config to paste, which downloads install.sh, checks its SHA-256 and runs it. The own-server guide has you run the same steps by hand.

You'll need an access key

Your server uses it to download Moorhold and its updates. Get an access key from your Moorhold account at account.moorhold.dev.

Where will Moorhold run?

Moorhold's desktop app is for Macs with Apple silicon, and you can download it from moorhold.dev/download. There's no Windows app, and we aren't giving a date for one. On any other computer, run Moorhold on a server and use it in your web browser.

Get Moorhold for Mac

To choose a server, see the notes for IONOS Cloud (our recommended provider) and Hetzner Cloud.

Plans shows what you get, and how to talk to us about more.

Files in this release

Each version has its own folder on this host, and a published folder never changes. These are the files for 2026.11.4.

FileWhat it is
install.shThe installer. Its SHA-256 is checked before it runs, in every guide.
release.lockThe signed lock. It pins the release bundle and Node.js by SHA-256, and the bundle names every container image by digest.
release.lock.minisigThe signature on release.lock, made with the release key.
SHA256SUMSThe SHA-256 of the installer, the lock, the bundle and both cloud configs.
moorhold-2026.11.4.tar.gzThe release bundle the installer unpacks.
cloud-init-ionos.yamlThe cloud config for IONOS Cloud.
cloud-init-hetzner.yamlThe cloud config for Hetzner Cloud.

The SHA-256 of install.sh 2026.11.4:

31575b713ddee80dd36de3e5f1bb5e93da36a34f066ba145212ed37bf4ec6618

SHA256SUMS lists these files' SHA-256. It isn't signed itself. The signature covers only release.lock.

Check it

How a release is checked

  1. The installer's SHA-256 is checked before it runs. The cloud guides pin it in the cloud config you paste, and the own-server guide has you check it by hand.
  2. The installer checks release.lock with minisign against Moorhold's release key, which is built into it. If the signature doesn't verify, the installer stops.
  3. Then it checks Node.js and the release bundle against the SHA-256 in the lock, and the bundle pins every container image by digest.

Release key

Key ID 7F6D12F3F6217F9C. Public key: moorhold-release.pub

RWScfyH28xJtf1DCwDTYUUS3wlSzmrKr2426mvg+EfqIV+mqziD5q5Si

To check a release yourself: minisign -Vm release.lock -P RWScfyH28xJtf1DCwDTYUUS3wlSzmrKr2426mvg+EfqIV+mqziD5q5Si