Workers pull compliance and remediation jobs, open agentless sessions to targets, evaluate profile rules, and write structured outcomes back to the platform.
Execution layer
WorkersThe Execution layer turns queued intent into action — Celery workers run checks, remediation, discovery, and schedules while streaming logs live.
Celery workers execute checks, remediation jobs, discovery scans, and scheduled tasks while streaming logs in real time
Where it sits in the stack
- 01 Access layer
- 02 Control plane
- 03 Data and messaging
- 04Execution layer Focus
- 05 Managed targets
How requests move
- 01
Worker claims a queued task
- 02
Session opens to the managed target
- 03
Checks or remediation run with live logs
- 04
Results and status return to the control plane
What this layer does
-
Celery workers for checks, remediation, and discovery
-
Shared execution path for scheduled and on-demand jobs
-
Real-time log streaming into the operator console
-
Retry-friendly workers that recover stalled work
Discovery scans and scheduled tasks share the same execution fabric, so capacity and retries behave consistently across workloads.
Log streaming keeps operators honest about what ran: failures are visible as they happen, not only after a batch finishes.