> 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/introduction/audience-guides/devops-engineer.md).

# If you're a DevOps engineer

This guide is for DevOps engineers, DevSecOps engineers, and platform engineers operating Seal in your organization. You will own the deployment, the integrations between Seal and the rest of your stack, and the day-2 of the container-side products and Seal OS.

## Where to start

* [Choosing your deployment method](/setup-apps-os/choosing-deployment-method.md): pick the right path for your environment.
* [Seal Apps via the Seal CLI in CI/CD](/setup-apps-os/cli-in-cicd.md): the recommended deployment, step by step.
* [How Seal discovers your packages](/discovering/how-seal-discovers-your-packages.md): how Seal sees what you have, with or without source-control access.
* [Working with Seal Base Images](/using-platform/working-with-seal-base-images.md), [Seal My Container](/using-platform/working-with-seal-my-container.md), and [Seal Vendor Apps](/using-platform/working-with-seal-vendor-apps.md): day-2 for the container side.
* [Internal SCA scanners](/integrations/internal-scanners.md): connecting Seal to Snyk, Black Duck, GitHub Advanced Security, or Ox Security.
* [The Seal GitHub App](/integrations/github/github-app.md): more visibility into your codebase, with the option to open automatic pull requests for fixes.

<figure><img src="/files/UjOT4YFY2MigfJ8k4468" alt="The Projects page showing several Seal Projects"><figcaption><p>The Projects page, where DevOps engineers manage Seal Projects across the tenant.</p></figcaption></figure>