Start Here
// Exploremap
The product map for the local runtime. FlowLayer Explore shows how a single orchestration server runs a multi-service stack and how clients observe and control that session — built for real development loops: repeatable startup, explicit dependencies, readable runtime state, practical debugging.
Flow in 3 signals
Section titled “Flow in 3 signals”| What you see | What FlowLayer does |
|---|---|
Service is blocked | Keeps dependents waiting until upstream readiness passes. |
| Partial stack starts in parallel | Schedules only nodes with satisfied dependencies in the same wave. |
| One client reconnects mid-session | Replays canonical server state instead of rebuilding context locally. |
First 10 minutes
Section titled “First 10 minutes”flowlayer-server -c ./services/flowlayer.jsoncflowlayer-client-tui -s http://127.0.0.1:7010 -token "$FLOWLAYER_SESSION_TOKEN"Run the server, connect the client, then inspect the first blocked dependency. That gives you useful runtime truth in under 10 minutes.
What you’ll learn
Section titled “What you’ll learn”- How dependency declarations become a runtime startup plan.
- How readiness gates block or unlock downstream services.
- How runtime state and logs are exposed through one control plane.
- How the official TUI acts as a thin operator client.
- Where FlowLayer fits compared to scripts, Compose, PM2, and hand-run terminals.
Recommended path
Section titled “Recommended path”- Read How FlowLayer Works for the core runtime model.
- Read Server then Client / TUI for the responsibility split.
- Finish with Use Cases and Compare, then keep Troubleshooting and Reference nearby.
Jump in
Section titled “Jump in” How FlowLayer Works Dependency graph planning, startup waves, readiness checks, and runtime propagation.
Server How flowlayer-server plans, orchestrates, and remains the session source of truth.
Client / TUI What the official client surfaces and why orchestration logic stays server-side.
Use Cases Concrete local scenarios: monorepo stacks, dependent services, and onboarding loops.
Compare Honest comparison against scripts, Docker Compose, PM2, and manual terminals.
Troubleshooting Fast checks for startup, readiness, config, and log issues.
Reference Binaries, config concepts, commands, token model, and protocol pointers.
If something fails while you read, open Troubleshooting and continue from there.