Skip to content

Integrations

Exporters push Evidence Events in. Evaluators ask Evaluate at a deploy boundary. They are different jobs — even when they share a git repo.

v1 sources

GuideRoleShips as
Kubernetes exporterDeploy (+ config) factsHelm chart (Evitrus/exporterk8s/)
EventBridge → ECSDeploy factsEventBridge + Lambda
GitHub AppBuild + Test factsEvitrus-hosted webhook
GitHub Actions exporterBuild / Test / weaker Deploy factsEvitrus/actions/export@v1 mode: emit
Ingest API / SDKCustom emittersPOST /ingest

Linear (Plan) and the Alert receiver (Operate incidents) are v1 sources; setup guides land with those exporters.

v1 evaluators

Independent from the exporter for the same source. Fail-open if Evaluate is unreachable. A deny records deploy.blocked.

GuideRoleShips as
GitHub Actions evaluatorPipeline gateSame action, separate mode: check step
Kubernetes evaluatorAdmission gateSeparate Deployment (Evitrus/exporteradmission/)

Legacy / optional

Not in the v1 catalog. Kept for teams that already installed them. Prefer the runtime exporter when they disagree with a CI-emitted deploy.

GuideNotes
Terraform → ECSApply-time emit. EventBridge is the v1 ECS path.
Kubernetes auditAPI-intent webhook. Does not replace the Deployment informer.

Evitrus — observability for auditability