End of Life (EOL) / End of Support (EOS) Policy
Our EOL (End of Life) and EOS (End of Support) policies ensure stability, transparency, and long-term reliability
Backward Compatibility and Versioning We maintain backward compatibility across product versions to minimize disruption. Versioning is managed carefully so existing integrations and workflows continue to operate without modification.
Deprecation Policy When a feature or API is marked for deprecation, we will provide a minimum of 12 months’ advance notice before it reaches End of Life (EOL). During this period, both old and new versions will remain supported to allow sufficient time for migration.
End of Life (EOL) EOL indicates that a product, feature, or API will no longer receive new enhancements or functionality after the announced date. However, it will continue to operate and remain supported until the EOS date.
End of Support (EOS) EOS marks the date when technical support, maintenance, and security updates will end. After this date, deprecated components may still function but will no longer receive fixes or compatibility updates.
Communication and Notice All EOL and EOS announcements will be shared at least 12 months in advance through official communication channels such as release notes, customer notifications, and documentation updates.
Updated 2 days ago