Getting started
This path takes you from host prerequisites to a verified Core (optionally with UI): install → runtime config → quickstart → hand-off to Configurations / Management for ongoing operations.
Runtime vs control plane
Padas Core is the data-plane runtime: ingestion, stream routing, PDL execution, and delivery. It is fully drivable via TOML + HTTPS API (https://<CORE_IP>:8999/api/v1/…) for GitOps-style automation.
Padas UI is the control plane console: register engines, edit registry objects, run Management deploy/assign flows, and observe Home — Control Tower. The UI requires at least one reachable Core to be useful; it does not replace the engine process.
| Mode | When to use it |
|---|---|
| Core only | Smallest footprint: CI, laptops, air-gapped scripting—padas.toml under $PADAS_HOME/etc/ drives behavior. |
| Core + UI | Shared operator workflow, multi-Core visibility—data plane semantics unchanged. |
Read order
Identity, access control, and tenant-style concerns belong in Advanced Settings → Security, not in the first-run guides.