Skip to content

Product Life Cycle

This page defines OpenCTI’s product life cycle, including version numbering, Long-Term Support (LTS) program, dependency management, and breaking change policies.

Understanding these policies will help you plan deployments, manage upgrades, and maintain a stable OpenCTI environment.

Version Numbering Scheme

OpenCTI has adopted a date-based versioning scheme that reflects our continuous delivery model. Releases are published when ready, ensuring that critical fixes and improvements reach users without unnecessary delays.

Version Format

Version Format Description
x.dddddd.z Non-LTS version
x = major version number
dddddd = release date (YYMMDD)
z = sequential number for same-day releases (including LTS releases)
x.dddddd.z-lts(.n) LTS version
x = major version number
dddddd = LTS branching date (YYMMDD)
z = sequential number for same-day releases (including non-LTS releases)
n = sequential hotfix number (starts at 1)

Version Examples

Non-LTS versions:

  • 7.260112.0 — Release from January 12, 2026, major version 7
  • 7.260112.1 — Second release on the same day
  • 7.260315.0 — Release from March 15, 2026, major version 7

LTS versions:

  • 7.260201.0-lts — LTS branched February 1, 2026, released March 1, 2026
  • 7.260201.0-lts.1 — First hotfix for the 7.260201-lts release
  • 7.260201.0-lts.2 — Second hotfix for the 7.260201-lts release

Release Frequency

Non-LTS releases are delivered when ready, which can range from daily to weekly depending on the urgency of fixes, new features, and quality assurance requirements. This flexible approach ensures:

  • Critical security fixes reach users as quickly as possible
  • Bug fixes are not artificially delayed by release schedules
  • New features become available to users continuously

Long-Term Support (LTS) Program

The LTS program provides a stable, predictable release path for organizations that require rigorous testing, validation, and deployment processes. LTS releases evolve slowly and receive only critical & security fixes, ensuring minimal disruption to production environments.

Why LTS ?

Many organizations operate within strict internal processes for testing, validation, deployment, and maintenance. These cycles can be lengthy, making it impossible to upgrade to every new version of OpenCTI. The LTS program addresses these challenges by providing:

  • A stable release line that evolves more slowly
  • Updates limited to critical fixes (major bugs and security fixes only)
  • A clear time window during which the release remains supported
  • Predictable upgrade cadence aligned with operational constraints

Important

LTS is not a mandatory path. It is an option for organizations that prefer stability over rapid adoption of new features. Organizations comfortable with frequent updates may continue using non-LTS releases to access the latest capabilities.

LTS Program Characteristics ?

Release Cadence:

  • LTS releases occur every 6 months
  • Each LTS version is supported for 1 year from its release date
  • This provides a 6-month overlap window to prepare and test migration to the next LTS

Stabilization Period:

  • Each LTS release is stabilized for 1 month before being published
  • This ensures reliability and reduces post-release issues

Update Policy:

  • LTS updates are limited to critical bug fixes or security fixes
  • No new features are added to LTS versions
  • Hotfixes are released on an as-needed basis

What qualifies as a critical or major bug?

A bug is considered critical if it renders a feature unusable from a user standpoint. This includes:

  • Complete failure of a core feature or workflow
  • Data loss or corruption issues
  • Significant performance degradation that blocks normal operations
  • Regressions

LTS Release Timeline Example

The following timeline illustrates how an LTS release progresses from branching through end of life:

Date Event
Feb 1, 2026. 7.260201.0-lts branched from latest release
Feb 1 - Mar 1 1-month stabilization period
Mar 1, 2026 7.260201.0-lts officially released
Aug 1, 2026 Next LTS (7.260801.0-lts) branched
Sep 1, 2026 7.260801.0-lts released (6-month overlap begins)
Mar 1, 2027 7.260201.0-lts reaches End of Life (EOL)

Key Insight: Overlap Window

The 6-month overlap between consecutive LTS releases (September 2026 to March 2027 in this example) gives organizations ample time to validate the new LTS version while the previous version remains fully supported.

Choosing Between LTS and Non-LTS Release

Selecting the right release path depends on your organization’s operational model, risk tolerance, and resource availability.

When to Use LTS

LTS is recommended if your organization:

  • Requires extensive internal testing and validation before deploying updates
  • Operates in regulated industries with strict change management processes
  • Prefers predictable, infrequent upgrades over continuous updates
  • Values minimal functional changes in production environments
  • Has limited resources to manage frequent version updates

When to Use Non-LTS

Non-LTS releases are recommended if your organization:

  • Values access to the latest features and improvements
  • Can deploy and test updates frequently
  • Prefers receiving bug fixes and enhancements as soon as they’re available
  • Has a flexible change management process
  • Operates in a development or testing environment

How to Access LTS Releases

LTS releases are distributed as container images like for regular release. However, LTS releases requires a specific LTS license key to effectively use OpenCTI.

To activate LTS for your organization:

  1. Contact your Account Executive or Customer Success Manager
  2. Request an LTS license for your deployment
  3. Receive your license key and deployment instructions
  4. Configure your deployment with the provided license key