HeliosDB Release and Capability Matrix: Reference Terms
| Item | Detail |
|---|---|
| Document | Release and Capability Matrix reference terms |
| Version | 1.0 |
| Effective date | 2026-10-29 |
| Published by | Dimen Sigon OÜ, trading as HeliosDB, registry code 16757774, Ahtri 12, 10151 Tallinn, Estonia |
| Address of this document | https://partners.heliosdb.com/legal/release-capability-matrix |
Change log
| Version | Date | Change |
|---|---|---|
| 1.0 | 2026-10-29 | First published version. |
1. Purpose
1.1 HeliosDB publishes a Release and Capability Matrix (the "Matrix") that states, for each HeliosDB edition and version, what is released and supported. Contracts, orders, support and partner materials refer to the Matrix instead of repeating capability statements. This document explains how the Matrix is built, what its statuses mean, and how it binds HeliosDB.
1.2 The Matrix includes the HeliosDB Compatibility Matrix, which lists database engines, protocols and open-source drivers per edition, driver package and tested version.
2. Structure
2.1 The Matrix has one row per edition, capability and version. For the Compatibility Matrix a row is one edition, engine, driver package and tested version combination. Each row states, where relevant: the protocol or API version; the driver package name, language, upstream source and licence; the tested driver, runtime and HeliosDB versions; the date last tested; connection, authentication and TLS settings; supported operations; known limitations and workarounds; and the test evidence.
2.2 The Matrix is published in a readable form and in a machine-readable form. Each published version carries a version identifier and a date. A version that HeliosDB designates as frozen also carries the SHA-256 fingerprint of its machine-readable file and is never changed afterwards.
3. Statuses
3.1 Each row has one status. The statuses mean:
| Status | Meaning |
|---|---|
| tested-supported | Covered by HeliosDB's tests on the stated versions, and supported |
| supported-with-limitations | Supported within the documented limitations; operations outside them are not supported |
| production-use | Used by a real application in production, with evidence recorded by HeliosDB; supported within what that use exercises, which the row describes |
| not-tested | Implemented, but without current test evidence for the stated versions; not supported until tested |
| skeleton | The shipped server starts a listener that completes the handshake and authentication, but statements do not read or write HeliosDB data; not usable for real workloads |
| stub | Code for the engine exists, but the shipped server does not start it, or its entry points answer "not implemented"; not usable for real workloads |
| planned | No implementation in this edition; HeliosDB documentation lists it as planned; it may be built in the future without any commitment |
| absent | No implementation and no documented plan in this edition; the name appears only as a migration source or comparison |
| unsupported | Not supported |
3.2 Feature readiness is shown separately as generally released, preview, source-build-only or roadmap. A Generally Released version is one designated as generally released in the Matrix; preview, nightly, release-candidate and source-build-only versions are not Generally Released.
3.3 Operations are given their own status where they differ from the row, and operations that do not apply to an engine are marked as not applicable rather than implying support.
4. How the Matrix binds HeliosDB
4.1 Only rows with the status tested-supported, supported-with-limitations or production-use describe supported capability. Support under the HeliosDB Support Policy and the HeliosDB Transaction Durability Commitment applies only within those rows.
4.2 An order identifies the frozen Matrix version that applies to it. A later edit of the Matrix does not reduce what an order already identifies. Removing supported behaviour follows clause 5.
4.3 Driver compatibility does not mean complete feature parity with the original database engine, or compatibility with every application, extension or administrative tool. It does not imply any endorsement or certification by the owners of those engines or drivers.
4.4 Statements counting engines or drivers per edition are made only where the Matrix supports them, and only in the form the Matrix states.
4.5 Requested capabilities beyond the Matrix are handled through a scoped evaluation or a separate development order, not as support.
5. Changes and deprecation
5.1 HeliosDB gives at least 90 days' notice before removing a supported row or operation in a new version, except where a legal or security reason requires faster action; in that case it gives notice as soon as possible with a mitigation plan.
5.2 HeliosDB keeps the history of published Matrix versions and makes each frozen version available.
6. Release series and lifecycle
6.1 Where HeliosDB designates a supported release series for an edition, the Matrix states its first release date, the period for which security fixes will be provided and its end-of-support date. HeliosDB gives at least 90 days' notice before the end of support, with a commercially reasonable upgrade route.
7. Draft and frozen versions
7.1 The status of each Matrix version (draft or frozen) and of each release series is shown with the Matrix. A draft version is informational only: no order can rely on it, or on an engine or driver count derived from it, until HeliosDB freezes that version and an order identifies it.