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

# End of Support policy

> ActiveViam's support lifecycle policy for all of its Software. Version 3.0.0 – June 19, 2026.

This page defines ActiveViam's policy for the support lifecycle of all of its Software products.

“**End of Support Software**” refers to any release of Software that is an unsupported version, as defined in this End of Support Policy. Each version of the Software will have a date when that particular version is no longer supported (the “**EOS Date**”).

The following umbrella terms are used throughout this policy:

* **Atoti Engine** refers to: Atoti Python SDK, Atoti Java SDK and DirectQuery;
* **Atoti UI** refers to: Atoti UI including the Atoti JavaScript SDK;
* **Atoti Solutions** includes: Atoti Libraries and Tools, Atoti CVA Risk Capital, Atoti FRTB, Atoti ISDA-SIMM, and Atoti Market Risk;
* **Atoti Intelligence** includes: Atoti Intelligence, Atoti Limits, and Atoti Sign-Off.

## Release versioning

Software release version numbers follow this convention: `MAJOR.MINOR.MAINTENANCE`

For example, a release versioned `5.4.3` is under major version 5, minor version 5.4, and maintenance version 5.4.3.

Version digits are incremented as follows:

| Digit | When incremented |
| - | - |
| Major | Major rewrite with conceptual changes |
| Minor | New functionality with some incompatible API changes |
| Maintenance | New functionality and bug fixes that are backward compatible |

## Support periods

End of service for a given minor version depends on the release of the next minor version.
The EOS Date is not set at the version's own release, but 2 years after the **next** minor version reaches General Availability (GA).

*Example: Atoti Java SDK 6.3.X is released on 2027-07-01, so the EOS Date for Atoti Java SDK 6.2.X is 2029-06-30.*

* **Atoti Engine**: as above
* **Atoti UI**: as above
* **Atoti Intelligence**: as above
* **Atoti Solutions**: as above, unless the **underlying Atoti Engine or Atoti UI dependency** reaches its own EOS Date sooner, in which case that earlier date applies instead.

  *Example, for Atoti FRTB 6.0.X:*

  * *Theoretical date: Atoti FRTB 6.1.XX goes GA on 2026-09-01, so the EOS Date would be 2028-08-31 (2 years later).*
  * *Dependency check: Atoti FRTB 6.1.XX depends on Atoti Java SDK 6.2.YY, whose own EOS Date is 2028-06-30, which is earlier.*
  * *Actual date: the earlier dependency date applies, so the actual EOS Date for Atoti FRTB 6.1.XX is 2028-06-30.*

Fixes for confirmed bugs reported against a supported minor version will be delivered (in accordance with the relevant commercial agreement, and if technically feasible) via a new maintenance release. We strongly recommend reproducing bugs against the latest maintenance release before reporting them.

Refer to the respective product pages below for GA and End-of-Support dates per released version:

* [Atoti Server & Java API](/eos/atoti-server)
* [Atoti Python SDK](/eos/python-sdk)
* [Atoti Admin UI](/eos/admin-ui)
* [Atoti UI & JavaScript API](/eos/atoti-ui)
* [Atoti Limits](/eos/limits)
* [Atoti Sign-Off](/eos/signoff)
* [Atoti Market Risk](/eos/market-risk)
* [Atoti FRTB](/eos/frtb)
* [Atoti CVA Risk Capital](/eos/cva-risk-capital)
* [Atoti Market Data](/eos/market-data)
* [Atoti Datastore Helper](/eos/datastore-helper)
* [Atoti What-If](/eos/what-if)

## Extended support

A Client using End of Support Software must contract for Extended Support from the EOS Date, for an additional fee on top of the usual Software maintenance fee, unless there is a mutually agreed upgrade plan for the Client to move to supported Software. The fees for Extended Support are calculated as a percentage of the annual recurring revenue for the Software and increase for each release back that the Software is operating after the EOS Date.

<table>
  <tbody>
    <tr>
      <td rowSpan={2}>
        <strong />
      </td>

      <td style={{textAlign: "center"}}>Before EOS date</td>
      <td colSpan={2} style={{textAlign: "center"}}>After EOS date</td>
    </tr>

    <tr>
      <td style={{textAlign: "center"}}>Standard support</td>
      <td style={{textAlign: "center"}}>Extended support</td>
    </tr>

    <tr>
      <td>Consideration of feature requests</td>
      <td style={{textAlign: "center"}}>Yes</td>
      <td style={{textAlign: "center"}}>No</td>
    </tr>

    <tr>
      <td>Resolution of Priority 1 Errors</td>
      <td style={{textAlign: "center"}}>Yes</td>
      <td style={{textAlign: "center"}}>Yes<sup><a href="#fn-1">1</a></sup></td>
    </tr>

    <tr>
      <td>Resolution of other Errors</td>
      <td style={{textAlign: "center"}}>Yes</td>
      <td style={{textAlign: "center"}}>No</td>
    </tr>
  </tbody>
</table>

“**Priority 1 Error**” and “**Error**” are as defined in the ActiveViam support services policy.

<sup id="fn-1">1. Provided that the resolution is technically feasible in the minor version run by the Client.</sup>