Access that respects your boundaries. A record that cannot be quietly rewritten.
Row-level access, an append-only journal, and a deployment model built around your own sovereignty.
Row-level access
Access is controlled row by row, by service domain, custodian and area, so a person sees only the assets their role covers. Not a screen-level permission a report can bypass, it applies at the level of the data itself.
A chain you can verify, not just trust.
TodayEvery change is journalled with who, when, why, and the value before and after. Each entry carries the hash of the one before it, computed with real SHA-256, right here in your browser.
Try it: edit an entry, then verify
Real SHA-256, via crypto.subtleEach hash is computed from the previous entry's hash and this entry's fields. Edit "What changed", "Before" or "After" on any entry, then verify, to see exactly where the chain breaks.
Data sovereignty, by design
TodayCoreva is deployed into your own landscape, not a shared multi-tenant service, so your data and your identity provider stay yours. A sovereignty setting refuses real data outside the region you choose.
The upgrade contract
ComingA kernel and register that are always on, with modules above them for prioritisation, investment, finance, spatial, compliance and integration. Switching a module on or off by configuration, with no code change and a test proving the rest keeps working, is under way, the same discipline that already gates a new asset class going live. See the module diagram on the Platform page.
Independent assurance, honestly tracked
What has not yet been commissioned. Each "Today" capability on this site is built, working, and covered by the platform's automated test suite. It has not been proven at Australian production scale, and several items behind it, an independent security test, a formal accessibility audit, an Australian-region deployment, are still to be commissioned.
Ask us to walk through the journal and the decision log
See a change raised, journalled, and verified end to end.