Tarantool Lifecycle policy

Tarantool is tracked by BlackTree as a database platform or data-management product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Evidence status

This record passed BlackTree's automatic primary-source checks with a confidence score of 82. It is returned for operational research without requiring routine manual approval. Confirm edition and deployment applicability before acting.

This discovery does not establish a product-specific support or retirement date. A missing date does not mean support continues.

Product overview

Main capabilities

Persistent data storage
Application data querying and management
Backup, security and operational administration

Typical use

Used as an application data store, analytical platform or managed data service.

Deployment

Operated on servers, virtual machines, containers or a vendor-managed cloud service.

This category-level context is generated from the registered product identity. Confirm exact product capabilities on the publisher's page .

Collected lifecycle data

Product	Tarantool
Release	Lifecycle policy
Start or release	Not extracted
Lifecycle boundary	Continuous or not dated in the source
Date precision	Unknown

Known exploited vulnerabilities

Catalogue updated 1 Oct 2026

These are product-family matches in the CISA Known Exploited Vulnerabilities catalogue. Confirm the affected product version in the vendor advisory.

No CISA known-exploited entries currently match this mapped product family.

This does not mean the product has no vulnerabilities.

Package vulnerability advisories

OSV advisories are matched through the registered package URL. A package-family match does not prove that the installed release is affected. Check the affected and fixed versions before remediation.

No package advisories have been linked for this product identity.

This is not evidence that the product has no vulnerabilities.

Source evidence

PRIMARYManual

Tarantool official lifecycle source

Alpha version has some of the features planned in the release series. It can be incomplete or unstable, and can break the backwards compatibility with the previous release series. | Alpha versions are published for early adopters and developers of dependent components, such as connectors and modules. | Beta version has all the features which are planned for the release series. It is a good choice to start developing a new application. | Readiness of a feature can be checked in a beta version to decide whether to remove the feature, finish it later, or replace it with something else. A beta version can still have a known bug in the new functionality, or a known degradation since the previous release series that affects a common use case. | Note that the development of 2.10.0 , the first release under the new policy, starts with version 2.10.0-beta1 . | Release candidate is used to fix bugs, mature the functionality, and collect feedback before an upcoming release. Release candidate has the same feature set as the preceding beta version and doesn’t have known bugs in typical usage scenarios or degradations from the previous release series. | Release candidate is a good choice to set up a staging server.

Publisher identity used by product-specific official-source collectors.

First collected 12 Sep 2026 · Last collected 27 Sep 2026 · Review state accepted

Open official vendor source