XaasIO Platform Releases
Software Lifecycle
Management
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.
Predictable releases. Governed platform evolution.
2
Scheduled platform releases
June and December
June and December
24
Months between Long-Term Support designations
YY.MM.N
Sequential maintenance updates within a release series
24
Platforms & modules under
one lifecycle framework
RELEASE INDEX
Released and Planned XaasIO Platform Series
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 |
|---|---|---|---|---|---|
| 25.12 XaasIO Platform | Valluvar | December 2025 | LTS | Released | Not yet announced |
| 26.06 XaasIO Platform | Nammalvar | June 2026 | Standard | Current release | Not yet announced |
| 26.12 XaasIO Platform | Ilango Adigal | December 2026 | Standard | Planned | Not yet announced |
| 27.06 XaasIO Platform | Sekkizhar | June 2027 | Standard | Planned | Not yet announced |
| 27.12 XaasIO Platform | Avvaiyar | December 2027 | LTS | Planned | Not yet announced |
Showing 5 of 5 release series.
| Release Series | Codename | Release Window | Type | Status | Support End |
|---|---|---|---|---|---|
| 25.12 XaasIO Platform | Valluvar | December 2025 | LTS | Released | Not yet announced |
| 26.06 XaasIO Platform | Nammalvar | June 2026 | Standard | Current release | Not yet announced |
Showing 2 of 5 release series.
| Release Series | Codename | Release Window | Type | Status | Support End |
|---|---|---|---|---|---|
| 25.12 XaasIO Platform | Valluvar | December 2025 | LTS | Released | Not yet announced |
| 27.12 XaasIO Platform | Avvaiyar | December 2027 | LTS | Planned | Not yet announced |
Showing 2 of 5 release series.
| Release Series | Codename | Release Window | Type | Status | Support End |
|---|---|---|---|---|---|
| 26.12 XaasIO Platform | Ilango Adigal | December 2026 | Standard | Planned | Not yet announced |
| 27.06 XaasIO Platform | Sekkizhar | June 2027 | Standard | Planned | Not yet announced |
| 27.12 XaasIO Platform | Avvaiyar | December 2027 | LTS | Planned | Not yet announced |
Showing 3 of 5 release series.
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 Records for the Released Baselines
Series identity and publication status for the released XaasIO Platform baselines.
XaasIO Platform · 26.06
Nammalvar
Release Window
June 2026
Position
Current release
Type
Standard
General Availability Date
Not yet published
Latest Maintenance Update
Not yet published
Support End and End of Life
Not yet announced
XaasIO Platform · 25.12
Valluvar
Release Window
December 2025
Position
LTS baseline
Type
LTS
General Availability Date
Not yet published
Latest Maintenance Update
Not yet published
Support End and End of Life
Not yet announced
RELEASE CADENCE AND TRACKS
Two Releases a Year. One LTS Designation Every 24 Months.
XaasIO follows a six-month release cycle: YY.06 in June and YY.12 in December. Every release belongs to one of two tracks, and maintenance updates are published within a release series using YY.MM.N.
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.
Cadence: June releases and the December releases between LTS designations
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.
Cadence: Every second December release, starting with 25.12. After 27.12, the next is 29.12
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.
VERSIONING AND UPDATES
A Release Identity with a Clear, Visible History
XaasIO release identifiers are calendar-based. Three parts tell you the year,
the month and the maintenance update.
the month and the maintenance update.
26.
YY · Release year
Two-digit release year. 26 = 2026.
06.
MM · Release month
06 = June. 12 = December.
1
N · Maintenance update
Sequential maintenance update.
1 = first, 2 = second.
1 = first, 2 = second.
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.
codename. Release notes identify each update’s prerequisites and whether it applies cumulatively or sequentially.
MAINTENANCE AND UPGRADES
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.
01
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.
02
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.
03
Apply and 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.
Platforms and modules
One Lifecycle Framework for 20 Platforms and 4 Modules
Every XaasIO platform and module follows the same release calendar, numbering and status terms. A shared release calendar does not mean every product ships in every series or supports every cross-product combination.
20 platforms
| No. | Platform | Technology or Scope | Lifecycle Scope |
|---|---|---|---|
| Platform 01 | XaasIO Compute Platform | OpenStack | Private-cloud compute, networking and infrastructure orchestration. |
| Platform 02 | XaasIO Virtualization Platform | KVM | Virtual-machine, host and cluster lifecycle management. |
| Platform 03 | XaasIO HCI Platform | Hyper-Converged Infrastructure | Integrated compute, storage and networking with coordinated cluster lifecycle management. |
| Platform 04 | XaasIO Kubernetes Platform | Kubernetes | Container orchestration and Kubernetes cluster lifecycle management. |
| Platform 05 | XaasIO SDS Platform | Ceph | Software-defined block, object and file storage. |
| Platform 06 | XaasIO RDS Platform | OpenEverest | Database provisioning and management on Kubernetes. |
| Platform 07 | XaasIO CMP Platform | Cloud Management Platform | Unified inventory, policy, approvals and infrastructure automation. |
| Platform 08 | XaasIO BSS and FinOps Platform | Business Support Systems and FinOps | Service catalog, metering, billing, cost allocation and cloud financial management. |
| Platform 09 | XaasIO Hyperscaler Platform | Hyperscaler Platform | Self-service cloud delivery, tenant services, metering and billing. |
| Platform 10 | XaasIO MLT Platform | Monitoring, Logging and Telemetry | Operational visibility across platform health, logs and telemetry. |
| Platform 11 | XaasIO AI-SRE Platform | AI-assisted Site Reliability Engineering | AI-assisted incident analysis, operational recommendations and human-governed remediation workflows. |
| Platform 12 | XaasIO AI Lake Platform | AI Lake | Governed data, lakehouse and enterprise-context foundations. |
| Platform 13 | XaasIO AI Token Factory | AI Token Factory | Governed and metered AI inference services. |
| Platform 14 | XaasIO AI Factory + HPC Platform | AI Factory + High-Performance Computing | Accelerated AI, scientific computing and high-performance workloads. |
| Platform 15 | XaasIO NFV Platform | Network Functions Virtualization | Virtualized network services and network-function lifecycle management. |
| Platform 16 | XaasIO Autonomous Defense Platform – Visai | Autonomous Defense | Human-governed security monitoring, threat detection and response orchestration. |
| Platform 17 | XaasIO DR and Replication Platform | Disaster Recovery and Replication | Replication, recovery orchestration and recovery planning. |
| Platform 18 | XaasIO Unified Automation Platform | Argo CD, Argo Events, Ansible AWX, Packer and OpenTofu | GitOps delivery, event-driven automation, configuration management, image builds and infrastructure as code. |
| Platform 19 | XaasIO Secure Communication and Collaboration Platform | Matrix homeserver and Jitsi | Self-hosted secure messaging, voice and video conferencing. |
| Platform 20 | XaasIO Secure Groupware Platform | SOGo | Self-hosted webmail, shared calendars and address books. |
4 Modules
| No. | Module | Technology or Scope | Lifecycle Scope |
|---|---|---|---|
| Module 01 | XaasIO IAM Module | Identity and Access Management | Identity, authentication and access-management integration. |
| Module 02 | XaasIO Directory Services Module | Directory Services | Centralized directory, user and group management, and identity integration. |
| Module 03 | XaasIO Backup Module | Backup and Recovery | Backup policy, scheduling, retention and restore management. |
| Module 04 | XaasIO VDI and PAM Module | Virtual Desktop Infrastructure and Privileged Access Management | Virtual desktop lifecycle management and governed privileged access to systems and sessions. |
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.
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 and 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.
SOVEREIGN OPERATIONS
Air-Gapped, Still Accountable
Platform-specific offline prerequisites, validated architecture and entitlement requirements belong in the
deployment and update documentation.
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 Covers the Complete Deployment
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
Images and charts
Identity and monitoring
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
Frequently asked questions
How often does XaasIO release new platform versions?
Twice a year. New XaasIO Platform release series arrive in June (YY.06) and December (YY.12). Maintenance updates are published
within a series as YY.MM.N, and security-driven updates may be issued between scheduled releases.
within a series as YY.MM.N, and security-driven updates may be issued between scheduled releases.
What is the current XaasIO Platform release?
26.06 — Nammalvar is the current release series. 25.12 — Valluvar is the current Long-Term Support baseline. 26.12 — Ilango
Adigal is the next planned series, targeted for December 2026.
Adigal is the next planned series, targeted for December 2026.
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.
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.
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.
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.
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.
are recorded per release.
Build what the world depends on
Planning a cloud for government, financial services, pharmaceuticals, healthcare, energy, transport, industry, service-provider operations, or private AI? Work with XaasIO to define the architecture, security boundary, and operating model your environment requires.