# How the pieces fit together

```mermaid
graph LR
    CI[Your CI/CD] --> CLI[Seal CLI]
    CLI --> AS[Seal Artifact Server]
    CLI <--> Plat[Seal Platform]
    CLI --> Scanner[Your SCA scanner]
    Browser[Your browser] --> UI[Seal UI]
    UI <--> Plat
    SCM[Source control] <--> Plat
    Slack[Your Slack] <--> Plat
    Clients[External clients] --> API[Seal Public API]
    API <--> Plat
```

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 (chat) reaches you through the Seal UI. The Seal Engineer (periodic AI workflows) posts to a configured Slack channel. Internally they share a common AI core and a single MCP interface to the Seal Platform; to the customer, they remain two distinct features with distinct entry points.

External tooling integrates programmatically through the Seal Public API, which is itself a thin layer over the platform.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sealsecurity.io/new-documentation/new-docs/architecture/how-pieces-fit-together.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.