The Kong Gateway 3.4 for Open Source (OSS) release is massive for our community users. Notably, this release introduces support for WebAssembly (Wasm), bringing a new level of extensibility and customization to Kong Gateway.
Read on to learn more about the new capabilities in Kong Gateway 3.4 for OSS.
We've been hard at work to add support for Wasm, and we're thrilled to deliver on this effort in Kong Gateway 3.4. Starting in 3.4 as a beta feature, all Kong Gateway users will be able to write Wasm filters in both Rust and Go, with *zero *external dependencies.
This is a massive win for customers who want to extend Kong Gateway in their preferred programming language. Over time we will add more language support for Wasm — with the ultimate goal of *any *developer being able to extend Kong Gateway in the language they're comfortable with. This means less specialized knowledge will be required to customize Kong Gateway capabilities over time — allowing users to get up and running faster, with the languages and tools they already know.
This demonstrates our commitment to embracing innovative technologies and our promise to make them accessible to our community. Stay tuned for an upcoming blog post on how you can get started with Wasm.
We welcome everyone to provide feedback on [Kong Nation](https://discuss.konghq.com/)Kong Nation and report any issues on [GitHub](https://github.com/kong/kong/issues)GitHub. Please note that for the duration of the Beta, we'll be using the [docs on the repo](https://github.com/Kong/ngx_wasm_module/tree/main/docs)docs on the repo as the reference documentation. When Wasm support is graduated to GA, we'll port them to our primary documentation site.
Don't want to use Wasm? No problem! The module is disabled by default. The Wasm module is *dynamic*: this means there's no additional memory dedicated to running Wasm with the module disabled.
TCP/UDP-based firewall rules represent some of the most common types of rules across the internet. The reason is simple: they can be very effective. If you're certain that an IP or CIDR space must be blocked, doing so at the TCP/UDP level is the quickest and cheapest way to do it.
Targeting lower-level protocols for deny/allow behavior means using fewer resources to reach that goal without unwrapping the packet for any higher-level information that could be harmful to your systems or target a vulnerability in a higher-level protocol.
Given the value provided by this capability, we're happy to announce that both TCP and UDP-based restrictions are now supported in the [IP Restriction plugin](https://docs.konghq.com/hub/kong-inc/ip-restriction/)IP Restriction plugin. This is in addition to the gRPC, gRPCS, http, and https restrictions you could already define.
For a full list of features, fixes, and updates, please see the available CHANGELOG Kong Gateway 3.4 for OSS [here](https://github.com/Kong/kong/blob/master/CHANGELOG.md#340)here. Download [Kong Gateway 3.4 for open source](https://konghq.com/install)Kong Gateway 3.4 for open source. Or [sign up for Kong Konnect](https://konghq.com/products/kong-konnect/register)sign up for Kong Konnect for free. It's the fastest way to experience Kong Gateway 3.4.
We're thrilled to announce the general availability of Kong Gateway 3.7 and Kong Gateway Enterprise 3.7. Along with enhancements and new features for both OSS and enterprise users, this version comes with the general availability of our edge AI Gate
[](https://konghq.com/blog/product-releases/kong-gateway-3-7)
As API usage and dependence continue to grow, the need for a reliable, performant, and secure API gateway has become even more essential. Kong Gateway Open Source continues to be the world’s most adopted API gateway, setting the benchmark for perfor
[](https://konghq.com/blog/product-releases/kong-gateway-3-3-open-source)
In the Kubernetes world, the Ingress API has been the longstanding staple for getting access to your Services from outside your cluster network. Ingress has served us well over the years and can be found present in several dozen different implementa
[](https://konghq.com/blog/engineering/gateway-api-from-early-years-to-ga)
🎂 Make a wish and blow out the candles…we're celebrating Kong's sixth anniversary! 👏👏👏 In 2015, Mashape open sourced Kong Gateway , launching the next generation of API management. In our last anniversary post, I took a look back at our histor
[](https://konghq.com/blog/news/kong-gateway-oss-turns-six)
Imagine you have a single Service, order-api . You want to apply a strict rate limit to most traffic, but you want to bypass that limit—or apply a different one—if the request contains a specific X-App-Priority: High header. Previously, you had t
[](https://konghq.com/blog/engineering/conditional-policy-execution)
How OAuth 2.0 Token Exchange Reshapes Trust Between Services — and Why the API Gateway Is Exactly the Right Place to Enforce It Modern applications don’t run as a single monolithic. They are composed of services — frontend APIs, backend microservi
[](https://konghq.com/blog/engineering/token-exchange-at-the-gateway)
Traditional APIs are, in a word, predictable. You know what you're getting: Compute costs that don't surprise you Traffic patterns that behave themselves Clean, well-defined request and response cycles AI APIs, especially anything that runs on LLMs
[](https://konghq.com/blog/engineering/monetize-ai-apis)