Adyen is increasing its influence over the open-source technology used to operate large-scale payment infrastructure. On 11 November, the Cloud Native Computing Foundation announced that the Amsterdam-based payments company had joined as a Platinum End User member. The move includes representation in the organisation’s governance and technical advisory structures, alongside Adyen’s contribution of a container-access auditing tool. It is a technology and governance development, not an acquisition, a new bank licence or a customer-facing payment method.[1]
The scale makes the infrastructure question substantial. CNCF says Adyen processed €1.39 trillion in payments volume during 2025 and runs more than 100 Kubernetes clusters globally. The trillion-euro number is the face value of payments processed, not company net revenue, profit or client funds held on balance sheet. Confusing it with sales would massively misstate the economics of a payment service provider.[1]
Why regulated financial infrastructure needs an audit trail
Modern payment processors operate distributed systems spanning authorisation, fraud signals, transaction routing, reconciliation and merchant reporting. Engineers periodically need production access to diagnose incidents, but unrestricted access can create security and audit risks. Adyen’s open-sourced kubectl-rexec tool is designed to improve accountability around Kubernetes container access while retaining the speed required for operational response. A tool release is a capability announcement; it does not by itself establish that every production access path has become risk-free.[1]
Scale and the meaning of each metric
| Disclosed measure | Value | Correct interpretation |
|---|---|---|
| Processed payments in 2025 | €1.39tn | Underlying customer payment volume |
| Kubernetes clusters | 100+ | Technical infrastructure footprint |
| CNCF membership | Platinum End User | Governance role, not a regulatory licence |
| Tool contribution | kubectl-rexec | Access auditing, not a payment product |
The foundation highlights Adyen’s use of Kubernetes, Cilium, Prometheus and OpenTelemetry. These projects address different layers of operating a distributed platform, including scheduling, networking, observability and metrics. Standardised components can make it easier to avoid proprietary infrastructure dependencies, yet every deployment still requires hardened configuration and tested incident procedures. For financial institutions, availability and security have direct implications for settlement timing and merchant confidence.[1]
Membership brings a seat on the CNCF Governing Board and an appointment to the End User Technical Advisory Board. That gives Adyen a forum in which to explain requirements from high-volume regulated operations. It does not mean the foundation has endorsed Adyen’s commercial services or certified compliance with payment regulations. Governance influence and regulatory assurance are independent concepts.[1]
Operational risk points for payment and broker technology
| Layer | What operators need to test |
|---|---|
| Authorisation | Service continuity through incidents and traffic spikes |
| Production access | Named access, approvals and durable logs |
| Networking and observability | Reliable alerts and failure detection |
| Reconciliation | Accurate transaction records after failover |
| Change management | Rollback, incident drills and independent review |
The wider brokerage lesson
Brokers increasingly rely on payment processors, cloud infrastructure and external fraud services for deposits and withdrawals. A vendor’s engineering choices therefore influence trading access even if the broker’s matching engine works correctly. Adyen’s development points to a competitive field in which resilience and verifiable operations matter alongside merchant pricing. Future evidence should be measured service availability, security outcomes and ecosystem adoption—not a speculative uplift in Adyen revenue from membership alone.[1]
Sources & further reading
- CNCF Welcomes Adyen as Platinum End User Member Cloud Native Computing Foundation · Accessed 12 Nov 2026