Platform ops
Running the gateway well after go-live: upgrades, ownership, capacity, and the observability that tells you why something broke.
Senior Staff Field Engineer at Kong Professional Services, Netherlands
Notes, tools and fixes from real enterprise gateway projects. Most of what I write here started as a problem a customer and I had to solve.

01 / About
I’m a Senior Staff Field Engineer in Kong’s Professional Services team, based in the Netherlands. I work with the teams that run API platforms inside large companies: banks, insurers, retailers, pharma. Some are putting Kong into production for the first time, some are moving from a self-managed setup to Konnect, and more and more of them want to know how to let AI agents use their APIs safely.
I started on API platforms in 2014 with Apigee at Zensar. After that I spent six years at Devoteam as an API management architect, helping energy companies, LeasePlan and IKEA choose and run platforms on Apigee, 3scale, Mashery and MuleSoft. I joined Kong in 2023. The products changed; the problems mostly didn’t.
Whatever the project, the goal is the same: get the customer live, help them see real value from the platform and scale it, and most of all leave them able to run it themselves.
I like to be hands-on. A typical engagement is a few weeks with a platform team: design sessions, building the first pipeline together, a production readiness review before go-live. When the same problem shows up on two projects, I try to turn the fix into a tool, a checklist or a write-up. Some of those tools are now used by other engineers at Kong, which is the part I’m proudest of.
When something is broken in the product, I’d rather fix it upstream than work around it.
02 / Focus
Running the gateway well after go-live: upgrades, ownership, capacity, and the observability that tells you why something broke.
Identity with OIDC and mTLS, rate limits and quotas, and routing rules that keep one noisy consumer from hurting everyone else.
Gateway config in git, checked in CI and applied by a pipeline, so a change to a route doesn't need a ticket or a meeting.
Hardening before go-live: configuration review, failure testing, certificates, and a checklist the team can own.
Token budgets, model fallback, MCP and per-tool authorization: running LLM and agent traffic safely. That includes exposing existing REST APIs or MCP servers to agents with proper security, token management, and insight into access and cost.
03 / Selected work
fix(konnect): register the new certificate before retiring the old one
New data plane pods could pick up a renewed certificate before Konnect trusted it, and every request to the control plane failed with a 401. I changed the order: register the certificate first, roll it out second.
Metrics, logs and traces from a Konnect hybrid gateway, wired into Prometheus, Loki and Tempo on a local kind cluster with one command.
Written during a Kong 2.8 to 3.4 upgrade, when I had to test the same config against several decK versions. It installs and switches between them.
Smaller upstream contributions: kongctl lint docs on developer.konghq.com and environment variable tokens for Kong/kwot.
04 / Field notes
05 / Experience
MSc Information Technology, DA‑IICT (2008)
BCA Computer Science, Gujarat University (2006)
English, Hindi, Gujarati
Meetup talks, podcasts and conversations about API and AI platforms