Installation
Waypoint ships as a single Go binary. It needs:
- A reachable Redis (or Valkey) instance for connection tracking and distributed locks.
- A Tailscale account, an ACL tag for the Waypoint node, and an auth key (or OAuth/WIF credentials).
- For Postgres or MongoDB mode: admin credentials on the backend so Waypoint can create scoped users.
Build from source
Section titled “Build from source”git clone https://github.com/redoapp/waypoint.gitcd waypointgo build ./cmd/waypoint/This produces a waypoint binary in the current directory. Go 1.26 or newer is required.
The companion waypoint-monitor TUI dashboard is a separate binary:
go build ./cmd/waypoint-monitor/Container image
Section titled “Container image”Dockerfiles are included at the repo root:
docker build -t waypoint -f Dockerfile.waypoint .docker build -t waypoint-monitor -f Dockerfile.waypoint-monitor .Development environment
Section titled “Development environment”The repo uses devenv with Nix. After installing devenv and direnv:
direnv allow # or: devenv shell --impureThis drops you into a shell with Go, golangci-lint, delve, and a local Redis service. Useful scripts:
| Script | What it does |
|---|---|
run-proxy | Runs Waypoint with waypoint-dev.toml (sources .env if present) |
debug-proxy | Same, under dlv |
test | go test ./... |
coverage | Full coverage report (unit + integration + e2e) |
The .envrc must use --impure because the devenv shell depends on environment variables (e.g. TS_AUTHKEY).