Next steps

You have Padas Motion installed and a sample pipeline on loopback TCP. Use these pages for real traffic and production shape.

Official containers and cloud images are not published yet.

More Motion Engines

Padas UI can manage additional Motion Engine instances (console: Cores; tree: core/) on other Linux hosts. Copy packages/padas-core-* from the Motion install (or use a padas-core release), install on that host, enroll with the same --ui-url as the console ($PADAS_HOME/core/bin/padas enroll on the engine host), then register/enroll under Services → Cores. Getting started does not require a second host. See Architecture.

Connectors

Replace the TCP helper with a real source and sink: Connectors.

Users, TLS, and hardening

Operators and first-boot identity: Users, roles & permissions.

TLS, API exposure, and a production checklist: Runtime operational security.

Pipelines and Management

Design and edit pipelines: Configuration → Pipelines.

Deploy, Remove, and runtime status: Management → Pipelines. Core Sync: Management → Cores.

Lookup (optional)

Not required for the sample TCP pipeline. Install nested padas-lookup-*, enroll (admin API until Services → Lookup ships), start padas-lookup-server, enable Core [lookup], bind tables, then PDL lookup: Enable lookup enrichment.

Motion Engine TOML

Override engine defaults in $PADAS_HOME/core/etc/padas.toml ($PADAS_HOME=/opt/padas): Motion Engine TOML.

Padas Chronos (emerging) is not this install path — see What is Padas?.