> 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/developer.md).

# If you're a developer

This guide is for developers who interact with Seal as part of their day job: integrating the Seal CLI into a CI/CD pipeline, creating or applying Sealing Rules for the codebases you own, and reading Seal's output in your build logs.

## Where to start

* [Your first Proof of Value](/getting-started/proof-of-value.md): an end-to-end walkthrough you can run in an afternoon.
* [Seal Apps via the Seal CLI in CI/CD](/setup-apps-os/cli-in-cicd.md): the integration step by step.
* [Sealing Rules](/using-platform/sealing-rules.md): the model and the UI flow. Sealing Rules are used in CLI deployments; they do not apply to artifact-server or manual-download deployments.
* [The Protection page](/discovering/protection-page.md): where you check on what is pending action for the Seal Projects you own.
* [The CLI reference](/reference/cli.md): commands, flags, and the `.seal-actions.yml` schema.

<figure><img src="/files/sCnfxJ7yywepgkkp0Q6f" alt="Seal CLI scan and fix output in a terminal"><figcaption><p>The Seal CLI output developers see in CI logs.</p></figcaption></figure>