PLACEHOLDERThis table is not yet in force
Every row below is marked PLACEHOLDER. The rows show the shape of the table and the columns we are required to publish; they carry no version number, no release date and no end-of-support date. Nothing on this page is a binding publication of an end-of-support date, and nothing on it binds us or entitles anyone to rely on a date.
- No end-of-support date has been set for any Verisa version. When a version is released we set its end-of-support date at release and publish it here at the same time.
- No end of sale, end of support or end of life has been announced for any product or module.
- Until every placeholder row is replaced with real data this page is served with a noindex instruction, so that a search engine cannot present a draft table as a published one.
- Table version
- 0.1 — draft, no date in force
- Valid from
- 2026-08-12
- Superseded versions
- Every superseded state of this table is preserved in the version history of the content file behind it.
Per-version end of support
A version's end-of-support date is the day we stop issuing bug fixes and security fixes for that version. We set it when the version is released and publish it with the release. It is never earlier than 36 months from the release date, and once published it is never brought forward.
Per-version end of support for Verisa products. Dates are written as ISO 8601 calendar dates and are not reformatted per language.| Version | Release date | General availability end | End of support | Status | Note |
|---|
| Verisa AI — first supported releasePLACEHOLDER | YYYY-MM-DD | YYYY-MM-DD | YYYY-MM-DD | Not yet published | Row shape only. The release date and the end-of-support date are determined at release and published with it; until then there is no date to publish. |
|---|
| Verisa Flow — first supported releasePLACEHOLDER | YYYY-MM-DD | YYYY-MM-DD | YYYY-MM-DD | Not yet published | Row shape only. A general availability end may precede the end of support: a version can stop being shipped to new deployments while it still receives fixes. |
|---|
| Voice Intelligence module — first supported releasePLACEHOLDER | YYYY-MM-DD | YYYY-MM-DD | YYYY-MM-DD | Not yet published | Row shape only. A module carries its own per-version dates even where it ships inside a platform release. |
|---|
The table scrolls sideways on narrow screens.
Product and module lifecycle
End of sale, end of support and end of life apply to a whole product or module, and follow a procedure separate from the per-version dates above. We give at least 12 months' written notice of an end of sale, and at least 24 months' written notice of an end of support or an end of life. The notice names the affected product, the dates, the support tail period, the successor product and the migration path.
Product-level and module-level lifecycle dates for Verisa products, with the support tail period and migration path that accompany each announcement.| Product / module | End of sale (EOS) | End of support (EOSup) | End of life (EOL) | Support tail period | Successor | Migration path |
|---|
| Verisa AIPLACEHOLDER | None announced | None announced | None announced | Stated in the notice | Stated in the notice | Row shape only. An end of sale does not touch a licence already acquired, a confirmed order or a support period already under way. |
|---|
| Verisa FlowPLACEHOLDER | None announced | None announced | None announced | Stated in the notice | Stated in the notice | Row shape only. End of life is the later of end of sale and end of support for the same product. |
|---|
| Voice Intelligence modulePLACEHOLDER | None announced | None announced | None announced | Stated in the notice | Stated in the notice | Row shape only. A module can reach end of life while the platform it ships with continues. |
|---|
The table scrolls sideways on narrow screens.
How this table binds us
PLACEHOLDER While a row on this page is marked PLACEHOLDER, that row is not a binding publication of an end-of-support date. It states no date, it binds nobody, and no end-of-support date has been set for the version it stands for.
This table is binding. The per-version end-of-support date shown here is the date we set and published when that version was released. It is never earlier than 36 months from the release date, and once published it may be moved later but never brought forward. Each row is versioned and superseded states are retained, so the content of this table on any past date can be reconstructed.
Publication does not replace notice. We send a separate written notice to the reseller at least 180 calendar days before each end-of-support date, stating the affected version, the target version required, the prerequisites for migration and the known compatibility impact. That notice is the contractual one. This page is a reference: consulting it neither starts nor shortens the 180-day period, and end of support for a whole product or module follows the separate end-of-support procedure, not this table.
Publication does not alter live commitments. Withdrawing a product or announcing an end date applies to future orders only. It does not unilaterally alter a confirmed order, a delivery committed in writing for a public procurement, or a support period already under way.
The Hungarian text of the reseller framework agreement governs. This translation is provided for information; in the event of divergence the Hungarian text prevails.