Lifecycle and End-of-Life Policy

1. Purpose

Technology changes continuously. This policy explains how elyXion handles supported versions, feature change, deprecation, retirement, and end-of-life across its own services and third-party dependencies.

2. Lifecycle Stages

Stage	Meaning
Preview	Evaluation feature; may change, lack SLA, and not be suitable for production
General Availability	Supported production capability within the purchased service
Maintenance	Stable capability receiving fixes or security updates; limited enhancement
Deprecated	Still available temporarily, but replacement or migration is recommended
End of Support	Standard support ends; assistance may be best effort or separately charged
Retired	Feature or service is removed or disabled

 

3. elyXion Services

elyXion may evolve features to improve security, reliability, usability, compliance, or vendor compatibility. For a material retirement, elyXion aims to provide at least [NOTICE PERIOD] notice and reasonable migration guidance. Shorter notice may be necessary for security, law, provider action, or circumstances outside control.

4. Third-party Lifecycle

Microsoft, GitHub, HashiCorp, operating-system, open-source, and other provider lifecycles may determine elyXion support. elyXion cannot extend a provider’s support or prevent breaking changes. Customer plans should fund upgrades and migrations.

5. Security Exceptions

elyXion may disable vulnerable protocols, cipher suites, integrations, credentials, or features with accelerated notice if continued operation creates material risk. Where practicable, an alternative will be offered.

6. Customer-managed Systems

Customers are responsible for approving and funding lifecycle work for their systems. elyXion will identify known end-of-life risk within scope and may refuse unsafe changes or limit support for unsupported technology.

7. Data Portability

Before retirement of an elyXion-hosted material feature, elyXion will describe available export options where applicable. Exports may exclude derived telemetry, internal security data, licensed third-party content, and elyXion intellectual property.

8. Portal changes

Portal interface, reports, dashboards, APIs, and integrations may evolve. elyXion will seek to avoid unnecessary breaking changes. Published APIs, if any, may use versioning and sunset dates.

9. Preview Services

Preview services may be suspended or withdrawn at any time, may process data differently, and should not host critical or regulated workloads unless specifically approved. Feedback is welcome but roadmap commitments are not created by preview access.

10. Extended Support

Where technically and legally feasible, elyXion may offer temporary extended support under a separate SOW. It may include higher fees, reduced commitments, compensating controls, and a mandatory migration plan.