Platforms

Platforms

Recommended Platforms & Platform Mesh

Platform Contributors Scope License URL
ApeiroRA SAP, European Union Cloud, Edge, OnPrem Open Source (NeoNephos + CNCF) https://apeirora.eu
CNOE Cisco, Amazon Cloud Open Source (CNCF) https://cnoe.io
openvela Microsoft, Alibaba, Xiaomi Cloud, IoT Apache License, Version 2.0 https://github.com/open-vela
PlatformMesh SAP, Kubermatic REST API Open Source (NeoNephos) https://platform-mesh.io
Agentgateway Solo.io MCP & A2A Open Source (CNCF) https://agentgateway.dev

We recommend Apeiro Reference Architecture (https://apeirora.eu) to unify your services from Hardware to Software, deploying with Kubernetes’ declarative power across any Cloud and Edge!

Architecture

Internal Developer Platform

Apeiro Platform Mesh

The high-level goal of the Apeiro Reference Architecture is to enable development and operation of applications and services across public clouds, private clouds, and the edge - the cloud-edge continuum. The use cases for these applications and services should be diverse and unrestricted, catering to end-users, other applications and services, IoT scenarios, and beyond.

The Apeiro Platform Mesh defines an environment that allows service providers to offer services of any kind and service consumers to discover those services, order capabilities, and control their lifecycle.

The Apeiro Reference Architecture defines and implements the “Platform Mesh” that enables developers to select and utilize the needed and preferred services from various service marketplaces. It does not make any assumptions about these services or the marketplaces, nor does it mandate the use of any specific services. Instead, it offers a mesh and the essential contracts that allows service providers to offer their services freely and enables service consumers to discover, order, and use these services.

This framework aims to transcend the traditional layered approach of strictly separating IaaS, PaaS, and SaaS in past infrastructures. Both higher-level and lower-level services are provided and managed through the same mechanism.

The reference architecture includes several common, but optional services. For a comprehensive list of these projects, visit the Apeiro Reference Architecture website. For example, Apeiro offers a Kubernetes environment through the Gardener project, but its use is not mandatory for applications. Other Kubernetes providers can also offer their services within the mesh. This flexibility gives developers more choices and helps prevent lock-in to a particular service supplier.

Components

Component Platform Engineer Developer Manager Auditor
Platform Mesh (kcp) builds, provisions services discovers, consumes services reviews service catalog audits service access
Data Fabric (ORD) operates, manages publishes, discovers data/API understands data flow audits data lineage
AI-Native Platform designs, maintains consumes AI services gets insights checks compliance
Operations (Greenhouse) operates, optimizes monitors, debugs gets insights (dashboard) audits system logs
Security (Heureka) configures, hardens consumes secrets, fixes CVEs reviews compliance status audits compliance
Lifecycle (OCM) provides templates/tools packages, deploys software n/a audits SBoM
Microfrontends provides framework builds, extends UI provides feedback n/a
Project Onboarding automates, onboards requests, uses approves n/a
Baremetal (IronCore) manages hardware (via API) n/a (abstracted) n/a audits physical assets