> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enclave.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Enclave in these docs is the code and cloud security platform at enclave.ai. It is not Open Enclave, Intel SGX or other hardware enclaves, or enclave.gg.
> People use Enclave in the web app at https://app.enclave.ai or the desktop app. These docs describe no public Enclave API or CLI, so don't invent endpoints, commands, or config files.
> Connecting an integration needs a person to sign in and approve access in a browser. Tell the user the exact step to take instead of saying you completed it.

# What is Enclave?

> Find the security issues an attacker can actually exploit across your code and cloud, with evidence for every one.

Enclave connects to your source code and cloud and builds a working model of how they fit together. It uses that model to find vulnerabilities, then checks whether each one can really be reached and exploited in your environment.

Every finding comes with proof: the attack path, the affected files and assets, the impact, and a proof of concept where one applies. Your team spends its time fixing real risk instead of triaging alerts that never mattered.

![The Research home page in Enclave](https://mintcdn.com/enclave/bhnFMg4ldiTYrwZX/images/product/research-home.png?fit=max\&auto=format\&n=bhnFMg4ldiTYrwZX\&q=85\&s=ddaf41d07bddf26fe3826dd018f74142)

## What Enclave is good at

* **Finding what an attacker can reach.** Enclave checks every finding against your real environment, so you fix the issues that are exploitable before the ones that only look severe.
* **Following risk across services.** Enclave traces paths through code, cloud resources, and identities, which surfaces attack chains that no single scanner sees on its own.
* **Proving each finding.** Every result includes the attack path, the affected files and assets, the impact, and a proof of concept where one applies, so you can verify it yourself instead of taking it on trust.
* **Answering questions about your environment.** You can ask about your code, cloud, findings, and CVEs in plain language and get answers grounded in your own setup.
* **Running the same analysis again and again.** Workflows repeat an analysis on events or a schedule, so coverage keeps up as your code and cloud change.

## Get started

> [card] [Quickstart](https://docs.enclave.ai/quickstart.md)
>
> Sign up and get your first answer.

> [card] [Research](https://docs.enclave.ai/research/sessions.md)
>
> Ask about your code, cloud, findings, and CVEs.

> [card] [Risk](https://docs.enclave.ai/risk/findings.md)
>
> Review and triage verified findings.

> [card] [Workflows](https://docs.enclave.ai/workflows/overview.md)
>
> Run the same analysis on events or a schedule.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.