DRAFT — requires approval by NexMena before publication.
Why this page is shortLink to the section: Why this page is short
Most corporate responsibility pages describe activity that has not happened, or describes a single donation as a programme. We would rather publish the commitments now and add the record as it accumulates — a page that grows is more credible than one that opens complete.
Technical capability that stays in the regionLink to the section: Technical capability that stays in the region
Our engagements end with knowledge transfer as a deliverable, not as a courtesy. Capability that leaves with the supplier is a dependency sold as a service.
Arabic as a working technical languageLink to the section: Arabic as a working technical language
We publish technical content in Arabic that is written or human-reviewed, never machine-translated. A region cannot own its technology in a language it only consumes documentation in.
Security knowledge shared beyond our clientsLink to the section: Security knowledge shared beyond our clients
Reference architectures, methodology and field notes are published openly. A regional organisation that never becomes a customer should still be measurably better defended for our having written.
Infrastructure decisions carry an energy costLink to the section: Infrastructure decisions carry an energy cost
Capacity planning, virtualisation density and cloud region choice all have an energy footprint. We treat that as an architectural input, and we will not claim more than that until we can measure it.