Install the gateway binary

The gateway ships as a single compiled binary plus its services/ config tree, migrations/, and bundled web assets, published to GitHub Releases. No container runtime required.

Pick the binary when you deploy to bare metal, a VM, or anywhere you want the server as a plain executable managed by systemd, a process supervisor, or a one-shot install.

One-line installer

curl -sSL https://get.systemprompt.io | sh

This detects your OS and architecture, downloads the signed tarball, verifies its SHA256, and installs to /usr/local/bin (root) or ~/.local/bin (user).

Flags

# Pin a specific version
curl -sSL https://get.systemprompt.io | sh -s -- --version v0.2.2

# Install to a custom prefix
curl -sSL https://get.systemprompt.io | sh -s -- --prefix /opt/systemprompt

# Additionally verify the cosign signature (requires cosign in PATH)
curl -sSL https://get.systemprompt.io | sh -s -- --verify

Manual download

Pick your tarball from Releases. Prebuilt assets cover Linux (amd64/arm64), macOS (Intel/Apple Silicon), and Windows (amd64). Verify and extract:

curl -LO https://github.com/systempromptio/systemprompt-template/releases/download/v0.2.2/SHA256SUMS.gateway
grep systemprompt-0.2.2-linux-amd64.tar.gz SHA256SUMS.gateway | sha256sum -c -
tar -xzf systemprompt-0.2.2-linux-amd64.tar.gz
cd systemprompt-0.2.2-linux-amd64
./systemprompt --version

Run

You need a Postgres database and at least one AI provider key:

export DATABASE_URL=postgres://user:pw@host:5432/systemprompt
export ANTHROPIC_API_KEY=sk-ant-...
systemprompt

On start the gateway writes a profile, waits for Postgres, runs migrations, and serves the API on port 8080.

Where to go next

For cosign signature verification, the full asset matrix, and tarball contents, see the full binary recipe in the template repository. For how releases and assets work on GitHub, see the GitHub Releases documentation.