Quick start
This page walks an operator (or an agent acting on the operator's behalf) through bringing up Hivemind from a fresh server.
You will have received an invite URL by email
Hivemind is gated behind single-use invite URLs. If you don't have one yet, email sales@seglamater.com to request design-partner access.
Invite URLs look like https://s.seglamater.app/i/<id>. They expire
in 24 hours and burn after a single successful install. If you need
a fresh one, just ask.
Server requirements
| Resource | Recommended | Minimum |
|---|---|---|
| OS | Ubuntu 22.04+, Debian 12+, Rocky 9 | Any Linux with kernel ≥ 5.10 |
| CPU | 2 cores | 1 core |
| RAM | 4 GB | 2 GB |
| Disk | 20 GB | 10 GB |
| Docker | Engine ≥ 24, with the docker compose plugin |
same |
The install user must be in the docker group, or be root.
Outbound network must reach (HTTPS / 443):
registry.seglamater.app— image pullupdates.seglamater.app— manifest + install scripts.seglamater.app— invite-scoped bundle download
Plus whatever public ingress you intend for Hivemind itself (typically behind a reverse proxy on 80/443).
Install (the one-liner)
On the target server, paste the invite URL into a curl | bash pipe:
That command:
- Fetches your signed deployment bundle from
s.seglamater.app. - Fetches the installer (
install.sh) fromupdates.seglamater.app. - Runs the installer non-interactively against the bundle.
The installer will:
- Verify the bundle's SHA-256 against our manifest.
- Pull the
hivemind-serverimage pinned by digest fromregistry.seglamater.app. - Stand up a Docker Compose stack (Postgres + server).
- Print the next-step URLs and the
/etc/hivemind/.envlocation.
Total time is typically 2–4 minutes on a 4 GB VPS. The installer is idempotent — safe to re-run if anything wedges.
After it finishes
The installer prints (capture all of these):
- Web UI URL (defaults to
http://localhost:8080). Put it behind your own reverse proxy with TLS. - Admin bootstrap URL — single-use, used to create the first admin account.
/etc/hivemind/.env— contains the database password, signing keys, and other runtime config. Back this up.
If you're handing the install off to an AI agent, the recommended procedure is in the email you received under "For an AI agent operator."
Verifying the signature (optional but recommended)
Hivemind ships a cosign signature alongside every release manifest. To verify:
# Fetch our public key (pinned by SHA-256 in the email you received).
curl -fsSL https://updates.seglamater.app/.well-known/keys/hivemind.pub \
-o /tmp/hivemind.pub
# Verify the manifest signature.
cosign verify-blob \
--bundle <path-to-manifest.json.sig> \
--key /tmp/hivemind.pub \
<path-to-manifest.json>
If verification fails, stop and email support@seglamater.com with the error output before doing anything further.
Need help?
Email support@seglamater.com with your customer ID. If the install failed, please include:
- The full output of the install command.
- The output of
docker compose psfrom the install directory. - Your server's distro + kernel version (
uname -a).