Data Plane hosting options

When you deploy Kong Gateway, you can choose how your Data Plane nodes are hosted based on the deployment topology you’re using.

Dedicated Cloud Gateways

Dedicated Cloud Gateways are Data Plane nodes that are fully-managed by Kong in Konnect.

You don’t need to host any Data Planes, and you maintain control over the size and location of the gateway infrastructure. This allows Kong to autoscale your nodes for you and reduces your operational complexity.

Benefits of Dedicated Cloud Gateways:

  • Konnect handles gateway upgrades for you.
  • Choose between public and private networking modes.
  • Automatic scaling with Autopilot mode.
  • Support for AWS and Azure in multiple regions.

Supported on:

 
flowchart TD
A(Dedicated Cloud Gateway 
Control Plane)
B(Managed Data Plane Node
Region 1)
C(Managed Data Plane Node
Region 2)

subgraph id1 [Konnect]
A
end

A --auto-scale configuration---> B
A --auto-scale configuration---> C

style id1 stroke-dasharray:3,rx:10,ry:10

  

Serverless gateways

Serverless gateways are lightweight API gateways. Their Control Plane is hosted by Konnect and Data Plane nodes are automatically provisioned. Serverless gateways are ideal for developers who want to test or experiment in a pre-production environment.

Serverless gateways offer the following benefits:

  • Konnect manages provisioning and placement
  • Can be deployed in under 30 seconds
  • Access to Kong Gateway plugins

Supported on:

 
flowchart TD
  A(Dev Portal • Gateway Manager • Advanced Analytics • Service Catalog)
  B( Kong-managed Control Plane 
  #40;Kong Gateway instance#41;)
  C( Data Plane 
  #40;Kong Gateway instance#41;)

  subgraph id1 [Konnect]
  A --- B
  end

  B --Kong proxy 
  configuration---> id2

  subgraph id2 [Fully-managed cloud nodes]
  C
  end

  style id1 stroke-dasharray:3,rx:10,ry:10
  style id2 stroke-dasharray:3,rx:10,ry:10

  

Self-hosted

With self-hosted, you must host your own Data Plane nodes on the supported system of your choice. The diagram shows a self-hosted Kong Gateway instance in hybrid mode.

Supported on:

 
flowchart TD
  A[(Database)]
  B( Control Plane 
  #40;Kong Gateway instance#41;)
  C( Data Plane
  #40;Kong Gateway instance#41;)
  D( Data Plane 1
  #40;Kong Gateway instance#41;)
  E( Data Plane 2
  #40;Kong Gateway instance#41;)

  subgraph id1 [Self-managed Control Plane]
  A---B
  end

  B --Kong proxy configuration---> id2

  subgraph id2 [Self-hosted node]
  C
  D
  E
  end

  style id1 stroke-dasharray:3,rx:10,ry:10
  style id2 stroke-dasharray:3,rx:10,ry:10

  
Something wrong?

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!