- Organisation
- Vipps MobilePay
- Predecessor
- Azure Application Gateway to Azure API Management to NGINX ingress
- Destination
- Azure Application Gateway to Kong Gateway on AKS
- Workload
- Vipps MobilePay API estate handling more than 10 billion monthly API calls across environments
- Stage
- Completed API gateway migration and decommissioning
- Retirement status
- Azure API Management was fully decommissioned and its resources were deleted.
- Confidence
- High
- Next trigger
- A material Kong architecture change or later API-estate consolidation milestone.
Programme context
Vipps MobilePay completed migration from Azure API Management to Kong Gateway and fully decommissioned the APIM resources.
Why this matters: The record identifies a named organisation, an explicit predecessor and destination platform, and a bounded workload and lifecycle stage.
Migration timeline
| Date or stage | Milestone | What changed | Evidence status |
|---|---|---|---|
| May 2025 | Migration milestone | First production traffic moved through Kong. | Source-stated date |
| September 2025 | Migration milestone | APIs already at 90 percent Kong traffic moved to 100 percent. | Source-stated date |
| October 2025 | Migration milestone | The source states 100 percent migration across all environments and APIM decommissioning. | Source-stated completion |
Workload migration matrix
| Workload | Predecessor | Destination | Status by 23 Jul 2026 |
|---|---|---|---|
| Vipps MobilePay API estate handling more than 10 billion monthly API calls across environments | Azure Application Gateway to Azure API Management to NGINX ingress | Azure Application Gateway to Kong Gateway on AKS | Completed API gateway migration and decommissioning |
Implementation and architecture
- A canary proxy split traffic between Kong and APIM during migration.
- Kong configuration uses Kubernetes-native patterns, decK and GitHub OIDC guardrails.
- A summer change freeze slowed the June-to-July migration period.
Known unknowns and contradictions
- The visible publication date of the customer-story page.
- The complete API-by-API migration inventory.
- Any residual NGINX components outside the gateway path.
No missing fact is inferred to broaden the source-supported migration claim.
PlatformTrace analysis
The source supports the named API gateway migration across all Vipps MobilePay environments. It does not establish a broader cloud-platform migration.
Performance, cost, uptime and operational outcomes remain attributed source claims unless independently stated otherwise.
Evidence ledger
- Kong customer story, verified 23 July 2026
Named Vipps MobilePay engineers describe the before-and-after gateway architecture, traffic progression and APIM decommissioning.
- Kong-hosted migration presentation, 11 June 2025
Supporting customer presentation describing the Azure APIM-to-Kong migration chronology and operating model.
Corrections and updates
23 July 2026 — Initial Verified dossier published from the complete five-lane overnight intake and corrected central adjudication. Later milestones will be appended rather than silently replacing this state.