Kong 0.9.5 has been released

RESTful Interface

Kong RESTful interface

Built on top of NGINX, Kong can be fully operated with a simple and easy to use RESTful API.

Plugin Oriented

Kong plugins

Put your services behind Kong and add powerful functionality through Kong Plugins, in one command.

Platform Agnostic

Platforms supported by Kong

Kong can run anywhere, in the cloud or on-premise - in a single, hybrid or multi-datacenter setup.

Owen Garrett

Kong allows developers to reduce complexity and deployment times in implementing an API solution on NGINX.

Owen Garrett, NGINX Head of Products

Get Started in 1 Minute

  1. Add your API on Kong

    After installing and starting Kong, use the Admin API on port 8001 to add a new API. Kong will route every incoming request with the specified public DNS to the associated target URL.

  2. Add Plugins on the API

    Then add extra functionality by using Kong Plugins. You can also create your own plugins.

  3. Make a Request

    ...and then you can consume the API on port 8000 by requesting the public DNS specified. In production point the public DNS to Kong. It also supports URL path routing.

$ curl -i -X POST \
  --url http://localhost:8001/apis/ \
  --data 'request_host=test.com' \
  --data 'upstream_url=http://mockbin.com'
$ curl -i -X POST \
  --url http://localhost:8001/apis/test.com/plugins/ \
  --data 'name=rate-limiting' \
  --data 'config.minute=100'
$ curl -i -X GET \
  --url http://localhost:8000/ \
  --header 'Host: test.com'

Orchestrate Common Functionality

Legacy Architecture

Complex API architecture without Kong
Common functionality is duplicated across multiple services
Systems tend to be monolithic and hard to maintain
Difficult to expand without impacting other services
Productivity is inefficient because of system constraints

Kong Architecture

Simple API architecture with Kong API Management
Kong centralizes and unifies functionality into one place
Build efficient distributed architectures ready to scale
Expand functionality from one place with a simple command
Your team is focused on the product, Kong does the REST