Platform and architecture

One physical truth. Governed lenses on top of it.

Every function views the same asset through its own lens, maintenance, finance, network, compliance, without copying the data or disagreeing about what it is.

One record. Every lens re-derives from it.

Every asset is held at its class's own physical grain, a bridge deck, a carriageway segment, a stormwater pit. Change the record once, and every lens above it re-derives.

Today

Provenance on every value.

Today

Every value carries its state (supplied, known absent, or not sourced, never a silent null), how it was obtained, its source, and a confidence score. A structure that cannot be scored with enough confidence is shown, not hidden, with exactly what is missing.

Attribute detail, BR-0042

Deck condition rating

Value
3, fair
State
Supplied
Source
2025 level 2 inspection
Confidence
High

Confidence is a word and a colour on screen, never a bare number pretending to precision the data does not have.

Reproducible decisions.

Today

A prioritisation run is frozen the moment it is published, and can be reproduced against its own recorded inputs years later.

Try it: reweight the ranking

Sample assets, Northfield network
Condition40%
Criticality35%
Risk25%

    Weights are normalised to 100%. The position range shows how far a rank could move given each asset's confidence band. Sample data, illustrative only.

    Governance and access.

    Today

    Access is controlled row by row, by service domain, custodian and area. Every create, update and withdrawal is written to an append-only change journal with who, when, why, and the value before and after. Each entry carries the hash of the one before it, so a verifier can prove the chain is unbroken. Coming scheduled verification with an alert, and anchoring the chain head outside the database. Try the live version on the Security and trust page.

    Standards, honestly stated.

    Today

    Coreva computes fair value, remaining service potential and depreciation from physical facts and an accounting policy you control, reconciles them to your ledger, and never posts to it. Every figure that applies a reading of AASB 13, AASB 116, AASB 136 or the relevant Treasury guidance says, on screen, that the reading has not yet been independently confirmed. In progress an independent valuer's and auditor's confirmation.

    A new asset class in 10 steps.

    Today, proven by test

    Adding a class Coreva has never shipped, a water main or an electricity line, is a configuration exercise, not a development project. Build one below.

    Try it: build a class card

    Building

    No code change. This sequence is proven end to end by the automated test that gates every Coreva release.

    Modular by design.

    Coming

    A kernel and register that are always on, with prioritisation, investment, finance, spatial, compliance and integration as modules above them, and Coreva Plans plugged in beside it. Switching a module on or off by configuration, with no code change, is under way.

    Deployment.

    Today

    Coreva 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 set.