Components

The named components that make up the Seal Platform.

Seal Platform

The backend that holds your tenant's state: discovered packages, vulnerabilities, Sealing Rules, Seal Projects, users, tokens, and the operational data that the UI and the CLI both work against.

Seal Artifact Server

The package registry that hosts every sealed package Seal has built. The Seal CLI fetches sealed packages from it, and customers can also configure their package managers to point at it directly.

Seal UI

The web application for viewing discovered packages, creating Sealing Rules, managing Seal Projects, configuring tenant settings, and operating the AI features.

Seal CLI

The command-line tool customers run to apply sealed packages or report on what is discovered. The recommended deployment is the CLI in your CI/CD pipeline; it also runs on developer laptops or anywhere with network access to the Seal Platform.

Seal Public API

The programmable REST API for integrating Seal with external tooling.

Seal MCP server

Seal's Model Context Protocol endpoint for AI clients. Open to any MCP-aware client, and exposes tools spanning the same areas as the Seal UI.

Seal GitHub App

The GitHub-hosted application that connects a customer's GitHub repositories to Seal. It reads dependency manifests, opens automatic pull requests for fixes, and reports findings back to the Seal Platform.

Seal GitHub Action

A wrapper around the Seal CLI that runs as a GitHub Actions step. Functionally equivalent to running the CLI directly; convenient for customers whose CI/CD is GitHub Actions.