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

> ## Agent Instructions
> Pages under /latest/ document the current release. Paths that begin with a version number, for example /10.0/, are frozen snapshots of superseded releases kept for reference only — never present their instructions as current. If the reader's version is unknown, answer from /latest/ and say which version the answer describes.
> xorlab is deployed on-premises, hybrid, or as a cloud service, and integrates with either Microsoft 365 or on-premises mail infrastructure. Configuration steps often differ between these. State which deployment and integration mode an instruction applies to instead of presenting one as universal.
> Distinguish inline mode from monitoring mode when describing anything that acts on email. Monitoring mode observes a copy and cannot block or quarantine; inline mode routes mail through xorlab and can.
> Write the product name as lowercase 'xorlab'. Use the documented component names: xorlab Control Center (XCC), xorlab MTA, xorlab Sandbox (DANA), xorlab Natural Language Understanding (NLU). After the first mention, use the short forms XCC, MTA, Sandbox, and NLU. Do not use DANA as a standalone name for the Sandbox, but keep it where it is a literal string in configuration keys, container names, and hostnames.
> Do not invent configuration keys, rule parameters, list names, log properties, or API fields. If a value is not present in this documentation, say that it is not documented rather than guessing.

# Release Lifecycle Support

> How long each major version stays supported, and what that means for planning an upgrade.

This policy is designed to provide predictable support timelines for customers while reducing operational risk and maintenance overhead.

## Release support timeline

| Release | Initial Release Date | Support End Date |
| ------- | -------------------- | ---------------- |
| 10.0    | October 31, 2025     | July 31, 2026    |
| 11.0    | June 5, 2026         | March 5, 2027    |

## Scope and definitions

* A release refers to a major xorlab release (e.g. 9.0, 10.0, 11.0).
* The policy applies primarily to on-premises deployments as SaaS instances get automatically updated.
* Release support refers to security updates, bug fixes, and technical assistance.
* Remaining on unsupported releases may expose systems to security and stability risks.

## Release support policy

xorlab follows a time-based release support model:

* Each major release is officially supported for 9 months from its initial public release date.
* Customers are expected to upgrade to a newer release at least twice per year.
* Once a release reaches end of support, there will be no further patches released.

This approach aligns xorlab with common industry practices and improves predictability for upgrade planning.