Plugin Compatibility

DB-less mode is the preferred choice for controller-managed Kong and Kong Enterprise clusters. However, not all plugins are available in DB-less mode. Review the table below to check if a plugin you wish to use requires a database.

Note that some DB-less compatible plugins have some limitations or require non-default configuration for compatibility.

Kong

Plugin	Kong	Kong (DB-less)
`acl`
`aws-lambda`
`azure-functions`
`basic-auth`
`bot-detection`
`correlation-id`
`cors`
`datadog`
`file-log`
`hmac-auth`
`http-log`
`ip-restriction`
`jwt`
`key-auth`
`oauth2`
`post-function`
`pre-function`
`prometheus`
`proxy-cache`
`rate-limiting`
`request-termination`
`request-transformer`
`response-ratelimiting`
`response-transformer`
`syslog`
`tcp-log`
`udp-log`
`zipkin`

Kong Enterprise

Plugin	Kong Enterprise	Kong Enterprise (DB-less)
`acl`
`aws-lambda`
`azure-functions`
`basic-auth`
`bot-detection`
`correlation-id`
`cors`
`datadog`
`file-log`
`hmac-auth`
`http-log`
`ip-restriction`
`jwt`
`key-auth`
`oauth2`
`post-function`
`pre-function`
`prometheus`
`proxy-cache`
`rate-limiting`
`request-termination`
`request-transformer`
`response-ratelimiting`
`response-transformer`
`syslog`
`tcp-log`
`udp-log`
`zipkin`
`application-registration`		¹
`canary`
`degraphql`
`exit-transformer`
`forward-proxy`
`graphql-proxy-cache-advanced`
`graphql-rate-limiting-advanced`
`jwt-signer`
`kafka-log`
`kafka-upstream`
`key-auth-enc`
`ldap-auth-advanced`
`mtls-auth`
`oauth2-introspection`
`openid-connect`
`proxy-cache-advanced`
`rate-limiting-advanced`
`request-transformer-advanced`
`request-validator`
`response-transformer-advanced`
`route-transformer-advanced`
`statsd-advanced`		²
`vault-auth`

¹ Only used with Dev Portal

² Only used with Vitals