CLI and API
Operate Omni Loader from code through the same control-plane contract.
The CLI uses the control-plane API. Scripts and operators therefore share validation, authorization, audit, and desired-state reconciliation.
API
One authority
Web and CLI use guarded endpoints.
Scope
Read-only or full
Limit automation to required authority.
Audit
Every mutation
Record actor, path, outcome, and denial.
Pipeline automation
Create and operate complete topologies.
Automation creates connections and pipelines, assigns agents or relay halves, provisions targets, edits tables, and controls lifecycle.
✓ Agent enrollment, approval, and revocation
✓ Agent-local secret references
✓ Create, assign, start, pause, reload, archive, and delete
✓ Target schema check and provision
Operational integration
Connect replication to existing runbooks.
Health endpoints support orchestration. Fleet, alert, schema, and log reads integrate with monitoring while webhooks deliver notifications.
✓ Fleet-wide search and status
✓ Source and destination positions
✓ Alert acknowledgement and resolution
✓ Scoped keys and sanitized errors
Keep exploring
See the connected parts of the platform.
Put replication lifecycle into your runbooks.
Tell us how you deploy and authorize automation. We will map API, scopes, audit, and commands.