Loading…
Kong is an open-source, cloud-agnostic API gateway — and in its enterprise edition, a full API management platform. It is the right choice when:
- The organization needs to run the API gateway on-premises alongside existing data center infrastructure - The deployment spans multiple cloud providers and a platform-neutral gateway layer is required - The team is already running Kubernetes and wants a Kubernetes-native ingress controller that also serves as the API gateway - The API management requirements do not justify the cost and complexity of Apigee X - The organization wants an open-source core with the option to add enterprise capabilities incrementally
We evaluate Kong Gateway vs. Kong Konnect vs. Kubernetes Ingress Controller against the infrastructure context. Deployment model documented with rationale before any provisioning begins.
Kong deployed in the target environment — on-premises, Kubernetes cluster, or cloud VM — with database (PostgreSQL) or DB-less declarative configuration depending on the deployment model selected.
Plugins configured against the security, traffic control, and observability requirements defined in the integration architecture. Each plugin's configuration documented and version-controlled.
Bring us the constraint. We'll bring the team.
We do not position Kong as a fallback. We position it as the deliberate answer for the deployment scenarios where it outperforms managed cloud-native alternatives.
Kong can be deployed as Kong Gateway (open source or enterprise), Kong Konnect (managed SaaS control plane with self-managed data plane), or as the Kong Ingress Controller in Kubernetes. We design the deployment model against the organization's infrastructure and operational requirements — not a default that requires rework later.
Kong's extensibility comes from its plugin architecture. We configure plugins covering: authentication (JWT, OAuth 2.0, API key, basic auth, LDAP), security (bot detection, IP restriction, CORS), traffic control (rate limiting, request size limiting, proxy caching), transformations (request and response modification), and observability (logging, Prometheus metrics, HTTP log to SIEM). Every plugin is configured with production-appropriate settings — not out-of-box defaults.
Services (upstream backends) and routes (incoming request matching rules) configured with upstream health checks, load balancing policies, and connection pool settings appropriate for each backend's capacity and latency profile.
For Kubernetes-based deployments, Kong Ingress Controller configuration: IngressClass, KongPlugin custom resources, TLS termination, and certificate management via cert-manager integration.
Prometheus and Grafana integration for real-time gateway metrics. Alert policies for error rate thresholds, latency spikes, and upstream health status. Operational runbooks for common procedures: plugin updates, certificate rotation, upstream reconfiguration.
Services and routes configured for each API in scope, with upstream health checks validated and load balancing policy confirmed against backend capacity.
Prometheus metrics scraping configured, Grafana dashboards built, alert policies set, and operational runbooks delivered. Knowledge transfer to the team managing Kong post-deployment.