# 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://sestra.gitbook.io/sestra-whitepaper/integrations-and-lifecycle/integrations.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.