> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/setup-apps-os.md).

# Application and OS setup

This section covers the day-1 mechanics for the two Seal products that work at the **dependency layer**: **Seal Apps** (your application's open-source dependencies) and **Seal OS** (OS-level packages and language runtimes). Both products work by sealing packages *inside* a build, in contrast to the container-layer products covered under [Container and image setup](/setup-containers.md).

## What's in this section

* [Choosing your deployment method](/setup-apps-os/choosing-deployment-method.md): the decision page comparing the five deployment methods (Remote, Local, Automatic Remediation, Artifact Server, Manual).
* [Seal Apps via the Seal CLI in CI/CD](/setup-apps-os/cli-in-cicd.md): the recommended deployment — installing the CLI, fix modes, per-CI-system integration, Dockerfile patterns, local development.
* [Seal Apps via the Seal Artifact Server](/setup-apps-os/artifact-server.md): pointing your package manager at the Seal Artifact Server as a remote.
* [Seal OS in CI/CD](/setup-apps-os/seal-os-cicd.md): the `seal fix --os` command, sealing OS packages in a Dockerfile, container build pipelines.
* [On-prem and air-gapped environments](/setup-apps-os/on-prem.md): hosting patterns when neither the Seal CLI nor the artifact server can reach the public internet.