We're excited to announce that Kong is now working with [Cloudsmith](https://cloudsmith.com/)Cloudsmith to host our community edition and enterprise edition gateway packages. With new hosting comes a couple of changes to how you, our loyal customers, will be receiving our software.
A new repository layout emerges! We previously housed packages in per-gateway-major-version, and per-OS-version repositories ("gateway-3.x-ubuntu-jammy"). Cloudsmith lets us do away with that using their "multi-format" repositories feature. With multi-format repos, we can now house packages of several formats, for several OSs, in a single repo. So we've opted to go with per-gateway-major-minor-version repository names ("gateway-33" would house all gateway versions 3.3(.x(.x)) for all OSs). Pretty neat! We hope this simplifies the process of setting up repositories for our software.
Kong Gateway version 2.7 and older can be found in a new "gateway-legacy" repo that uses the old metadata signing key from our old site.
Let's face it, our old download site was a little . . . boring. Luckily, Cloudsmith offers us an antidote to that. Check out [](http://packages.konghq.com/)[http://packages.konghq.com/](http://packages.konghq.com/)http://packages.konghq.com/ in a web browser to peruse our package repositories, view/verify public keys, download single packages, search across all our packages using [Cloudsmith's query syntax](https://help.cloudsmith.io/docs/search-packages)Cloudsmith's query syntax, browse by tags, view package checksums, setup package repositories (via the "Set Me Up!" button), and more! Much less boring.
We expect this transition to benefit our customers in some other key ways as well:
When will the old download site be retired?
To make this transition as seamless as possible, the old download site will be around for at least another 6-months from this announcement per our deprecation policy.
For additional details, please refer to [our documentation](https://docs.konghq.com/gateway/latest/install/linux/ubuntu/#advanced-installation)our documentation.
Kong customers include some of the most forward-thinking, tech-savvy organizations in the world. And while we’re proud to help them innovate through traditional APIs, the reality is that their ambitions don’t stop there. Increasingly, our customers a
[](https://konghq.com/blog/product-releases/kong-event-gateway)
Agent-to-agent communication is the next frontier of AI infrastructure. As teams decompose monolithic AI workflows into specialized agents — a research agent, a booking agent, a summarization agent — the calls between those agents become as importa
[](https://konghq.com/blog/product-releases/kong-ai-gateway-3-14)
Managed Redis cache is a turnkey "Shared State" add-on for Kong Dedicated Cloud Gateways. It is designed to combine the performance of an in-memory data store with the simplicity of a SaaS product. When you spin up a Dedicated Cloud Gateway in Kong
[](https://konghq.com/blog/product-releases/multicloud-cloud-gateways-managed-redis-cache)
With Kong Ingress Controller, when your Control Plane was hosted in Kong Konnect, and you were using Kubernetes Gateway API, your dataplane, routes, and services were in read-only mode. When using Kong Ingress Controller with Kubernetes Gateway API
[](https://konghq.com/blog/product-releases/kong-operator-2-1)
The Kubernetes Gateway API represents a massive collaborative effort and key advancement in Kubernetes networking. Developed by multiple vendors and community members, the Gateway API provides a robust and extensible new standard for managing ingres
[](https://konghq.com/blog/engineering/kubernetes-gateway-api-engineering-perspective)
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)