End-of-life & lifecycle policy
You should know how long the release you deploy stays supported, and how much warning you get before it doesn't. Here is the cadence, the support window, and the per-version table.
Infrastructure outlives feature cycles. The policy below sets a predictable security-patch window per release and a generous notice period before any version reaches end of life, so a version upgrade is something you schedule — not something forced on you by a surprise cutoff.
Policy
Policy
- Release cadence: Minor releases every 3 months; patch releases as needed for security and high-severity defects.
- Support window: Each minor release receives security and critical-defect patches for 12 months from GA.
- EOL notice: End-of-life is announced at least 3 months in advance via the changelog and customer email.
- Post-EOL behaviour: Post-EOL versions receive no further patches. Air-gapped customers may continue to operate post-EOL versions but lose new feature delivery; security advisories are still published.
Versions
Versions
Per-version GA and end-of-life dates are finalized against the release-history record before launch and will be published here. The policy above — the support window and notice period — applies to every release regardless of its exact dates.
Air-gapped customers. Customers operating on air-gapped networks may continue to run post-EOL versions. We deliver security patches as signed offline packages on request through your support channel; new feature delivery ends at EOL.
Keep reading
Related
Last reviewed: 2026-06-07.
Planning an upgrade?
Tell us the version you run today and we'll map your support window and EOL date.