# The Seal product family

Seal has five products that together cover your stack. They all use the same underlying [sealing approach](/new-documentation/new-docs/seal-approach.md): a sealed package replaces a vulnerable origin version without changing your code. They differ in **what** they secure and in **how** the fix reaches your environment.

| Product                                                                                  | What it secures                                                                                               | Delivery                                                                               |
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| [**Seal Apps**](/new-documentation/new-docs/product-family/seal-apps.md)                 | Application open-source dependencies (npm, pip, Maven, Gradle, ...)                                           | Sealed dependencies pulled in during your CI/CD build, or via the Seal Artifact Server |
| [**Seal OS**](/new-documentation/new-docs/product-family/seal-os.md)                     | OS-level packages and language runtimes on Linux servers and in containers, including EOL distributions       | Sealed packages installed by the Seal CLI, in place                                    |
| [**Seal Base Images**](/new-documentation/new-docs/product-family/seal-base-images.md)   | OS-level packages and language runtimes inside container base images                                          | Clean base image, pulled from a Seal-hosted registry                                   |
| [**Seal My Container**](/new-documentation/new-docs/product-family/seal-my-container.md) | OS-level packages, language runtimes, and embedded open-source artifacts inside your private container images | Sealed copy of your container image, pushed back to your registry                      |
| [**Seal Vendor Apps**](/new-documentation/new-docs/product-family/seal-vendor-apps.md)   | OS-level packages, language runtimes, and embedded open-source artifacts inside vendor-supplied containers    | Seal CLI applies fixes in place inside the vendor's container in your environment      |

The pages below cover each product in turn. For day-1 setup, see [Application and OS setup](https://github.com/seal-community/gitbook/blob/main/new-docs/setup-apps-os/README.md) or [Container and image setup](https://github.com/seal-community/gitbook/blob/main/new-docs/setup-images-containers/README.md). For the day-to-day operating view, see [Using the Seal Platform](https://github.com/seal-community/gitbook/blob/main/new-docs/using-platform/README.md).


---

# 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/product-family.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.