LOCKEDIN / FORWARD-DEPLOYED ENGINEERING 101
Understand it.
Then build it.
You can be an experienced engineer and still be new to agents. Start with what each thing is and how it helps a person do useful work. Explore 48 original introductions across software, agents, cloud, security and delivery. Start here without a model key; each topic connects to deeper instruction and practice.
- 101UnderstandPlain language, visual walkthrough, vocabulary
- 102Build with guidanceOriginal lessons, examples and knowledge checks
- 103Practise and explainRunnable labs, failure cases and handover
- 01Inventory traffic
- 02Configure a route
- 03Test failure
An AI traffic gateway
What is Kong AI Gateway?
Kong AI Gateway provides gateway capabilities for AI traffic, including model, MCP and agent interfaces. It helps teams manage routing, access and observability across backends. Kong Gateway, its plugins and the Konnect management platform are related components with deployment and licensing choices.
FDEs may need a shared control point across providers or a customer's existing gateway estate.
CONNECT IT TO WHAT YOU KNOW
Start with something familiar.
Think of a configurable reverse proxy with AI-aware policies. It sits on the request path rather than inside the model's reasoning.
An API-compatible route does not make models behaviorally interchangeable. Check feature support, model semantics, data handling and licensing for the selected configuration.
Words worth knowing
- Reverse proxy
- A service that forwards client requests to backends.
- Plugin
- An extension that adds gateway behavior.
- Fallback
- An alternative path used under defined failure conditions.
ONE EXAMPLE / FICTIONAL CASE
Watch the work take shape.
A customer wants one governed route for approved model requests and separate controls for MCP tool traffic.
- 01Inventory traffic
- 02Configure a route
- 03Test failure
Inventory traffic
Separate model inference, tool calls and agent delegation; each has different permission and failure semantics.
A traffic mapFROM RECOGNITION TO REASONING
Compare APIM and Kong for one specific workload.
- 01
Use identity, deployment location, supported API and policy needs as comparison rows.
- 02
Mark unverified capabilities as unknown.
- 03
Write one case where a fallback must be refused.
A requirement-led comparison, not a vendor ranking.
Compare your reasoning when you are ready
A fallback to an unapproved data location is unacceptable even if it improves availability. Select the gateway by verified requirements rather than logo familiarity.
Keep notes in your own working copy. Moving through these cards does not record completion.
TURN THE IDEA INTO USEFUL WORK
You can now go deeper.
An API-compatible route does not make models behaviorally interchangeable. Check feature support, model semantics, data handling and licensing for the selected configuration.
Academy lessons use your existing training access. Free guides stay open.