Skip to content
Microgateway server core, executes main port forwarding logic when fed config and plugins
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
tests Merge pull request #133 from evanmiller67/feature/add-configurable-ke… Aug 30, 2019
.eslintrc Add eslint config Aug 9, 2019
.gitignore one more .gitignore update Jun 14, 2019
.jshintrc introduce changes for code quality Jun 28, 2019
.travis.yml introduce changes for code quality Jun 28, 2019
LICENSE Update LICENSE Mar 31, 2016 Fix capitalization in readme Feb 20, 2018
index.js Creating centralized console logging Jul 31, 2019
npm-shrinkwrap.json 3.0.5 Aug 30, 2019
package.json 3.0.5 Aug 30, 2019
server.js Creating centralized console logging Jul 31, 2019


Microgateway-core is a pass through api proxy that events to plugin middleware. The plugin middleware can implement a variety of functions like oauth, spikearrest, and quotas on your apis.

We have provided some default middleware that you can use in the microgateway-plugin repo.


To use microgateway-core you must initialize microgateway with a config. The config can be instantiated using the microgateway-config repo.

const config = require('microgateway-config');
config.init({source:'<>', targetDir:'<>', targetFile:'<>'});
const Gateway = require('microgateway-core');
const plugin = {
		return {
			onrequest:(req,res,options,cb) => {
config.get({source:'same.yaml',keys:{key: '', secret: ''}},(err,config)=>{
	const gateway = Gateway(config);
	gateway.addPlugin('my-plugin', plugin.init);

More info

For more info on usage we use the microgateway-core to power our microgateway product. We use a command line utility here.

You can’t perform that action at this time.