Why Ambassador?

Ambassador is a Kubernetes-native microservices API Gateway built on the Envoy Proxy. Ambassador is built from the ground up to support multiple, independent teams that need to rapidly publish, monitor, and update services for end users.

Ambassador is:

  • Self-service. Ambassador is designed so that developers can manage services directly. This requires a system that is not only easy for developers to use, but provides safety and protection against inadvertent operational issues.
  • Operations friendly. Ambassador operates as a sidecar process to the Envoy Proxy, and integrates Envoy directly with Kubernetes. Thus, all routing, failover, health checking are handled by battle-tested, proven systems.
  • Designed for microservices. Ambassador integrates the features teams need for microservices, including authentication, observability, routing, TLS termination, and more.

Alternatives to Ambassador

Alternatives to Ambassador fall in three basic categories.

Both hosted API Gateways and traditional API gateways are:

A Layer 7 proxy can be used as an API Gateway, but typically requires additional bespoke development to support microservices use cases. In fact, many API Gateways package the additional features needed for an API Gateway on top of a L7 proxy. Ambassador uses Envoy, while Kong uses NGINX. If you're interested in deploying Envoy directly, we've written an introductory tutorial.


Istio is an open source service mesh, built an Envoy. A service mesh is designed to manage east/west traffic, while an API gateway manages north/south traffic. Documentation on how to deploy Ambassador with Istio is here.


We have an ambitious roadmap for Ambassador, and would love for your help. Check out the Ambassador roadmap for more.

results matching ""

    No results matching ""