RMOZ / platform
Keep your systems connected.
Link selected records to the software your team uses. Plan identifiers, permissions and events before connecting the workflow.
Connect business events, not just systems
Integration teams need agreement on what an event means, who owns it and when another system may act on it. RMOZ starts with source-of-truth mapping across business applications, document stores and the ledger.
Specify the interface contract
Identifiers, schema versions, timestamps, status meanings and authorisation boundaries are defined before integration starts. Authentication, endpoints, SDKs and rate limits are documented for each client environment.
Design for duplicates and partial failure
Each workflow receives an authorised event, validates it, records the decision and reconciles the downstream result. Idempotency, retries, replay protection and failure queues are built in, and a timeout is never treated as success or failure.
Prove portability and a usable exit
Every integration is designed for portability: records can be exported, evidence references are preserved and status history moves with the data if you change providers.
Continue the journey
FAQ
Questions, answered
Where are the API reference and SDK downloads?
API references and SDKs are provided to clients during onboarding. To start, download the integration checklist or contact our team.
Does interoperability require moving all data to a ledger?
No. A design may exchange limited events or evidence references while keeping operational and sensitive records in their existing systems.
YOUR NEXT STEP
Build your next step
on trust.
Find the right starting point for your assets, records and business.
Find your use case