- 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
- Atoti Engine — a given minor version is supported for 2 years following the General Availability (GA) of the next minor version. Example: if Atoti Java SDK 6.2.0 is released on 2026-07-01, the EOS Date for Atoti Java SDK 6.1.X will be 2028-06-30.
- Atoti UI – as above
- Atoti Intelligence – as above
- Atoti Solutions — a given minor version is supported for 2 years following the General Availability (GA) of the next minor version. Unless the underlying Atoti Engine or Atoti UI dependency becomes EOS before that date, in which case the EOS Date of that minor release will be the same as the EOS for the underlying Atoti Engine or Atoti UI dependency. Example: if Atoti FRTB 6.1.0 is released on 2026-09-01, the (theoretical) EOS Date for Atoti FRTB 6.0.X would be 2028-08-31. However, because the underlying dependency is Atoti Java SDK 6.1.X, the EOS Date will actually be 2028-06-30.
- Atoti Server & Java API
- Atoti Python SDK
- Atoti Admin UI
- Atoti UI & JavaScript API
- Atoti Limits
- Atoti Sign-Off
- Atoti Market Risk
- Atoti FRTB
- Atoti CVA Risk Capital
- Atoti Market Data
- Atoti Datastore Helper
- Atoti 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.| Before EOS date | After EOS date | ||
| Standard support | Extended support | ||
| Consideration of feature requests | Yes | No | |
| Resolution of Priority 1 Errors | Yes | Yes1 | |
| Resolution of other Errors | Yes | No | |