Deploy Options

Three ways to run Rohrpost, depending on how much infrastructure you want to own.

Single VM

Docker Compose (or Podman Compose) on any Linux box. One command, everything included.

Kubernetes

Helm chart for production clusters — separate deployments per service, configurable resource limits.

Managed / SaaS

Hosted at app.rohrpost.io. No infrastructure to run at all — sign up and get an API key.

Single VM (Docker Compose)

This is the path covered in the Quick Start: clone the repo and run./deploy/deploy.sh up. It builds every service, runs migrations, and starts Postgres (pgvector + Apache AGE), NATS JetStream, Garage, Ollama, and the full Rohrpost stack. Comfortable on a 2 vCPU / 4 GB RAM VM.

For a machine that should keep Rohrpost running across reboots, a systemd user unit is included at deploy/rohrpost.service — it starts the compose stack on login and stops it cleanly on shutdown, with Restart=on-failure.

For internet-facing deployments, front the gateway, admin web, and MCP server with a reverse proxy that terminates TLS — deploy/apache2/ has example vhost configs for a three-subdomain layout (app, api, mcp).

Kubernetes

For running Rohrpost on an existing cluster instead of a dedicated VM, see theKubernetes deployment guide.

Managed / SaaS

app.rohrpost.io runs the same open-source stack with zero setup — register, create an API key, and connect. See pricing for plan limits.