I will troubleshoot, secure, and extend your kong API gateway
Kong Gateway, Keycloak and API Security Consultant
About this Gig
Need expert help with Kong Gateway OSS, Keycloak/OIDC, custom plugins, or a migration decision?
I provide independent, vendor-neutral technical support for Kong Gateway deployments across Docker, Kubernetes/KIC, DB-less, PostgreSQL, Helm, decK, and cloud environments.
I can help with:
Troubleshooting routes, upstreams, plugins, TLS, performance, and deployment failures
Kong OSS + Keycloak using OIDC, JWT/JWKS, claims, roles, or token introspection
Migration assessment from Kong to Tyk, Envoy Gateway, Traefik, NGINX, or another gateway
Clean-room custom Kong OSS plugins for authentication, authorization, mTLS, transformations, and external policy integrations
Upgrade planning, hardening, observability, configuration drift, and rollback design
Deliverables may include root-cause findings, updated configuration or source code, reproducible tests, deployment instructions, and rollback guidance.
Custom security capabilities are independently implemented using open standards. They are not Kong Enterprise plugins and are not affiliated with Kong Inc.
Please contact me before ordering production migrations, mTLS, multi-IdP, FAPI, or complex custom plugin work.
Tools:
Docker
•
GitHub
•
Hashicorp Vault
•
Kubernetes
Frameworks:
Terraform
•
Ansible
Programming language:
Bash
•
JavaScript
•
Lua
•
Python
•
Golang
Expertise:
Migration
•
Debugging
•
Development
FAQ
Do you support Kong Gateway OSS 3.9?
Yes. I can troubleshoot and harden Kong OSS 3.9 deployments, assess lifecycle risks, and plan migration to Enterprise, Konnect, or another gateway.
Can you integrate Keycloak without the Enterprise OIDC plugin?
Yes. Depending on your flow, I can use JWT/JWKS, token introspection, or an independently developed standards-based custom plugin.
Can you build a Kong Enterprise plugin?
Yes. I build clean-room alternatives based on open standards and Kong's public PDK. Scope and compatibility are agreed before development.
What do you need before starting?
Your Kong version and topology, sanitized config, relevant logs, expected behavior, environment details, and a reproducible request if available.
