# soc2doc

## Docs

- [Authentication](https://docs.soc2doc.ai/api/authentication.md): The authentication model for the soc2doc developer preview is not finalized, and no credentials are issued today.
- [API (developer preview)](https://docs.soc2doc.ai/api/introduction.md): soc2doc does not expose a public API yet. This section describes the intended direction without presenting any callable endpoints.
- [soc2doc docs](https://docs.soc2doc.ai/introduction.md): What soc2doc is, how the Commitment Review works, and how it fits alongside compliance-automation platforms.
- [After the review](https://docs.soc2doc.ai/product/after-the-review.md): How teams use the Commitment Review after delivery: assign owners, book a call, move into managed support, or run the work internally.
- [The Commitment Review](https://docs.soc2doc.ai/product/commitment-review.md): What a Commitment Review is: the commitments in your issued SOC 2 mirrored back in plain English, organized for ownership and follow-through.
- [Confidentiality](https://docs.soc2doc.ai/product/confidentiality.md): Who sees your report, in what order, and the controls around access, storage, retention, and deletion.
- [How it works](https://docs.soc2doc.ai/product/how-it-works.md): NDA first, then upload. AI extracts commitments; a practitioner verifies the work; your Commitment Review is delivered after review.
- [FAQ](https://docs.soc2doc.ai/why/faq.md): Common questions about the Commitment Review, confidentiality, deletion, assessors, platforms, and audit independence.
- [soc2doc vs Vanta, Drata, Sprinto](https://docs.soc2doc.ai/why/vs-vanta-drata-sprinto.md): How soc2doc differs from evidence-automation platforms and where it can work alongside them.
- [What soc2doc is](https://docs.soc2doc.ai/why/what-soc2doc-is.md): A practitioner-led SOC 2 support service for teams that need the work understood, owned, and carried through the year.