Express Gateway is an API Gateway that sits at the heart of any microservices architecture. This chart bootstraps all the components needed to run Express Gateway on a Kubernetes cluster using the Helm package manager.

Express Gateway is an API Gateway that sits at the heart of any microservices architecture, regardless of what language or platform you’re using. Express Gateway secures your microservices and exposes them through APIs using Node.js, ExpressJS and Express middleware. Developing microservices, orchestrating and managing them now can be done insanely fast all on one seamless platform without having to introduce additional infrastructure.

Main Features

  • Built Entirely on Express and Express Middleware
  • Dynamic Centralized Config
  • API Consumer and Credentials Management
  • Plugins and Plugin Framework
  • Distributed Data Store
  • CLI


The Express Gateway roadmap consists of three parts:

  • FeatHub – features requested and voted on by any community member, this feeds into the…
  • Roadmap – the published roadmap of all features under considerations and projected timeframes, the highest priority items are put into the…
  • Waffle board – a real-time as a public task board on with the backlog of stories for the next release

With Express Gateway, you actually get to leverage the vast ecosystem of Express.js middleware and another open source to get the job done.


Community Driven

As part of our ongoing commitment to the community, as sponsors of the Express Gateway project, we expanded on our initial ideas and built out a Roadmap that was flexible enough to adapt based on community input, but also sent the right external signal so if you — or anyone else, who wanted to get more involved, we could share our initial vision.



In several user interviews, a few key insights stood out. Even when you’re trying to launch an open source project, the same design thinking principles till apply. In order to attain the kind of flexibility we were looking for, the team decided to stick to a few core concepts:

  • Create a gateway for any language, framework
  • Make this gateway with all microservice use cases in mind


Above all else, we wanted to make Express Gateway simple. API Gateways and microservices are complicated enough.

Here are a few things we focused on during the initial build phase:

  • * A declarative config separated from the code to control it all
  • * Building some of the most commonly used gateway policies like OAuth2, rate limiting etc
  • * A full-blown consumer and credential management system out of the box
  • Auto-detect and hot-reload config changes

Plugging into our latest release

In case you missed it, we also just had a recent release that included an extensible Plugin Framework. Express Gateway 1.2.0 adds a new plugin engine that allows anyone to add their own extension entities within a plugin. Then you can install and utilize it dynamically within Express Gateway.

The Quick & Dirty:

An Express Gateway plugin acts as a container and has three key things:

  • Package.json
  • A folder for each entity extension
  • Manifest.js
  • The package.json declares all dependencies that the plugin requires, just like any Node.js modules.
  • We got to work breaking down all of the installations, entity extension point folders, manifest.js, and more of that magic.

All about the code

But, how easy is it to get started with an open source API Gateway like Express Gateway?

Well, let’s see.

Get the start of a real-time app up and running, complete with authentication. First, install your dependencies by running.

Tell us about a new Kubernetes application


Never miss a thing! Sign up for our newsletter to stay updated.


Discover and learn about everything Kubernetes