Kong Gateway OSS
We provide consulting, deployment, configuration, integration, and technical support for Kong Gateway OSS. We help organizations manage API traffic through a gateway layer with clear routing, access policies, monitoring, and operating procedures.
Our work focuses on the capabilities available in the selected open source release and its OSS plugins. Whether you are introducing a gateway or improving an existing deployment, we work with your development and infrastructure teams to understand upstream services, client behavior, and the responsibilities involved in operating the gateway.
A gateway sits on the path between clients and applications. Routing mistakes, inconsistent configuration, certificate issues, and unsuitable timeout settings can affect many services at once.
We help your team manage that shared responsibility through tested configuration, controlled changes, and visibility into how requests move through the platform.
What we do
01 / 10
Decide how Kong Gateway OSS should fit into your application environment. We review traffic patterns, network boundaries, upstream dependencies, and supported deployment modes so that the design reflects operational needs and the capabilities of the selected release.
02 / 10
Establish the gateway with validated connectivity and documented configuration. We configure the chosen runtime and any required database, protect administrative interfaces, and test representative requests before supporting production introduction and the operational handover.
03 / 10
Organize routing so that requests reach the intended applications predictably. We configure services, routes, upstream targets, and request matching, then test behavior for normal requests, edge cases, and unavailable backends.
04 / 10
Apply the selected OSS authentication and traffic-control plugins where they meet the requirement. We review plugin availability and behavior, configure policies, and test client requests so that access decisions and rate limits are understood.
05 / 10
Configure secure connections across the gateway path. We review certificates, client-facing listeners, upstream connectivity, and network access, documenting certificate renewal and the dependencies operators need to maintain when application endpoints or infrastructure change.
06 / 10
Help your team manage gateway configuration through repeatable changes. We organize declarative configuration or supported administration workflows, review environment differences, and test updates before rollout so that routes and policies remain easier to trace and maintain.
07 / 10
Investigate latency and errors across the gateway and upstream applications. We review request metrics, logs, resource usage, timeout behavior, and connection settings, then validate targeted changes against representative API traffic.
08 / 10
Plan gateway operations around failure and maintenance scenarios. We review node redundancy and configuration recovery, rehearse upgrades, and validate routes and plugin behavior after changes, including database compatibility where the deployment uses a database.
09 / 10
Get help with routing failures, upstream errors, authentication problems, certificate incidents, latency increases, and configuration deployment issues. We examine the available evidence, coordinate investigation across the relevant components, and help your team identify corrective actions.
Support arrangements define the covered environment, service hours, communication channels, priorities, and escalation process. This gives your team a clear route for requesting assistance and following an issue through investigation, validation, and closure.
10 / 10
Build practical understanding of service and route administration, OSS plugins, configuration workflows, monitoring, certificate management, and gateway recovery. We tailor sessions to the environment and the responsibilities of the people developing, administering, and supporting it.
Workshops can use your configuration, representative examples, and agreed operating scenarios. Documentation and runbook walkthroughs help your team apply the knowledge after the engagement.
How we engage
You may need a technical assessment, a defined implementation project, help with a recurring problem, or ongoing operational assistance. We offer consulting, project delivery, and support arrangements built around that need.
We can work alongside your internal team or take responsibility for agreed activities. The scope sets out the environment, dependencies, access, deliverables, and responsibilities, with coverage and response targets defined in the service agreement. Ongoing engagements can include scheduled health reviews, maintenance planning, and progress reporting.
01
Assessments, architecture reviews and technical guidance.
02
Implementation, migration and upgrade projects with handover.
03
Incident investigation and resolution guidance under agreed coverage.
04
Ongoing administration for the activities assigned to us.
We test the gateway as part of the application request path. Validation includes both successful traffic and expected failure responses, with clear records of route behavior, policy scope, administrative access, and the configuration needed to reproduce the deployment.
We agree the work and acceptance checks with your team, validate changes in a suitable environment, and document the outcome. Clear handover makes the configuration, operating procedures, and next actions easier to maintain after delivery.
Versions below were confirmed against upstream release information on 15 October 2026. We reconfirm them at the start of each engagement.
Because no upstream OSS fixes follow 3.9.3, security and defect fixes are limited to what we can deliver within the agreed scope. We state this limit in every engagement and can plan a migration to a supported gateway.
Standard support is delivered in business hours, Monday to Saturday, India Standard Time. Coverage hours, response targets and escalation steps for each severity are defined in the service agreement. Upstream response times are outside our control.
Get in touch
Introducing Kong Gateway OSS or looking for help with API routing and gateway operations? Share your services, traffic requirements, and current deployment so we can define an appropriate engagement.
Kong and Kong Gateway are trademarks of their respective owners and are used here only to describe the software we support. We are an independent service provider and are not affiliated with, endorsed by or sponsored by the Kong project or its trademark owner.
Copyright 2026 AMNEX INFOTECHNOLOGIES PRIVATE LIMITED.
