Introduction
Momo documentation
Section titled “Momo documentation”Momo is a standalone multi-node container runtime and gateway. You describe apps in YAML (app.yml), apply them with a single CLI, and Momo reconciles Docker on linked nodes while the gateway routes HTTP/WebSocket traffic — including scale-to-zero cold starts.
Client ──▶ [optional momo edge] ──▶ momo gateway ── Acquire/Release ──▶ momo node ──▶ Docker │ │ └──────── shared store (file|sqlite|postgres) ─┘| Role | Command | Responsibility |
|---|---|---|
| Edge | momo edge |
Optional TLS/HTTP front door (static PEMs or Let’s Encrypt HTTP-01) |
| Gateway | momo gateway |
Route watch, per-node gRPC pool, HTTP/WebSocket proxy, /healthz /readyz /metrics |
| Node | momo node |
HostSpec → Docker reconcile, Acquire/Release, idle reaper, heartbeats |
| Operator | momo apply / remove / … |
Mutate desired state; export/import for backup and DR |
Next steps
Section titled “Next steps”- Quick start — run gateway + node locally
- Architecture — how the pieces fit together
- Spec schema —
app.ymlreference - CLI reference — every command