Keep track of your Protector software versioning
The mitigation of web security threats requires continuous innovation and improvement to stay ahead of threat actors. As a result, Akamai regularly releases new versions of the Protector software. These updates provide the best possible protection for your digital assets, preventing threat actors from creating counter solutions.
Versioning ensures clarity about which features, improvements, or fixes Akamai engineering team introduced in each Protector software release. In this chapter, we'll break down the versioning system used for Protector and explain why it matters to update your software and keep your protections up to date.
Supported versions
Akamai strongly recommends that you continuously upgrade your applications with new releases.
Note that Akamai’s software support policy applies to the latest three major or minor releases of the Protector software. It means that support is available for users on the current version of Protector and its two previous major or minor versions. After a new version is released, support for any earlier version (earlier than the last three major or minor releases) will be discontinued. This includes downgrades to any earlier versions than the last three supported releases. For example, if the current Protector software version is 1.7.0, support will be provided for versions 1.7.0, 1.6.0, and 1.5.0. Support will no longer be available for the Protector software version 1.4.0 or any earlier versions.
Our versioning format follows a three-digit system, structured as X.Y.Z:
- X (major version). This number is incremented when Akamai introduces large changes in the Protector software, such as new features or considerable upgrades that may alter the way the software operates.
- Y (minor version). The middle number is increased when new features or improvements are added, but Protector remains backward-compatible with its previous version. Minor updates may introduce enhancements or additional functionalities, without breaking the existing features.
- Z (patch version). It reflects bug fixes and minor adjustments. These are typically non-disruptive changes intended to correct issues or improve stability without altering the software’s core functionality. Patch updates ensure that the software continues to perform reliably, addressing small bugs and optimizing performance.
Note that if a major or minor version update occurs, it will also be documented in release notes (login required) so that you can understand the scope and impact of the changes.
The following table details all differences between the last three versions of the Protector software:
| Protector software version number | Type of update | Impact | Date |
|---|---|---|---|
| v1.2.0 | New features and enhancements | Protector v1.2.0 introduces Layer 7 rate limiting controls, DoS Trends dashboard, and expanded client IP header support. | December 8, 2025 |
| 1.1.2 | New deployment mode | Protector v1.1.2 introduces a new reverse proxy deployment mode (beta). You can now deploy App & API Protector Hybrid as a pre-configured VM image on AWS or on-premises via VMware ESXi. | October 29, 2025 |
| v1.1.1 | App & API Protector Hybrid launches in General Availability | New dashboards in Security Center: | July 21, 2025 |
| v1.1.0 | App & API Protector Hybrid launches in Limited Availability | Changes and new features: | April 11, 2025 |
| v1.0.1 | First public release of App & API Protector Hybrid in Beta | Protections include: | January 17, 2025 |
Updated 1 day ago