Deployment

-

This guide shows how to deploy Plano directly using Docker without the plano CLI, including basic runtime checks for routing and health monitoring.

+

Plano can be deployed in two ways: natively on the host (default) or inside a Docker container.

+
+

Native Deployment (Default)

+

Plano runs natively by default. Pre-compiled binaries (Envoy, WASM plugins, brightstaff) are automatically downloaded on the first run and cached at ~/.plano/.

+

Supported platforms: Linux (x86_64, aarch64), macOS (Apple Silicon).

+
+

Start Plano

+
planoai up plano_config.yaml
+
+
+

Options:

+
    +

  • --foreground — stay attached and stream logs (Ctrl+C to stop)

    • +

  • --with-tracing — start a local OTLP trace collector

    • +
+

Runtime files (rendered configs, logs, PID file) are stored in ~/.plano/run/.

+
+
+

Stop Plano

+
planoai down
+
+
+
+
+

Build from Source (Developer)

+

If you want to build from source instead of using pre-compiled binaries, you need:

+
    +

  • Rust with the wasm32-wasip1 target

    • +

  • OpenSSL dev headers (libssl-dev on Debian/Ubuntu, openssl on macOS)

    • +
+
planoai build --native
+
+
+
+

Docker Deployment

Below is a minimal, production-ready example showing how to deploy the Plano Docker image directly and run basic runtime checks. Adjust image names, tags, and the plano_config.yaml path to match your environment.

@@ -202,6 +236,11 @@ docker compose logs -f plano