Mothership

Process supervisor with HTTP exposure. Launch your fleet, route traffic, run WASM plugins.

Mothership wraps, monitors, and exposes your application fleet. It launches child processes with dependency ordering, proxies HTTP and WebSocket traffic to them, runs migrations before anything starts, and shuts everything down gracefully. It is not a container orchestrator — it is the thing you run inside the container, or straight on a VPS.

Fleet management

Launch ships and bays with dependency ordering, health checks, crash-loop backoff, and graceful dependency-aware shutdown. Learn more.

HTTP exposure

Named binds, regex routes, User-Agent routing, static files, compression, and a CORS preflight cache — all in front of your processes. Learn more.

Docking protocol

WebSocket multiplexing over a single Unix socket for real-time apps that don’t need their own HTTP server. Learn more.

Safe launches

Uplinks verify external dependencies before launch; prelaunch jobs run migrations first; flagship election makes sure only one server runs them. Learn more.

WASM payloads

Sandboxed request/response processing at the proxy layer: rate limiting, CORS, JWT validation, IP allowlists. Fail-closed. Learn more.

Observable

Prometheus metrics, per-ship memory monitoring, a real-time TUI dashboard, and Ja4H request fingerprinting. Learn more.

Get started

The Quickstart takes you from cargo install mothership to a running fleet with a validated manifest in a few minutes.