> For the complete documentation index, see [llms.txt](https://docs.algenta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algenta.ai/trust-and-security/support-policy.md). # Support policy What support and long-term-support commitments exist today, and what is explicitly pending an owner decision rather than invented ahead of it. ## What's real today Security fixes land on `main` and in the latest published release of every artifact (API/worker/engine images, the Python and TypeScript SDKs, and `algenta-mcp`) — see [SECURITY.md](https://github.com/thyn-ai/algenta/blob/main/SECURITY.md) for the acknowledgement and triage timeline that already applies to every report, on every edition, today. Community, Pro, Team, and Enterprise are real, shipping license editions with real capacity caps — see [Licensing & editions](/deploy-and-operate/licensing.md). That page is the source of truth for what each edition unlocks; this page is only about support and lifecycle commitments layered on top of it. ## What is not published yet A per-edition support-tier matrix (response-time targets, support channels, escalation paths mapped to Community/Pro/Team/Enterprise) and a formal long-term-support window (which releases get security backports, and for how long) do not exist yet. Both require an owner sign-off before they're published, because a support commitment is a promise made to every customer who reads it, not an engineering estimate — inventing numbers here would be worse than the gap itself. The proposal on the table — not yet approved, stated here only so it's visible rather than hidden — is **latest-plus-previous** as the LTS window: security backports to the current release and the one before it, on Enterprise. Treat this as a proposal until this page says otherwise. ## What changes when this is signed off This page will be updated, in the same change that ships the decision, with: * A support-tier table mapped to license edition (channel, initial-response target, escalation path). * A published LTS window and what "backport" means in practice for this project's rolling-release model (see [SECURITY.md](https://github.com/thyn-ai/algenta/blob/main/SECURITY.md#supported-versions) for how versions are supported today, absent a formal window). * Whether an SLA is contractual (Enterprise) versus best-effort (Community/Pro/Team). Until then, do not read a specific number — hours, days, a version count — into this page or into any material built from it. [Capability status](/trust-and-security/capability-status.md) points back here rather than restating a number that doesn't exist yet. ## Next steps * [Licensing & editions](/deploy-and-operate/licensing.md) * [Trust overview](/trust-and-security/overview.md) * [Security questionnaire](/trust-and-security/security-questionnaire.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.algenta.ai/trust-and-security/support-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.