

Neptune Integration Hub Is Now SAP Clean Core Level A and Public Cloud Certified.
SAP teams moving to the public cloud usually face a trade-off: protect the core and slow the migration, or move fast and put upgrade stability at risk. Neptune Integration Hub now removes that trade-off for its own integration layer.
Integration Hub holds two certifications from SAP. On 11 May 2026, it achieved Clean Core Level A, SAP’s highest rating for clean core extensibility, certified for SAP S/4HANA Cloud Private Edition and for RISE with SAP. On 16 October 2026, it also achieved certified integration with SAP S/4HANA Cloud, Public Edition. Both are listed in SAP’s certified solutions directory.
Together, the two certifications change three things for an SAP team:
- Connect to SAP without touching the core.
- Move to the public cloud without rebuilding existing integrations.
- Keep upgrades predictable, because everything runs on released APIs.
Most SAP customers are not choosing between modernizing and protecting the core. They want both: a system that stays upgrade-ready while processes keep flowing across the enterprise. These two certifications are evidence for that, not a claim for it.
What Level A and Public Cloud certification actually mean
SAP’s clean core framework ranks extensibility on four levels, from cloud-ready to not recommended. Level A is the top: cloud development and usage of released APIs only, nothing that touches an internal SAP object or an extension point SAP has not released.
| Level | What it covers | Where it sits |
|---|---|---|
| A | Cloud development and usage of released APIs | Clean, upgrade-stable by design |
| B | Usage of best practice or classic APIs | Clean with more care required |
| C | Consumption of internal objects | Conditionally clean, only when the changelog for SAP objects is applied |
| D | Not clean core | Upgrade-stable, but not recommended |
Integration Hub’s Clean Core Level A certification covers its SAP S/4HANA Cloud Private Edition compatibility: built on released remote and local APIs and released extension points only, with a passed SAP Code Vulnerability Analyzer (CVA) security scan and no reliance on internal SAP objects. That is a design constraint, not a marketing claim. An architecture that stays inside released APIs cannot drift into internal SAP objects later, which is the usual way an extension quietly stops being clean.
The second certification, achieved five months later, confirms Integration Hub as a certified integration for SAP S/4HANA Cloud, Public Edition, SAP’s fully standardized, SAP-operated public cloud deployment model. Private Edition compatibility and Public Edition integration answer two different questions: one is about how deep the extension can reach into a landscape you still control, the other is about running cleanly on the edition SAP operates for you. Integration Hub now carries both marks.


One platform, wherever you are with SAP
Integration Hub’s certifications are not an isolated mark on one product. They fit a pattern across Neptune DXP, the SAP-Native Execution Platform: Neptune Open Edition, the side-by-side edition, carries SAP BAIP certification, and Neptune SAP Edition for on-premise landscapes runs at Level C, the appropriate level for an edition that still works with internal SAP objects on ECC and S/4HANA.
That spread matters because SAP customers are not all on the same deployment model at the same time. Some are still on ECC. Some have moved to S/4HANA on-premise. Some are planning the move to S/4HANA Cloud Private Edition. Neptune’s position is the same regardless of where a customer sits in that journey: native on SAP, connected across the enterprise.
For an architect evaluating Neptune, the practical takeaway is this. Integration Hub lets you connect to SAP without touching the core, move to the public cloud without rebuilding the integrations you already built, and keep upgrades predictable because the extension stays on released APIs the whole way through. None of that requires choosing against SAP’s own roadmap. Where SAP BTP is the right fit for a given scenario, Neptune integrates with it. Where the logic lives inside SAP itself, Neptune already runs there, now with SAP’s own certification behind it.
Closing
If you are planning a move to SAP S/4HANA Cloud Private Edition, or just want to see how your integration layer holds up against SAP’s own clean core bar, the certification record is public. See Neptune Integration Hub in SAP’s certified solutions directory ↗


