Microgateway 5.1

Airlock Microgateway’s Community Edition has been repositioned to make Gateway API adoption as simple as possible. It now includes the Gateway API features without requiring a license and without throughput limitations. Selected Microgateway capabilities, such as globally configured custom responses and telemetry, are also included.

Teams that want to evaluate Microgateway's security features can request an evaluation licence.

For the Premium Edition, two additional licensing options are now available: Gateway API-only deployments without security features such as filtering or authentication enforcement, and authentication enforcement without filtering. The existing options for filtering only, as well as combined filtering and authentication enforcement, remain available. All Premium Edition options include first-class Airlock support.

Key benefits:

• Lower entry barrier:Teams can use Airlock Microgateway as a modern Gateway API-based ingress option without license handling or throughput restrictions.
• More tailored licensing: Customers can license the capabilities they need, whether for Gateway API-only deployments, authentication-focused use cases, filtering-focused use cases, or deployments that combine authentication and filtering.

With the retirement of Kubernetes Ingress NGINX, organizations need a sustainable migration path for existing ingress setups. Airlock Microgateway provides a Gateway API-based alternative and gives the community a free option to start that transition.

We extended the Gateway API support in Airlock Microgateway with ListenerSet and RegularExpression path matching in HTTPRoute.

ListenerSet allows additional listeners to be attached to a Gateway, making it easier for application teams to manage listener and TLS settings while avoiding the previous limitation of 64 listeners per Gateway.

Regex-based path matching enables more sophisticated routing rules for applications with complex URL structures.

Key benefits:

• More flexible ownership: Application teams can manage their own listener and TLS configuration without overloading a central Gateway resource.
• More powerful routing: HTTPRoutes can now use regular expressions to match paths that cannot be covered well with exact or prefix matching.

These extensions help teams model larger and more complex Kubernetes ingress setups with standard Gateway API resources.

Airlock Microgateway can now limit the number of requests forwarded to a backend within a defined time window. This helps protect applications and APIs from excessive request rates and reduces the impact of denial-of-service attempts.

Key benefits:

• Improved resilience: Helps keep backend services responsive during traffic spikes or abusive request patterns.
• Better resource control: Allows teams to define clear request thresholds and reduce the risk of unrestricted resource consumption.

Rate limiting is also recommended by OWASP as a measure to prevent unrestricted resource consumption in APIs.

This new release introduces numerous improvements for greater security, flexibility, and seamless integration. We look forward to your suggestions and feedback as we continue to improve Microgateway!