Centralized Decentralization: Migration from Azure to Kong

How VIPPS MobilePay migrated at scale using Kong Gateway on AKS, canary routing, and GitHub OIDC guardrails—reducing scale time 89% and improving DX.

VIPPS MobilePay shares how they migrated from Azure API Management (APIM) to Kong Gateway using a canary proxy, AKS, and a centralized pipeline with GitHub OIDC guardrails—achieving an 89% reduction in scale time and a better developer experience.

Key topics covered:

- Canary traffic splitting APIM ⇆ Kong and rollback strategy

- 89% faster scaling on Kubernetes (AKS) vs. APIM autoscale delays

- YAML-first API ops with decK and GitHub OIDC tagging/guardrails

- Decentralized manifests, centralized pipelines, and ownership enforcement

- Operational insights: routes, upstreams, tokens, incident response context