Skip to main content
  • XaasIO Platform Releases

Software

Lifecycle

Management

Predictable releases. Governed platform evolution.
Plan deployments, track release series and manage platform updates with a consistent lifecycle across the XaasIO portfolio. New platform releases arrive in June and December, with Long-Term Support designations every 24 months.

2

Scheduled platform releases
June and December

24

Months between
LTS designations

.N

Sequential maintenance
updates

21

Platforms & modules One lifecycle framework
Release index

The system is

always in motion.

Browse the released and planned XaasIO Platform series. Release months identify the scheduled release window;
exact release dates and platform-specific deliverables belong in the individual release record.

Release Series Codename Release Window Type Status Support End
Release Series
26.06
XaasIO Platform
 CodenameNammalvar Release WindowJune 2026 TypeStandard StatusCurrent release Support EndNot announced
Release Series 25.12
XaasIO Platform
 CodenameValluvar Release WindowDecember 2025 TypeLTS StatusReleased Support EndNot announced
Release Series 26.12
XaasIO Platform
 CodenameIlango Adigal Release WindowDecember 2026 TypeStandard StatusPlanned Support EndNot announced
Release Series 27.06
XaasIO Platform
 CodenameSekkezhhar Release WindowJune 2027 TypeStandard StatusPlanned Support EndNot announced
Release Series 27.12
XaasIO Platform
 CodenameAvvaiyar Release WindowDecember 2027 TypeLTS StatusPlanned Support EndNot announced
Planned releases are calendar targets, not availability commitments. A new release does not, by itself, end support for an earlier LTS release.
Support end dates have not yet been announced in this index.
Release Series Codename Release Window Type Status Support End
Release Series
26.06
XaasIO Platform
 CodenameNammalvar Release WindowJune 2026 TypeStandard StatusCurrent release Support EndNot announced
Release Series 25.12
XaasIO Platform
 CodenameValluvar Release WindowDecember 2025 TypeLTS StatusReleased Support EndNot announced
Planned releases are calendar targets, not availability commitments. A new release does not, by itself, end support for an earlier LTS release.
Support end dates have not yet been announced in this index.
Release Series Codename Release Window Type Status Support End
Release Series 25.12
XaasIO Platform
 CodenameValluvar Release WindowDecember 2025 TypeLTS StatusReleased Support EndNot announced
Release Series 27.12
XaasIO Platform
 CodenameAvvaiyar Release WindowDecember 2027 TypeLTS StatusPlanned Support EndNot announced
Planned releases are calendar targets, not availability commitments. A new release does not, by itself, end support for an earlier LTS release.
Support end dates have not yet been announced in this index.
Release Series Codename Release Window Type Status Support End
Release Series 26.12
XaasIO Platform
 CodenameIlango Adigal Release WindowDecember 2026 TypeStandard StatusPlanned Support EndNot announced
Release Series 27.06
XaasIO Platform
 CodenameSekkezhhar Release WindowJune 2027 TypeStandard StatusPlanned Support EndNot announced
Release Series 27.12
XaasIO Platform
 CodenameAvvaiyar Release WindowDecember 2027 TypeLTS StatusPlanned Support EndNot announced
Planned releases are calendar targets, not availability commitments. A new release does not, by itself, end support for an earlier LTS release.
Support end dates have not yet been announced in this index.
Release cadence

Every six months,

The system moves

Browse the released and planned XaasIO Platform series. Release months identify the scheduled release window; Exact release dates and platform-specific deliverables belong in the individual release record.

June and December

XaasIO follows a six-month release cycle: YY.06 in June and YY.12 in December. Maintenance updates are published within a release series using YY.MM.N.

LTS every 24 months

Starting with 25.12 — Valluvar, every second December release is designated as an LTS. The next LTS series is 27.12 — Avvaiyar, followed by 29.12 under the same cadence.
Versioning and updates

A release identity

with a clear visible history.

26 .

YY / Year
2026

06 .

MM / Month

June or
December

1

N / Update
Sequential number

Part Details Example
YY Two-digit release year 26 = 2026
MM Release month 06 = June · 12 = December
N Sequential maintenance update 1 = first · 2 = second

XaasIO release identifiers are calendar-based: 26.06 identifies the June 2026 series, and 26.06.1 identifies a maintenance update within it, retaining the series codename. Release notes identify each update’s prerequisites and whether it applies cumulatively or sequentially.

XaasIO ≠ upstream

A XaasIO identifier does not imply a specific OpenStack, Ceph, OpenEverest, operating-system or other upstream version.

Manifests map the detail

The release manifest maps deliverables to exact upstream baselines and dependencies.
Platforms and modules

A release identity

with a clear visible history.

17 platforms and 4 modules. A shared release calendar does not mean every product ships in every series or supports every cross-product combination.

Platform or module Technology / scope Lifecycle scope
XaasIO Compute PlatformPlatform 01 OpenStack Private-cloud compute, networking and infrastructure orchestration.
XaasIO Virtualization PlatformPlatform 02 KVM Virtual-machine, host and cluster lifecycle management.
XaasIO HCI PlatformPlatform 03 Hyper-Converged Infrastructure Integrated compute, storage and networking with coordinated cluster lifecycle management.
XaasIO Kubernetes PlatformPlatform 04 Kubernetes Container orchestration and Kubernetes cluster lifecycle management.
XaasIO SDS PlatformPlatform 05 Ceph Software-defined block, object and file storage.
XaasIO RDS PlatformPlatform 06 OpenEverest Database provisioning and management on Kubernetes.
XaasIO CMP PlatformPlatform 07 Cloud Management Platform Unified inventory, policy, approvals and infrastructure automation.
XaasIO BSS and FinOps PlatformPlatform 08 Business Support Systems & FinOps Service catalog, metering, billing, cost allocation and cloud financial management.
XaasIO Hyperscaler PlatformPlatform 09 Hyperscaler Platform Self-service cloud delivery, tenant services, metering and billing.
XaasIO MLT PlatformPlatform 10 Monitoring, Logging & Telemetry Operational visibility across platform health, logs and telemetry.
XaasIO AI-SRE PlatformPlatform 11 AI-assisted Site Reliability Engineering AI-assisted incident analysis, operational recommendations and human-governed remediation workflows.
XaasIO AI Lake PlatformPlatform 12 AI Lake Governed data, lakehouse and enterprise-context foundations.
XaasIO AI Token FactoryPlatform 13 AI Token Factory Governed and metered AI inference services.
XaasIO AI Factory + HPC PlatformPlatform 14 AI Factory + High-Performance Computing Accelerated AI, scientific computing and high-performance workloads.
XaasIO NFV PlatformPlatform 15 Network Functions Virtualization Virtualized network services and network-function lifecycle management.
XaasIO Autonomous Defense Platform – VisaiPlatform 16 Autonomous Defense Human-governed security monitoring, threat detection and response orchestration.
XaasIO DR and Replication PlatformPlatform 17 Disaster Recovery and Replication Replication, recovery orchestration and recovery planning.
XaasIO IAM ModuleModule 01 Identity and Access Management Identity, authentication and access-management integration.
XaasIO Directory Services ModuleModule 02 Directory Services Centralized directory, user and group management, and identity integration.
XaasIO Backup ModuleModule 03 Backup and Recovery Backup policy, scheduling, retention and restore management.
XaasIO VDI and PAM ModuleModule 04 Virtual Desktop Infrastructure & Privileged Access Management Virtual desktop lifecycle management and governed privileged access to systems and sessions.

Release tracks

Standard and

LTS are not promises.

Standard releases

The regular six-month delivery point for validated platform evolution. June releases and the December releases between LTS designations belong to this track. 26.06 — Nammalvar is the current standard release.

Long-Term Support releases

A designated long-term baseline for deployments that require longer planning horizons and controlled platform changes. 25.12 — Valluvar is the current LTS baseline; 27.12 — Avvaiyar is the next planned LTS.

Support duration is a separate policy. Do not interpret “LTS every 24 months” as “24 months of support.” The support term, maintenance scope and end-of-life date are published per platform and release, separately from release naming.

Release status terminology
Planned The series is on the calendar; its date, scope or codename may still change.
In development Engineering and validation are in progress; the series is not generally available.
Released The series has been published and its release record identifies available deliverables.
Maintained Updates are provided within the published platform-specific support scope and term.
End of life Standard maintenance for the specified platform release has ended; separately contracted services must be confirmed explicitly.

The Release tracks

Maintenance, security and upgrades

Maintenance updates address approved fixes, security corrections, and validated compatibility changes. Security-driven updates may be issued between scheduled platform releases — a June or December window is not a reason to defer a required security response.

Assess

Confirm current state

Confirm the deployed series, platform versions, dependencies, and available updates. Review release notes, known issues, security advisories, and the applicable support record.

Validate

Test the change

Use the approved compatibility matrix and upgrade guide. Test backups and recovery procedures, verify capacity and service health, and validate the change in a test environment.

Apply & verify

Promote and confirm

Promote the approved release through controlled repositories, execute the documented procedure, and verify platform health, data integrity and service behavior. Retain change records.

Only documented, validated upgrade paths are supported. LTS does not imply a direct 25.12 → 27.12 upgrade. Intermediate upgrades or migrations may be required. Downtime, rolling-upgrade support and rollback or restore procedures are release-specific.

Production adoption follows validated baselines, not an automatic move to the newest upstream version. Where an N-1 deployment policy applies, security, dependency support and compatibility requirements take precedence over mechanically remaining one version behind.

Supply chain

Software supply chain and release evidence

Release evidence identifies the software delivered, its upstream origins and how to verify the artifacts. Consult the release record for the evidence and formats available per platform. 

Upstream
SBOM

An inventory of the selected upstream components and dependencies, preserving their native version and license information.

XaasIO release
SBOM

An inventory of the XaasIO-delivered software, including packaged components, dependencies and applicable XaasIO changes.

Artifact verification & provenance

Release records associate delivered packages, images and charts with checksums or digests, signature-verification information and build provenance.

Governed release promotion

Release preparation follows code review, security checks, controlled builds, testing, approval and publication, aligned to SOC 2 engineering controls.

Soverign operations

Air-gapped

still accountable.

Platform-specific offline prerequisites, validated architecture and entitlement requirements belong in the deployment and update documentation.

Controlled updates inside your security boundary.

Local execution · Governed change

Validated air-gapped deployments use approved offline bundles and local repositories or registries. Verify signatures and checksums, stage all required dependencies, perform the approved maintenance procedure and retain local audit records.

Offline readiness is assessed for the complete deployment: operating systems, packages, images, charts, identity, monitoring and any AI model or accelerator dependencies.
  • Operating systems and packages
  • Identity and monitoring
  • Images and charts
  • AI model or accelerator dependencies

AI-assisted Day-2 operations remain human-governed. Production changes require appropriate authorization, controlled execution, and an auditable change record.

Clarifications

Frequently asked questions

Is every December release an LTS release?
No. LTS designation occurs every 24 months. With 25.12 as the anchor, 27.12 is the next LTS; 26.12 is a standard release.
Does LTS mean 24 months of support?
No. Twenty-four months is the interval between LTS designations. The support duration and end-of-life date are separate, platform-specific policy fields.
Is 26.06.1 the current release?
26.06 is the current release series. 26.06.1 illustrates the numbering of its first maintenance update; availability must be confirmed in published release notes.
Can I upgrade directly between LTS releases?
Only when the applicable platform upgrade guide explicitly validates that path. Intermediate upgrades or migrations may be required.
Do XaasIO release numbers identify the upstream version?
No. XaasIO release numbers identify a XaasIO release series. Exact upstream component versions are recorded separately in the release manifest and SBOMs.
Does a common release number guarantee cross-platform compatibility?
No. Use the validated platform compatibility matrix. Product availability, dependency versions and supported combinations are recorded per release.

Get in Touch with Our Architecture & Success Team

Evaluate a VMware Exit, scope a hyperscaler repatriation plan, or launch a managed OpenStack/Kubernetes/Data/AI platform.
We’ll propose a practical path to production with clear milestones and managed service options.
Schedule Meeting