description Kong Gateway (Self-Managed) Overview
Focusing specifically on the self-managed, open-source version of Kong, this is the choice for teams prioritizing complete control over their infrastructure. It allows deep customization of plugins and traffic flow without relying on cloud vendor abstractions, making it perfect for highly regulated or specialized on-premise deployments.
help Kong Gateway (Self-Managed) FAQ
Can Kong Gateway run without PostgreSQL?
Yes, self-managed Kong Gateway supports DB-less operation using declarative configuration loaded into each node's memory. Plugins that require shared database state, such as some cluster-wide rate-limiting modes, cannot provide their full behavior in that topology.
What is the difference between traditional and hybrid mode in Kong Gateway?
Traditional mode gives gateway nodes direct access to the configuration database. Hybrid mode separates database-backed control-plane nodes from DB-less data-plane nodes that serve API traffic.
Can I write my own plugins for self-managed Kong?
Yes, Kong supports custom plugins for authentication, request transformation, logging, traffic control, and other gateway stages. In hybrid mode, the same custom plugin code must be installed on both the control plane and every data plane that uses it.
What do I lose by choosing open-source Kong Gateway instead of Enterprise or Konnect?
The open-source edition provides the core reverse proxy, routing, and community plugins but omits commercial capabilities such as Enterprise workspaces, advanced role-based administration, and official support. Konnect also removes much of the work of operating the control plane yourself.
explore Explore More
Similar to Kong Gateway (Self-Managed)
See all arrow_forwardReviews & Comments
Write a Review
Be the first to review
Share your thoughts with the community and help others make better decisions.