Install Inflowenger

Quick Install

The fastest path. Asks a few questions, brings up Infra + Fractal, and — if you agree — the inspector panel, then prints your API Secret Key and the panel URL.

curl -fsSL https://raw.githubusercontent.com/Inflowenger/getting-started/main/install.sh | bash

It writes real docker compose stacks into ~/inflowenger (override with INFLOW_DIR), so afterward you manage them exactly like the manual steps below. The prompts read from your terminal even through the pipe; to run it unattended, drive it with env vars instead — e.g. accept every default and skip the panel:

curl -fsSL https://raw.githubusercontent.com/Inflowenger/getting-started/main/install.sh \
  | ASSUME_YES=1 INSTALL_INSPECTOR=0 API_JWT_SECRET=my-shared-secret bash

Prefer to see every step? The manual walkthrough below does exactly what the script automates, one stack at a time.

What You're Standing Up

Two headless services, and then a UI on top for development. The platform is the product; the dev panel is optional tooling on top. They meet on a shared Docker network, inflow_net.

Browser ─────► Dev panel frontend (Vue)   :8080
                     │ HTTP + WebSocket (logs)
                     ▼
        inflow-inspector-api (Go/Fiber)  :8025
        flows · context · logs · /infra/* proxy
                     │ NATS + HTTP  (inflow_net)
 ┌──────────────────────────────────────────────┐
 │ Platform  (network: inflow_net)              │
 │ Infra  :8022 / :4222  ◄── register ──►       │
 │ NATS + coordinator         Fractal (runtime) │
 └──────────────────────────────────────────────┘

Manual Setup: the Platform

Needs Docker with the Compose v2 plugin, and free host ports 8022, 8222, 4222. Everything starts with Infra.

cd platform
cp .env.example .env

Infra needs an API Secret Key — the shared HMAC secret the inspector panel uses to authenticate later. Set it yourself in .env (recommended, predictable across restarts):

openssl rand -base64 48 | tr -dc 'A-Za-z0-9' | head -c 60; echo

Or leave API_JWT_SECRET blank and copy the value Infra prints on first boot instead — see below. Either way, you'll reuse this key for the dev panel. Both stacks share an external Docker network — create it once per host, then bring the platform up:

docker network create inflow_net   # once per host; skip if it already exists
docker compose up -d
docker compose logs -f infra

Confirm a Healthy Start

On a healthy start, Infra logs the accounts it bootstrapped, the secrets it generated, and the address you'd use to add another Fractal.

{"level":"info","ts":1783630706.9686565,"msg":"System Account Loaded"}
{"level":"info","ts":1783630706.9711125,"msg":"Inflow Infrastructure Account is ready"}
{"level":"info","ts":1783630706.9714851,"msg":"Plugin Account is ready "}
{"level":"info","ts":1783630706.9714975,"msg":"API Secret Key is : PAykm7EqmSlmJ0NmU2t6WlNYOGRbviMnZMvEOe6RBw5s3tI6ZXlVxMJ9os57rCCC"}
{"level":"info","ts":1783630706.9810252,"msg":"you can add inflow resource by  'curl -fsSL http://192.168.1.4:8022/fractal/11/install.sh | bash'"}

{"level":"info","ts":1783630709.0359278,"msg":"Infra Server on NatsIO is ready on port 4222"}
{"level":"info","ts":1783630709.0359592,"msg":"Infra Server HTTP Monitor is ready on 8222"}
{"level":"info","ts":1783630709.0359704,"msg":"Infra Server Cluster is ready on Port 6222 , Name : abc.xyz..inflowenger.io"}

{"level":"info","ts":1783630709.0445325,"msg":"Infra Started"}

Add More Fractals

The compose file starts one Fractal. To add more against a running Infra, use the scoped one-liner from Infra's logs — it goes through the same default portal, no token required.

curl -fsSL http://<your-infra-address>:8022/fractal/11/install.sh | bash

Copy the exact line from your own Infra logs — the host, port, and path are specific to that instance. It prompts for a container name and tags, ensures the inflow_net network exists, and joins the new Fractal to it so it can reach Infra.

Manual Setup: the Dev Panel

The panel joins the same inflow_net, so the platform must be running first.

cd ../inspector
cp .env.example .env

Edit .env and set INFLOW_INFRA_JWT_SECRET to Infra's API Secret Key — the same value as API_JWT_SECRET, or whatever it printed in its logs:

INFLOW_INFRA_JWT_SECRET=<infra-API-Secret-Key>

docker compose up -d
docker compose logs -f

Sign In to the Panel

The panel authenticates exactly like Swagger UI: it's static assets with no credentials and no backend URL baked in, and there's no server-side session. You authorize your own browser at runtime.

Verify End-to-End

Persist Data & Secure the Operator Key

The platform stack mounts ./store:/data so Infra's state survives restarts. Without it, every restart mints new keys and invalidates existing Fractals, plugins, and panels.

OPERATOR_SEED=<seed-from-nk>

API_JWT_SECRET=<your-shared-secret>

Licensing

Inflowenger is free for standalone use. At startup, Infra generates a random, anonymous license key for analytics purposes — no action needed. For a paid or sponsored license, name your cluster instead, in platform/.env:

INFRA_CLUSTER=<your-cluster-name>

Ports & Environment Variables

Ports

platform/.env

inspector/.env

Troubleshooting & Teardown

# inspector panel (add -v to also drop the cached source-build volumes)
cd inspector && docker compose down

# platform (add -v to also delete Infra's persisted keys in ./store)
cd ../platform && docker compose down