Skip to content
Get help

Global service map

Does Kong Gateway work in China?

. Regenerated with each Chinaready Landscape publish.

Quick answer: Self-hosted Kong Gateway OSS/Enterprise is fully usable in mainland China. Availability is Limited mainly because Kong Konnect and overseas control-plane sync are fragile across the border. If you replace Kong, compare Apache APISIX, Flomesh, Higress.

Availability in China: Limited

Kong Gateway in mainland China: self-host vs Konnect

For China launches, separate self-hosted Kong from Kong Konnect / cross-border control planes. Do not treat “Limited” as “Kong cannot run in China.”

Local and private-cloud deployment (fully usable)

  • OSS and Enterprise software: Download Kong OSS or run Enterprise on-prem or on China-region clouds (Alibaba Cloud, Tencent Cloud, AWS China, Azure China).
  • Performance and ecosystem: OpenResty/Nginx lineage, Lua plugins, and mainland community adoption are unaffected by geography.
  • Localization: From Kong 2.3 onward, UTF-8 naming supports Chinese characters for routes and services.

Managed SaaS and cross-border networking (constrained)

  • Kong Konnect: Official hosted control planes sit on Western cloud infrastructure and can see high latency, instability, or blocking from mainland China.
  • Split planes: Overseas control plane + China data plane sync is fragile under Great Firewall network conditions.

Compliance notes

  • ICP filing: Public mainland API endpoints on China-hosted domains need ICP filing; without it, cloud providers cut ports 80/443.
  • Data residency: Sensitive personal data on overseas Kong SaaS may conflict with China’s Data Security Law and PIPL export rules.

Recommendation

For mainland operations, prefer in-country self-hosted Kong (Docker/Kubernetes) over Konnect. If you want a China-native substitute stack, evaluate the mapped options below — Apache APISIX as the closest OpenResty-lineage substitute, Flomesh for gateway plus mesh, and Higress for Envoy/cloud-native stacks.

Kong Gateway alternatives in China

Mapped China-ready candidates

Apache APISIX

Infrastructure & Edge · Service Mesh & Gateway · Direct alternative

Generally available · Global analog limited in China

Apache APISIX is a high-performance open-source API gateway built on OpenResty and Nginx, widely used for mainland China self-hosted API traffic management.

China context: Closest common Kong substitute in China. Same OpenResty/Nginx lineage and Lua plugin model; strong mainland community adoption and commercial support ecosystem.

Flomesh

Infrastructure & Edge · Service Mesh & Gateway · Partial alternative

Generally available · Global analog limited in China

Flomesh provides China-origin service mesh and API gateway capabilities using a Pipy dataplane for east-west and north-south traffic management.

China context: China vendor option when teams need gateway plus service-mesh traffic management rather than a pure Kong-style edge gateway replacement.

Higress

Infrastructure & Edge · Service Mesh & Gateway · Partial alternative

Generally available · Global analog limited in China

Higress is a cloud-native API gateway based on Envoy, commonly evaluated in Alibaba Cloud-native stacks as a Kong-style traffic entry alternative.

China context: Strong fit for teams already on Alibaba Cloud-native infrastructure who want an Envoy-based API gateway rather than an OpenResty/Kong stack.

FAQ

Does Kong Gateway work in China?

Yes for self-hosted deployments. Kong Gateway OSS and Enterprise run well on-prem or on China-region clouds. Chinaready labels Kong Gateway as Limited because Kong Konnect and cross-border control-plane architectures are unreliable or non-compliant for many mainland production stacks.

Why is Kong Gateway labeled Limited if self-hosting works?

Limited refers to the Kong Konnect / overseas control-plane path and related compliance constraints, not to local Kong Gateway software. Mainland teams that self-host Kong inside China usually avoid the Limited failure modes.

What are the best China alternatives to Kong Gateway?

Chinaready Landscape currently maps Kong Gateway to Apache APISIX, Flomesh, Higress. Prefer Apache APISIX when you want the closest OpenResty/Nginx-style substitute, Flomesh when you need gateway plus service-mesh traffic management, and Higress for Envoy-based cloud-native stacks. Replacement fit varies, so treat this as a research shortlist rather than a one-to-one endorsement.

Should teams use Kong Konnect with data planes in China?

Usually no. Syncing an overseas hosted control plane to China data planes is fragile under cross-border network conditions and can create data-residency risk. Prefer an in-country control plane and data plane, or a China-ready substitute gateway.

Where should teams go after shortlisting Kong Gateway alternatives?

Use the interactive Chinaready Landscape to compare adjacent infrastructure services, then read Chinaready's main site for launch operating guidance covering ICP filing, data residency, distribution, and go-to-market constraints beyond vendor selection. If the path remains unclear, book a call with Chinaready.