> For the complete documentation index, see [llms.txt](https://sestra.gitbook.io/sestra-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sestra.gitbook.io/sestra-whitepaper/integrations-and-lifecycle/integrations.md).

# Integrations

### Integration for Developers

Developers integrate Sestra at the API boundary. They:

* protect endpoints
* rely on Sestra to decide access
* do not manage user accounts

Integration focuses on:

* checking session validity
* responding to access decisions

***

### Integration for Product Teams

Product teams use Sestra to define access rules. They:

* decide what conditions are required
* decide how long access lasts
* define usage limits

Product logic stays separate from access control.

***

### Integration for Enterprises

Enterprises use Sestra to:

* reduce identity handling
* minimize compliance scope
* simplify audits

Sestra allows enterprises to adopt modern access models without restructuring existing systems.

***

### Integration for Other Projects

Other projects can build on Sestra by:

* treating it as an access layer
* defining custom verification logic
* integrating via standard APIs

Sestra does not lock projects into a specific technology.