# Overview The IMESH API gateway offers a Kubernetes-native ingress controller for DevOps and developers to overcome application networking's limitations. It is based on Envoy Proxy, which makes it faster and lighter. It conforms to Kubernetes Gateway API specifications. Unlike legacy gateway solutions, the IMESH API gateway is meant to handle traffic at scale for microservices-based applications. {% embed url="" %} \ Features of IMESH API Gateway are: 1. Unified API interface for DevOps, developers, DevSecOPs, and platform engineers 2. Federated RBAC for developers to create APIs independently 3. Conformance with [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/) standards 4. Native support for Envoy Gateway and Istio Ingress controller 5. The built-in network features such as failover, retries, timeouts, canary, and rate-limiting 6. YAML templates for AuthN/Z policies such as JWT, OIDC, Basic Auth, etc. 7. Support GitOps-style delivery 8. Scale to millions of transactions per day without fail 9. Real-time dashboard for traffic and API performance ### #### --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.imesh.ai/imesh-api-gateway/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.