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

# Open Source

> The gateway and verification tooling are open source, and the attestation report ties production back to a specific source commit.

The platform's privacy claims are designed to be checked against source, not taken on trust. The gateway
is open source, and its [attestation report](/confidential-ai/attestation-report) records the exact
source commit the running workload was built from.

## Source provenance in the report

Every attestation report includes `attestation.source_provenance`:

```json theme={null}
{
  "repo_url": "https://github.com/Dstack-TEE/private-ai-gateway.git",
  "repo_commit": "9d45c7e3d48d2f74c31cd85f1fb5c6cee1435ef3",
  "image_digest": null,
  "image_provenance": null
}
```

This is what makes "verify the running code" concrete: the report names the repository and commit the
attested workload was built from. To audit a deployment, review that commit and compare it against the
release you are willing to trust.

## Repositories

<CardGroup cols={2}>
  <Card title="private-ai-gateway" icon="server" href="https://github.com/Dstack-TEE/private-ai-gateway">
    The Attested Confidential Inference gateway: the API surface, attestation reports,
    receipts, and provider verification.
  </Card>

  <Card title="dstack" icon="cube" href="https://github.com/Dstack-TEE/dstack">
    The dstack TEE runtime and KMS the gateway uses for workload identity and quotes.
  </Card>

  <Card title="RedPill on GitHub" icon="github" href="https://github.com/redpill-ai">
    The organization, clients, and tooling.
  </Card>
</CardGroup>

## What you can check from source

* **Attestation handling.** How the gateway builds the report, binds the nonce and keyset into the
  quote, and endorses its signing keys.
* **Provider verification.** How each confidential provider is verified and which
  [channel binding](/confidential-ai/channel-binding) is enforced before forwarding.
* **Receipts.** How the [transparency event log](/confidential-ai/receipts) is built and signed, and
  that bodies are hashed, not stored.
* **Fail-closed forwarding.** That a required upstream which cannot be verified or bound is rejected.

## Reporting a vulnerability

Report security issues privately to [support@redpill.ai](mailto:support@redpill.ai) rather than in a
public issue. Include reproduction steps.

## Next

<CardGroup cols={2}>
  <Card title="Attestation report" icon="microchip" href="/confidential-ai/attestation-report" />

  <Card title="Verify a response" icon="circle-check" href="/guides/verify-a-response" />
</CardGroup>