How the pieces fit together

One diagram of how the Seal components connect.

The Seal Platform is the hub. Every other component either communicates with the platform or carries data toward it.

The Seal CLI runs in your CI/CD pipeline or on a developer laptop. It pulls sealed packages from the Seal Artifact Server when applying fixes, reports discovered packages and fix results back to the platform, and (when configured) calls the APIs of your internal SCA scanners (Snyk, Black Duck, GitHub Advanced Security, Ox Security) to inform them which vulnerabilities have been remediated in which packages, so the scanners' dashboards stay accurate.

Your browser loads the Seal UI, which is a single-page application that talks to the platform.

The Seal GitHub App lives in GitHub. It reads your dependency manifests there, reports findings to the platform, and opens automatic pull requests when configured. GitLab and Azure DevOps integrations exist; they read manifests through the source control system's own API rather than via a hosted app, and they do not open pull requests.

The Seal AI Agent and the Seal Engineer are two Seal Platform features. The Seal AI Agent is the chatbot in the Seal UI: you talk to it. The Seal Engineer runs flows on a schedule and posts results back to a Slack channel; the Slack workspace install lives inside the Seal Engineer configuration. You schedule the Seal Engineer. The Seal AI Agent does not connect to Slack.

External tooling integrates programmatically through the Seal Public API.