API gateways occupy an awkward place in most engineering organisations. Everybody agrees they are necessary once you have more than a handful of services, nobody quite agrees what belongs inside one, and the result is usually a gateway configuration that has accumulated authentication, rate limiting, request transformation, routing, observability hooks and a few pieces of business logic that should never have gone there. Kong Academy is Kong's attempt to teach people how to run its gateway properly, and judged on that narrow goal it does well. The platform sits at education.konghq.com and is free to register for.
The foundational courses cover Kong Gateway itself, the Konnect hosted control plane, plugin architecture, and increasingly the AI gateway features that route and govern traffic to language model providers. That last category is the reason this academy is worth attention beyond the API crowd. The problem of putting a control layer between your applications and a set of model providers, with rate limiting, key management, cost attribution, prompt logging and failover, is a real operational problem that a lot of teams are solving badly with bespoke code right now. Kong has product opinions about it and teaches them clearly.
The certification design is the part I rate most highly. Kong runs two Associate credentials, one for Kong Gateway and one for Konnect, and the exams are booked through TrueAbility, which runs performance-based testing rather than multiple choice. You are given an environment and asked to make it behave a certain way. This matters more than it sounds.
The dominant model in vendor certification is a timed question bank, which rewards memorising configuration flags and punishes nothing, and produces credential holders who have never actually stood the product up. A hands-on exam produces a different kind of pass. It is slower to build, more expensive to run and much harder to cheat, and the fact that Kong chose it says something about how seriously the credential is meant to be taken. The complaint is the pricing opacity.
Kong's certification pages describe the exams, point you to the scheduling platform and do not state a price anywhere on Kong's own domain. You discover the cost when you arrive at checkout on a third party site. This is a small thing and a slightly irritating one, and it puts Kong in the same bracket as Optimizely and Dynatrace, vendors who will happily describe the value of a credential without telling you what it costs. Publishing the number would take one line of HTML.
The structural gap is the one every vendor academy has, and Kong's version of it is specific. An API gateway is a piece of infrastructure that is genuinely useful at a certain scale and genuinely harmful below it. A team with six services and one deployment target does not need a gateway, it needs a load balancer and some discipline about authentication. A team that adopts a gateway too early ends up with a second system to operate, a new single point of failure and a strong temptation to migrate cross-cutting logic into a place where it is hard to test.
None of that is in the curriculum, and it could not be. Kong is structurally the wrong party to teach you restraint about deploying Kong, in the same way a paging vendor cannot teach you to page less. Go elsewhere for the architecture decision and come here once you have made it. Also worth noting that the two-tier certification ladder stops early.
Both credentials are Associate level. There is no professional or architect tier, which limits how much career signal the badge carries after your first year with the product. Kong has talked about developer, operator and architect certification tracks, and if those materialise the programme gets considerably more interesting. Four point zero.
Free training, portable badges, a genuinely hands-on exam design that most vendors avoid, current material on the AI gateway problem, undercut slightly by hidden pricing and a credential ladder that ends before it gets to the level most hiring managers care about.