Skip to main content

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.

This page defines ActiveViam’s policy for the support lifecycle of all its commercial products. The following umbrella terms are used throughout this document:
  • Atoti Core Platform refers to: Atoti Server, Atoti Java API, Atoti Python API, Atoti UI, Atoti JS API, and Atoti DirectQuery.
  • Business Solutions refers to: Atoti Collateral Optimization, Atoti CVA Risk Capital, Atoti FRTB, Atoti ISDA-SIMM, and Atoti Market Risk.
  • Business Modules refers to: Atoti Limits, Atoti Market Data, 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:
DigitWhen incremented
MajorMajor rewrite with conceptual changes
MinorNew functionality with some incompatible API changes
MaintenanceNew functionality and bug fixes that are backward compatible

​
Support periods

  • Atoti Core Platform — a given minor version is supported for 2 years following the General Availability (GA) of the next minor version. Example: if Atoti Python API 4.1.0 is released on 2028-03-01, the EOS for Atoti Python API 4.0 will be 2030-02-28.
  • Business Solutions and Business Modules — a given minor version is supported for 2 years following its own General Availability (GA). Example: if Atoti FRTB 9.3.0 is released on 2028-06-12, the EOS for Atoti FRTB 9.3 will be 2030-06-11.
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.

​
Extended support

A customer may contract for an Extended Support option for a predefined period after the EOS date, for an additional fee on top of the usual software maintenance fee.
All cases in the table below require the customer to be current on the annual maintenance fee. Under these circumstances, the customer always has access to the support ticket management system (Jira), product documentation, and the latest product releases.
For a given minor version of a given product…Before EOS dateAfter EOS date
Standard supportExtended supportNo extended support
Consideration of feature requestsYesNoNo
Resolution of critical1 bugsYesYes2No
Resolution of non-critical bugsYesNoNo
1. ‘Critical’ here is defined as per commercial agreement but typically means: an error causing serious disruption, degradation or failure of the Software.
2. IF resolution is technically feasible in the minor version run by the customer.