Hivekeep
EN
Configure
Install

Get Hivekeep running.

One command does everything. Once it's up, Queenie sets up the rest by chatting with you, so there are no config files to edit.

Recommended · the simplest way

Paste one line. That's it.

Run this in a terminal on your Linux or macOS machine. It installs everything for you.

curl -fsSL https://raw.githubusercontent.com/MarlBurroW/hivekeep/main/install.sh | bash

When it finishes, open the link it prints in your browser. Queenie does the rest.

Optional

Want a custom port, a domain, or Docker?

Skip this if the one-liner above is all you need. Otherwise answer a couple of questions and we'll generate the exact command for your setup.

1 · How will you use it?

2 · Settings

3 · Run it

Installshell
curl -fsSL https://raw.githubusercontent.com/MarlBurroW/hivekeep/main/install.sh | bash

Your encryption key is handled for you. The installer auto-generates and saves it at $DATA_DIR/.encryption-key so your secrets survive restarts. Back up that file alongside your database. (Pin a fixed ENCRYPTION_KEY with the advanced toggle above if you'd rather manage it yourself.)

If the install fails
  • port already in use / EADDRINUSE: port 3000 is taken. Change the Port field above and re-run.
  • Windows: the installer is Linux and macOS only. Run it inside WSL2, or use Docker Desktop.
  • Download or clone hangs: make sure the machine can reach github.com and bun.sh over HTTPS (a proxy may be blocking them).

Open http://localhost:3000 in your browser. Queenie walks you through the rest (admin account, your first AI provider, your first agents). No config files to edit.
Advanced & other options Requirements, and Docker vs native vs source
Before you start

What the one-liner needs.

Most machines already have all of this.

You can run sudo
The installer needs it to install missing system packages (git, curl, unzip).
About 500 MB free disk
Room to clone and build. 1 GB or more is comfortable.
A 64-bit machine
x86_64 or ARM64. 32-bit (older Raspberry Pi) is not supported.
Outbound HTTPS
It downloads from github.com and bun.sh, so those must be reachable.
openssl present
Used to generate keys. It ships with almost every Linux and macOS.

On Windows? The native installer doesn't run on Windows directly. Use WSL2 (run the one-liner inside your Linux distro) or Docker Desktop.

Compare

Native, Docker, or from source?

All three run the exact same app. They differ in how it lives on the machine.

Recommended

Native (install.sh)

Pick this if you just want it to work. One command, on your own Linux or macOS box.

  • One command, builds locally, no image to publish or pull
  • Saves your encryption key automatically, secrets persist
  • Runs as a service (systemd / launchd), auto-update with rollback
  • Agents own the box: install tools & deps, direct hardware access
  • Modifies the host system (by design)
  • Linux & macOS only (Windows via WSL2)
Container

Docker

Pick this if you already live in Docker and want a clean, sandboxed appliance.

  • Fully isolated, zero host pollution
  • Runs anywhere Docker runs, including Windows
  • Published image is not available yet, prefer native for now
  • Agent-installed tools & binaries don't survive a restart
  • You must persist the data volume or you lose your secrets
From source

Manual

Pick this if you want to read the code, hack on it, or run it your own way.

  • Full control: clone, build, run with Bun yourself
  • Best for contributors and development
  • No service, no auto-update, you wire those up
  • You handle Bun, build, migrations and the encryption key by hand