Senior Staff Field Engineer · Kong · Netherlands
Hi, I'm
Kuldeep Bhati.
I help enterprises run APIs and AI agents in production.
I work with the platform teams inside banks, insurers and retailers, taking Kong Gateway, Konnect and AI Gateway to production. Twelve years on API platforms, and now the AI agents that use them.
Most of what I write here started as a problem a customer and I had to solve, and some of it ended up as an upstream fix to Kong.

- Platforms
- Kong Gateway
- Konnect
- AI Gateway
- Apigee
- MuleSoft
- 3scale
- Mashery
- Focus now
- AI Gateway 2.x
- MCP gateways
- Governance as code
- Konnect migrations
Latest writing
All posts- 01 Kong AI Gateway governance as code: lint checks before go-liveMCP tool access, logged prompts, literal secrets: governance gaps visible in the YAML. A kongctl lint ruleset for Kong AI Gateway catches them before apply.
- 02 From plugin to entities: local Ollama behind Kong AI Gateway 2.xThe same local Ollama model from the last post, now behind Kong AI Gateway 2.x on Konnect: a provider, a model and an API key instead of plugin config.
- 03 Stop switching tool versions: pin every CLI per project with miseOne mise.toml pins decK, kongctl, kubectl, Helm and the rest of your toolbox per repo, with checksums, and CI reads the same file.