Welcome to the official documentation for Kong Mesh!
Kong Mesh is an enterprise-grade service mesh that runs on
both Kubernetes and VMs on any cloud. Built on top of CNCF’s
Kuma and Envoy and focused on simplicity,
Kong Mesh enables the microservices transformation with:
Kong Mesh extends Kuma and Envoy with enterprise features and
support, while providing native integration with
Kong Gateway (Enterprise) for a
full-stack connectivity platform for all of your services and APIs, across
every cloud and environment.
Kong Mesh provides a unique combination of strengths and
features in the service mesh ecosystem, specifically designed for the enterprise
When used in combination with Kong Gateway (Enterprise), Kong Mesh
provides a full stack connectivity platform for all of our L4-L7 connectivity,
for both edge and internal API traffic.
Organizations are transitioning to distributed software architectures to
support and accelerate innovation, gain digital revenue, and reduce costs.
A successful transition to microservices requires many pieces to fall into
place: that services are connected reliably with minimal latency,
that they are protected with end-to-end security, that they are discoverable
and fully observable. However, this presents challenges due to the need to
write custom code for security and identity, a lack of granular telemetry,
and insufficient traffic management capabilities, especially as the number of
Leading organizations are looking to service meshes to address these challenges
in a scalable and standardized way. With a service mesh, you can:
Kong Mesh is the universal service mesh for enterprise
organizations focused on simplicity and scalability with Kuma and Envoy.
Kong’s service mesh is unique in that it allows you to:
Thanks to the underlying Kuma runtime, with Kong Mesh, you
can easily support multiple clusters, clouds, and architectures using the
multi-zone capability that ships out of the box. This — combined with
multi-mesh support — lets you create a service mesh powered by an Envoy proxy
for the entire organization in just a few steps. You can do this for both
simple and distributed deployments, including multi-cloud, multi-cluster, and
Learn more about the
standalone and multi-zone deployment modes in the Kuma documentation.