One place per platform
Every service on the estate writes its own documentation here rather than into a repository nobody else reads.
Documentation
Where every platform on the estate writes its own documentation.
A document and knowledge store with ingestion, search, retention and per-tenant access control, so the runbook for a service is not in one engineer’s head. Its database was provisioned on the fleet on 6 September 2026 and is covered by the same replication and backup arrangements as every other service; the application is still under development and the deployed instance runs against a development database.
Who it is for. Used by RODMENA for its own documentation and runbooks. Not sold; listed so the catalogue is complete.
Every service on the estate writes its own documentation here rather than into a repository nobody else reads.
Access is governed by Identity and Auth, so a document is readable by exactly the people who should read it.
Documents carry a retention position rather than accumulating until someone deletes the wrong thing.
The product site has the documentation and the way in. For procurement questions, a pilot or an integration, talk to us directly.