Skip to content
Kong Docs are moving soon! Our docs are migrating to a new home. You'll be automatically redirected to the new site in the future. In the meantime, view this page on the new site!
Kong Logo | Kong Docs Logo
  • Docs
    • Explore the API Specs
      View all API Specs View all API Specs View all API Specs arrow image
    • Documentation
      API Specs
      Kong Gateway
      Lightweight, fast, and flexible cloud-native API gateway
      Kong Konnect
      Single platform for SaaS end-to-end connectivity
      Kong AI Gateway
      Multi-LLM AI Gateway for GenAI infrastructure
      Kong Mesh
      Enterprise service mesh based on Kuma and Envoy
      decK
      Helps manage Kong’s configuration in a declarative fashion
      Kong Ingress Controller
      Works inside a Kubernetes cluster and configures Kong to proxy traffic
      Kong Gateway Operator
      Manage your Kong deployments on Kubernetes using YAML Manifests
      Insomnia
      Collaborative API development platform
  • Plugin Hub
    • Explore the Plugin Hub
      View all plugins View all plugins View all plugins arrow image
    • Functionality View all View all arrow image
      View all plugins
      AI's icon
      AI
      Govern, secure, and control AI traffic with multi-LLM AI Gateway plugins
      Authentication's icon
      Authentication
      Protect your services with an authentication layer
      Security's icon
      Security
      Protect your services with additional security layer
      Traffic Control's icon
      Traffic Control
      Manage, throttle and restrict inbound and outbound API traffic
      Serverless's icon
      Serverless
      Invoke serverless functions in combination with other plugins
      Analytics & Monitoring's icon
      Analytics & Monitoring
      Visualize, inspect and monitor APIs and microservices traffic
      Transformations's icon
      Transformations
      Transform request and responses on the fly on Kong
      Logging's icon
      Logging
      Log request and response data using the best transport for your infrastructure
  • Support
  • Community
  • Kong Academy
Get a Demo Start Free Trial
Kong Gateway
3.3.x
  • Home icon
  • Kong Gateway
  • Kong Enterprise
  • Consumer Groups
  • Consumer Groups
github-edit-pageEdit this page
report-issueReport an issue
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Kong AI Gateway
  • Plugin Hub
  • decK
  • Kong Ingress Controller
  • Kong Gateway Operator
  • Insomnia
  • Kuma

  • Docs contribution guidelines
  • 3.10.x (latest)
  • 3.9.x
  • 3.8.x
  • 3.7.x
  • 3.6.x
  • 3.5.x
  • 3.4.x (LTS)
  • 3.3.x
  • 2.8.x (LTS)
  • Archive (3.0.x and pre-2.8.x)
  • Introduction
    • Overview of Kong Gateway
    • Support
      • Version Support Policy
      • Third Party Dependencies
      • Browser Support
      • Software Bill of Materials
    • Stability
    • Release Notes
    • Breaking Changes
      • Kong Gateway 3.3.x
      • Kong Gateway 3.2.x
      • Kong Gateway 3.1.x
      • Kong Gateway 3.0.x
      • Kong Gateway 2.8.x or earlier
    • Key Concepts
      • Services
      • Routes
      • Consumers
      • Upstreams
      • Plugins
    • How Kong Works
      • Routing Traffic
      • Load Balancing
      • Health Checks and Circuit Breakers
      • Kong Performance Testing
    • Glossary
  • Get Started with Kong
    • Get Kong
    • Services and Routes
    • Rate Limiting
    • Proxy Caching
    • Key Authentication
    • Load-Balancing
  • Kong in Production
    • Deployment Topologies
      • Overview
      • Kubernetes Topologies
      • Hybrid Mode
        • Overview
        • Deploy Kong Gateway in Hybrid mode
      • DB-less Deployment
      • Traditional
    • Installation Options
      • Overview
      • Kubernetes
        • Overview
        • Install Kong Gateway
        • Configure the Admin API
        • Install Kong Manager
        • Install Developer Portal
      • Docker
        • Using docker run
        • Build your own Docker images
      • Linux
        • Amazon Linux
        • Debian
        • Red Hat
        • Ubuntu
      • Post-installation
        • Set up a data store
        • Apply Enterprise license
        • Enable Kong Manager (Enterprise)
    • Running Kong
      • Running Kong as a non-root user
      • Securing the Admin API
      • Using systemd
    • Access Control
      • Start Kong Gateway Securely
      • Programmatically Creating Admins
      • Enabling RBAC
    • Licenses
      • Overview
      • Download your License
      • Deploy Enterprise License
      • Using the License API
      • Monitor Licenses Usage
    • Networking
      • Default Ports
      • DNS Considerations
      • Network and Firewall
      • CP/DP Communication through a Forward Proxy
      • PostgreSQL TLS
        • Configure PostgreSQL TLS
        • Troubleshooting PostgreSQL TLS
    • Kong Configuration File
    • Environment Variables
    • Serving a Website and APIs from Kong
    • Monitoring
      • Overview
      • Prometheus
      • StatsD
      • Datadog
      • Health Check Probes
    • Tracing
      • Overview
      • Writing a Custom Trace Exporter
      • Tracing API Reference
    • Resource Sizing Guidelines
    • Security Update Process
    • Blue-Green Deployments
    • Canary Deployments
    • Clustering Reference
    • Logging
      • Log Reference
      • Dynamic log level updates
      • Customize Gateway Logs
    • Configure a gRPC service
    • Use the Expressions Router
    • Upgrade and Migration
      • Upgrading Kong Gateway 3.x.x
      • Backup and Restore
      • Upgrade Strategies
        • Dual-Cluster Upgrade
        • In-Place Upgrade
        • Blue-Green Upgrade
        • Rolling Upgrade
      • Upgrade from 2.8 LTS to 3.4 LTS
      • Migrate from OSS to Enterprise
      • Migration Guidelines Cassandra to PostgreSQL
      • Breaking Changes
  • Kong Gateway Enterprise
    • Overview
    • Kong Vitals
      • Overview
      • Metrics
      • Analytics with InfluxDB
      • Analytics with Prometheus
      • Estimate Analytics Storage in PostgreSQL
    • Secrets Management
      • Overview
      • Getting Started
      • Advanced Usage
      • Backends
        • Overview
        • Environment Variables
        • AWS Secrets Manager
        • Google Cloud Secret Manager
        • HashiCorp Vault
      • How-To
        • Securing the Database with AWS Secrets Manager
      • Reference Format
    • Dynamic Plugin Ordering
      • Overview
      • Get Started with Dynamic Plugin Ordering
    • Dev Portal
      • Overview
      • Enable the Dev Portal
      • Publish an OpenAPI Spec
      • Structure and File Types
      • Themes Files
      • Working with Templates
      • Using the Editor
      • Authentication and Authorization
        • Basic Auth
        • Key Auth
        • OIDC
        • Sessions
        • Adding Custom Registration Fields
        • Manage Developers
        • Developer Roles and Content Permissions
      • Application Registration
        • Authorization Provider Strategy
        • Enable Application Registration
        • Enable Key Authentication for Application Registration
        • Enable External Authentication
          • External OAuth2 Support
          • Set up Okta and Kong for External Oauth
          • Set up Azure AD and Kong for External Authentication
        • Manage Applications
      • Customize Dev Portal
        • Theme Editing
        • Migrating Templates Between Workspaces
        • Markdown Rendering Module
        • Customizing Portal Emails
        • Adding and Using JavaScript Assets
        • Single Page App in Dev Portal
        • Alternate OpenAPI Renderer
      • SMTP
      • Workspaces
      • Helpers CLI
      • Portal API Documentation
    • Audit Logging
    • Keyring and Data Encryption
    • Workspaces
    • Consumer Groups
    • Event Hooks
    • Configure Data Plane Resilience
    • About Control Plane Outage Management
    • FIPS 140-2
      • Overview
      • Install the FIPS Compliant Package
    • Authenticate your Kong Gateway Amazon RDS database with AWS IAM
  • Kong Manager
    • Overview
    • Enable Kong Manager
    • Get Started with Kong Manager
      • Services and Routes
      • Rate Limiting
      • Proxy Caching
      • Authentication with Consumers
      • Load Balancing
    • Authentication and Authorization
      • Overview
      • Create a Super Admin
      • Workspaces and Teams
      • Reset Passwords and RBAC Tokens
      • Basic Auth
      • LDAP
        • Configure LDAP
        • LDAP Service Directory Mapping
      • OIDC
        • Configure OIDC
        • OIDC Authenticated Group Mapping
      • Sessions
      • RBAC
        • Overview
        • Enable RBAC
        • Add a Role and Permissions
        • Create a User
        • Create an Admin
    • Networking Configuration
    • Workspaces
    • Create Consumer Groups
    • Sending Email
  • Develop Custom Plugins
    • Overview
    • File Structure
    • Implementing Custom Logic
    • Plugin Configuration
    • Accessing the Data Store
    • Storing Custom Entities
    • Caching Custom Entities
    • Extending the Admin API
    • Writing Tests
    • (un)Installing your Plugin
    • Plugin Development Kit
      • Overview
      • kong.client
      • kong.client.tls
      • kong.cluster
      • kong.ctx
      • kong.ip
      • kong.jwe
      • kong.log
      • kong.nginx
      • kong.node
      • kong.request
      • kong.response
      • kong.router
      • kong.service
      • kong.service.request
      • kong.service.response
      • kong.table
      • kong.tracing
      • kong.vault
      • kong.websocket.client
      • kong.websocket.upstream
    • Plugins in Other Languages
      • Go
      • Javascript
      • Python
      • Running Plugins in Containers
      • External Plugin Performance
  • Kong Plugins
    • Overview
    • Authentication Reference
    • Allow Multiple Authentication Plugins
    • Plugin Queuing
      • Overview
      • Plugin Queuing Reference
  • Admin API
    • Overview
    • Information Routes
    • Health Routes
    • Tags
    • Debug Routes
    • Services
    • Routes
    • Consumers
    • Plugins
    • Certificates
    • CA Certificates
    • SNIs
    • Upstreams
    • Targets
    • Vaults
    • Keys
    • Licenses
    • Workspaces
    • RBAC
    • Admins
    • Developers
    • Consumer Groups
    • Event Hooks
    • Keyring and Data Encryption
    • Audit Logs
    • Status API
  • Reference
    • kong.conf
    • Injecting Nginx Directives
    • CLI
    • Key Management
    • Performance Testing Framework
    • The Expressions Language
      • Overview
      • Language References
      • Performance Optimizations
    • Rate Limiting Library
    • FAQ
enterprise-switcher-icon Switch to OSS
On this pageOn this page
  • Set up consumer group
  • Set up Rate Limiting Advanced config for consumer group
  • Remove consumer from group - group view
  • Remove consumer from group - consumer view
  • Delete consumer group configurations
  • Delete consumer group
  • Manage multiple consumers
  • More information
You are browsing documentation for an older version. See the latest documentation here.

Consumer Groups

Consumer groups enable the organization and categorization of consumers (users or applications) within an API ecosystem. By grouping consumers together, you eliminate the need to manage them individually, providing a scalable, efficient approach to managing configurations.

With consumer groups, you can define any number of rate limiting tiers and apply them to subsets of consumers, instead of managing each consumer individually.

For example, you could define three consumer groups:

  • A “gold tier” with 1000 requests per minute
  • A “silver tier” with 10 requests per second
  • A “bronze tier” with 6 requests per second

The consumer_groups endpoint works together with the Rate Limiting Advanced plugin.

Consumers that are not in a consumer group default to the Rate Limiting advanced plugin’s configuration, so you can define tier groups for some users and have a default behavior for consumers without groups.

To use consumer groups for rate limiting, you need to:

  • Create one or more consumer groups
  • Create consumers
  • Assign consumers to groups
  • Configure the Rate Limiting Advanced plugin with the enforce_consumer_groups and consumer_groups parameters, setting up the list of consumer groups that the plugin accepts
  • Configure rate limiting for each consumer group, overriding the plugin’s configuration

For all possible requests, see the Consumer Groups reference.

Set up consumer group

  1. Create a consumer group named Gold:

     curl -i -X POST http://{HOSTNAME}:8001/consumer_groups \
     --data name=Gold
    

    Response:

     {
         "created_at": 1638915521,
         "id": "8a4bba3c-7f82-45f0-8121-ed4d2847c4a4",
         "name": "Gold",
         "tags": null
     }
    
  2. Create a consumer, Amal:

     curl -i -X POST http://{HOSTNAME}:8001/consumers \
     --data username=Amal
    

    Response:

     {
         "created_at": 1638915577,
         "custom_id": null,
         "id": "8089a0e6-1d31-4e00-bf51-5b902899b4cb",
         "tags": null,
         "type": 0,
         "username": "Amal",
         "username_lower": "amal"
     }
    
  3. Add Amal to the Gold consumer group:

     curl -i -X POST http://{HOSTNAME}:8001/consumer_groups/Gold/consumers \
     --data consumer=Amal
    

    Response:

     {
       "consumer_group": {
       "created_at": 1638915521,
       "id": "8a4bba3c-7f82-45f0-8121-ed4d2847c4a4",
       "name": "Gold",
       "tags": null
       },
       "consumers": [
         {
             "created_at": 1638915577,
             "id": "8089a0e6-1d31-4e00-bf51-5b902899b4cb",
             "type": 0,
             "username": "Amal",
             "username_lower": "amal"
         }
       ]
     }
    

Set up Rate Limiting Advanced config for consumer group

  1. Enable the Rate Limiting Advanced plugin, setting the rate limit to five requests (config.limit) for every 30 seconds (config.window_size):

     curl -i -X POST http://{HOSTNAME}:8001/plugins/  \
     --data name=rate-limiting-advanced \
     --data config.limit=5 \
     --data config.window_size=30 \
     --data config.window_type=sliding \
     --data config.retry_after_jitter_max=0 \
     --data config.enforce_consumer_groups=true \
     --data config.consumer_groups=Gold
    

    For consumer groups, the following parameters are required:

    • config.enforce_consumer_groups=true: enables consumer groups for this plugin.
    • config.consumer_groups=Gold: specifies a list of groups that this plugin allows overrides for.

    Note: In this example, you’re configuring the plugin globally, so it applies to all entities (Services, Routes, and Consumers) in the Kong Gateway instance. You can also apply it to a specific Service or Route for more granular control.

  2. The plugin you just set up applies to all consumers in the cluster. Change the rate limiting configuration for the Gold consumer group only, setting the limit to ten requests for every ten seconds:

     curl -i -X PUT http://{HOSTNAME}:8001/consumer_groups/Gold/overrides/plugins/rate-limiting-advanced \
     --data config.limit=10 \
     --data config.window_size=10 \
     --data config.retry_after_jitter_max=1
    

    Response:

     {
       "config": {
           "limit": [
               10
           ],
           "retry_after_jitter_max": 1,
           "window_size": [
               10
           ]
       },
       "consumer_group": "Gold",
       "plugin": "rate-limiting-advanced"
     }
    
  3. Check that it worked by looking at the Gold consumer group object:

     curl -i -X GET http://{HOSTNAME}:8001/consumer_groups/Gold
    

    Notice the plugins object in the response, along with the parameters that you just set for the Rate Limiting Advanced plugin:

     {
         "consumer_group": {
             "created_at": 1638915521,
             "id": "8a4bba3c-7f82-45f0-8121-ed4d2847c4a4",
             "name": "Gold",
             "tags": null
         },
         "consumers": [
             {
                 "created_at": 1638915577,
                 "id": "8089a0e6-1d31-4e00-bf51-5b902899b4cb",
                 "type": 0,
                 "username": "Amal",
                 "username_lower": "amal"
             }
         ],
         "plugins": [
             {
                 "config": {
                     "limit": [
                         10
                     ],
                     "retry_after_jitter_max": 1,
                     "window_size": [
                         10
                     ],
                     "window_type": "sliding"
                 },
                 "consumer_group": {
                     "id": "8a4bba3c-7f82-45f0-8121-ed4d2847c4a4"
                 },
                 "created_at": 1638916518,
                 "id": "b7c426a2-6fcc-4bfd-9b7a-b66e8f1ad260",
                 "name": "rate-limiting-advanced"
             }
         ]
     }
    

Remove consumer from group - group view

You can remove a consumer from a group by accessing /consumers or /consumer_groups. The following steps use /consumer_groups.

  1. Check the Gold consumer group for the consumer name:

     curl -i -X GET http://{HOSTNAME}:8001/consumer_groups/Gold
    

    Response:

     {
         "consumer_group": {
             "created_at": 1638915521,
             "id": "8a4bba3c-7f82-45f0-8121-ed4d2847c4a4",
             "name": "Gold",
             "tags": null
         },
         "consumers": [
             {
                 "created_at": 1638915577,
                 "id": "8089a0e6-1d31-4e00-bf51-5b902899b4cb",
                 "type": 0,
                 "username": "Amal",
                 "username_lower": "amal"
             }
         ]
       }
    
  2. Using the username or ID of the consumer (Amal in this example), remove the consumer from the group:

     curl -i -X DELETE http://{HOSTNAME}:8001/consumer_groups/Gold/consumers/Amal
    

    If successful, you receive the following response:

     HTTP/1.1 204 No Content
    
  3. To verify, check the consumer group configuration again:

     curl -i -X GET http://{HOSTNAME}:8001/consumer_groups/Gold
    

    Response, with no consumers assigned:

     {
         "consumer_group": {
             "created_at": 1638917780,
             "id": "be4bcfca-b1df-4fac-83cc-5cf6774bf48e",
             "name": "Gold",
             "tags": null
         }
     }
    

Remove consumer from group - consumer view

You can remove a consumer from a group by accessing /consumers or /consumer_groups. The following steps use /consumers.

  1. If you know the consumer name and not the consumer group name, you can look up the group through the consumer:

     curl -i -X GET http://{HOSTNAME}:8001/consumers/Amal/consumer_groups
    

    Response:

     {
         "consumer_groups": [
             {
                 "created_at": 1638915521,
                 "id": "8a4bba3c-7f82-45f0-8121-ed4d2847c4a4",
                 "name": "Gold",
                 "tags": null
             }
         ]
     }
    
  2. Using the username or ID of the group (Gold in this example), remove the consumer from the group:

     curl -i -X DELETE http://{HOSTNAME}:8001/consumers/Amal/consumer_groups/Gold
    

    If successful, you receive the following response:

     HTTP/1.1 204 No Content
    
  3. To verify, check the consumer object configuration:

     curl -i -X GET http://{HOSTNAME}:8001/consumer_groups/Gold
    

    Response, with no consumers assigned:

     {
         "consumer_group": {
             "created_at": 1638917780,
             "id": "be4bcfca-b1df-4fac-83cc-5cf6774bf48e",
             "name": "Gold",
             "tags": null
         }
     }
    

Delete consumer group configurations

You can also clear the configuration of a consumer group without deleting the consumer group itself.

With this method, the consumers in the group aren’t deleted and are still in the consumer group.

  1. Delete the consumer group configuration using the following request:

     curl -i -X DELETE http://{HOSTNAME}:8001/consumer_groups/Gold/overrides/plugins/rate-limiting-advanced
    

    If successful, you receive see the following response:

     HTTP/1.1 204 No Content
    
  2. To verify, check the consumer object configuration:

     curl -i -X GET http://{HOSTNAME}:8001/consumer_groups/Gold
    

    Response, without a plugins object:

     {
         "consumer_group": {
             "created_at": 1638917780,
             "id": "be4bcfca-b1df-4fac-83cc-5cf6774bf48e",
             "name": "Gold",
             "tags": null
         }
     }
    

Delete consumer group

If you don’t need a consumer group anymore, you can delete it. This removes all consumers from the group, and deletes the group itself. The consumers in the group are not deleted.

  1. Delete a consumer group using the following request:

     curl -i -X DELETE http://{HOSTNAME}:8001/consumer_groups/Gold
    

    If successful, you receive see the following response:

     HTTP/1.1 204 No Content
    
  2. Check the list of consumer groups to verify that the Gold group is gone:

     curl -i -X GET http://{HOSTNAME}:8001/consumer_groups
    

    Response:

     {
     "data": [],
     "next": null
     }
    
  3. Check a consumer that was in the group to make sure it still exists:

     curl -i -X GET http://{HOSTNAME}:8001/consumers/Amal
    

    An HTTP/1.1 200 OK response means the consumer exists.

Manage multiple consumers

You can perform many /consumer_groups operations in bulk.

  1. Assuming you deleted the group Gold in the previous section, create it again, along with another group named Speedsters:

     curl -i -X POST http://{HOSTNAME}:8001/consumer_groups \
     --data name=Gold
    
     curl -i -X POST http://{HOSTNAME}:8001/consumer_groups \
     --data name=Speedsters
    
  2. Create two consumers, BarryAllen and WallyWest:

     curl -i -X POST http://{HOSTNAME}:8001/consumers \
     --data username=BarryAllen
    
     curl -i -X POST http://{HOSTNAME}:8001/consumers \
     --data username=WallyWest
    
  3. Add both consumers to the Speedsters group:

     curl -i -X POST http://{HOSTNAME}:8001/consumer_groups/Speedsters/consumers \
     --data consumer=BarryAllen \
     --data consumer=WallyWest
    

    Kong Gateway validates the provided list of consumers before assigning them to the consumer group. To pass validation, consumers must exist and must not be in the group already.

    If any consumer fails validation, no consumers are assigned to the group.

    Response, if everything is successful:

     {
         "consumer_group": {
             "created_at": 1639432267,
             "id": "a905151a-5767-40e8-804e-50eec4d0235b",
             "name": "Speedsters",
             "tags": null
         },
         "consumers": [
             {
                 "created_at": 1639432286,
                 "id": "ea904e1d-1f0d-4d5a-8391-cae60cb21d61",
                 "type": 0,
                 "username": "BarryAllen",
                 "username_lower": "barryallen"
             },
             {
                 "created_at": 1639432288,
                 "id": "065d8249-6fe6-4d80-a0ae-f159caef7af0",
                 "type": 0,
                 "username": "WallyWest",
                 "username_lower": "wallywest"
             }
         ]
     }
    
  4. You can clear all consumers from a group with one request. This may be useful if you need to cycle the group for a new batch of users.

    For example, delete all consumers from the Speedsters group:

     curl -i -X DELETE http://{HOSTNAME}:8001/consumer_groups/Speedsters/consumers
    

    Response:

     HTTP/1.1 204 No Content
    
  5. You can also add a consumer to multiple groups:
    • If all groups are allowed by the Rate Limiting Advanced plugin, only the first group’s settings apply.
    • Otherwise, whichever group is specified in the Rate Limiting Advanced plugin becomes active.

    Add BarryAllen to two groups, Gold and Speedsters:

     curl -i -X POST http://{HOSTNAME}:8001/consumers/BarryAllen/consumer_groups \
     --data group=Gold \
     --data group=Speedsters
    

    The response should look something like this:

     {
       "consumer": {
           "created_at": 1639436091,
           "custom_id": null,
           "id": "6098d577-6741-4cf8-9c86-e68057b8f970",
           "tags": null,
           "type": 0,
           "username": "BarryAllen",
           "username_lower": "barryallen"
       },
       "consumer_groups": [
           {
               "created_at": 1639432267,
               "id": "a905151a-5767-40e8-804e-50eec4d0235b",
               "name": "Gold",
               "tags": null
           },
           {
               "created_at": 1639436107,
               "id": "2fd2bdd6-690c-4e49-8296-31f55015496d",
               "name": "Speedsters",
               "tags": null
           }
       ]
     }
    
  6. Finally, you can also remove a consumer from all groups:

     curl -i -X DELETE http://{HOSTNAME}:8001/consumers/BarryAllen/consumer_groups
    

    Response:

     HTTP/1.1 204 No Content
    

More information

  • Consumer group precedence information.
  • API documentation
  • Enforcing rate limiting tiers with the Rate Limiting Advanced plugin
  • Consumer groups in Kong Manager
  • Consumer groups in Konnect
Thank you for your feedback.
Was this page useful?
Too much on your plate? close cta icon
More features, less infrastructure with Kong Konnect. 1M requests per month for free.
Try it for Free
  • Kong
    Powering the API world

    Increase developer productivity, security, and performance at scale with the unified platform for API management, service mesh, and ingress controller.

    • Products
      • Kong Konnect
      • Kong Gateway Enterprise
      • Kong Gateway
      • Kong Mesh
      • Kong Ingress Controller
      • Kong Insomnia
      • Product Updates
      • Get Started
    • Documentation
      • Kong Konnect Docs
      • Kong Gateway Docs
      • Kong Mesh Docs
      • Kong Insomnia Docs
      • Kong Konnect Plugin Hub
    • Open Source
      • Kong Gateway
      • Kuma
      • Insomnia
      • Kong Community
    • Company
      • About Kong
      • Customers
      • Careers
      • Press
      • Events
      • Contact
  • Terms• Privacy• Trust and Compliance
© Kong Inc. 2025