Installation Overview
RepoFlow supports a few installation options, each optimized for a different kind of environment. This page helps you choose the right one.
Quick recommendation
- Production (recommended): Helm chart (Kubernetes) → best for scaling, upgrades, observability, and long‑running environments.
- Single server / small production: Docker Compose → good balance of simplicity + separation of services.
- Personal sandbox: Docker (all‑in‑one container) → quickest way to run RepoFlow locally, not for production or serious self‑hosting.
If you’re evaluating RepoFlow for a team or production use, start with Docker Compose (single server) or Helm (Kubernetes).
Caution: Choose your deployment type up front. Switching deployment types later is not supported and usually requires a fresh deployment and a careful data migration plan. If you still need to switch, please contact support.
Compare options
| Option | Best for | Tradeoffs | Docs |
|---|---|---|---|
| Helm chart (Kubernetes) | Production, HA, scaling | Requires a Kubernetes cluster and Helm | Deploying with Helm |
| Docker Compose | Single VM, simple self‑host | Less “production‑grade” than Kubernetes, with limited built‑in HA | Deploying with Docker Compose |
| Docker (all‑in‑one container) | Personal sandbox | Everything runs in one container. Not HA. DB inside container. Not recommended to migrate later. | Deploying with Docker |
How to choose
Pick based on where you’re running RepoFlow:
- You have Kubernetes (or want the most robust deployment): use Helm.
- You’re deploying on one host and want something simple: use Docker Compose.
- You’re running it for yourself locally: use Docker all‑in‑one.
Air‑gapped environments
If your environment has no internet access:
- Helm: Air‑gapped deployment (Helm)
- Docker Compose: Air‑gapped deployment (Docker Compose)