nábd Core · the foundation of the nábd suite
One data foundation. Every nábd module reads from it.
Core is the persistent data layer underneath Pay, Ops, and Care. Real-time sync from your SuccessFactors tenant, your S/4HANA Public Cloud, and the government portals your operations rely on — Muqeem, GOSI, MOL. Built on SAP BTP. Included with every module purchase.
The principle
One foundation. Many readers. No fragmented integrations.
Every nábd module needs the same picture of your enterprise — who works for you today, where, under what contract, paid through which entity, with what residency status, against which budget. Three sources hold that picture authoritatively: SuccessFactors, S/4HANA Public Cloud, and the government portals your operations file with daily.
If every nábd module integrated directly with each of those three sources, the result would be a brittle mesh — three modules × three sources = nine integrations to build, monitor, and re-validate every time a source schema changes. Core collapses that into one. The modules read from Core. Core syncs from the sources.
The picture
Core, with the apps it carries.
Core is the foundation. Pay, Ops, and Care live on it — each its own product, all reading from the same shared data layer.
nábd Pay
Payroll engine
nábd Ops
Operating layer
nábd Care
Employee fabric
The foundation
nábd Core
One persistent data layer. Read by every app, never bypassed.
nábd Pay
Payroll engine
nábd Ops
Operating layer
nábd Care
Employee fabric
The foundation
nábd Core
One persistent data layer. Read by every app, never bypassed.
Core in the centre. Pay, Ops, Care around it. No arrows — the relationship is the composition.
Three flows, defined
Each direction does one job. No ambiguity.
Read-only sync
Sources → Core
Core pulls. It never writes back to SuccessFactors, S/4HANA, or the government portals. Those sources stay authoritative and untouched by Core itself.
Real-time read
Modules → Core
Pay, Ops, and Care read from Core every time they need master data. No nightly batch. No reconciliation gap between modules.
Module-by-module
Modules → Sources
When a module needs to write back — Pay posting payroll results, Care closing an HR case — it writes directly to the source through its own integration, not through Core.
The result: one current view of your operations available to every module, three integrations Raptors maintains end-to-end rather than nine each customer integrates module-by-module, and zero risk of Core corrupting an authoritative source.
How Core ships
Included with every module. Not sold standalone.
Core is the foundation of the suite. Every nábd module purchase includes it. You do not configure Core separately, you do not contract for it separately, and you do not run it as a standalone product. Deploy nábd Pay, Core ships with it. Deploy Pay and Ops, the two modules share one Core instance — which is precisely how they maintain a consistent picture of your enterprise.
The modules — Pay, Ops, Care — are the products you buy. Core is how they work.
Architecture commitments
SAP-grade infrastructure, by design.
Built on SAP BTP
Standard SAP cloud architecture — same security posture, same compliance framework as the rest of your SAP estate.
Multi-tenant SaaS
Your data isolated in a tenant addressable to your organisation. No shared schemas. No cross-customer exposure.
Single sign-on with SuccessFactors
Your users sign in once. The same identity reaches Core and every nábd module.
Continuous sync from sources
Schedule and frequency tuned to source-system limits — most master data current within minutes, not nightly.
Audit-trailed reads
Every write a module makes through Core's data model is recorded. The audit trail is queryable.
MENA data residency
Core runs in SAP BTP regions that satisfy Egyptian PDPL and Saudi PDPL data-residency requirements.
Next step
Talk to us about Pay, Ops, or Care. All of them powered by Core.
A working session with the team that runs nábd. We map your gaps and show you what a deployment looks like.