DOVU

Nobody has to take your word for it.

How a DOVU record works.

A DOVU record is a set of signed steps, kept where the people it concerns cannot edit it. Your software does not write it about itself.

Records are written to Hedera, a public ledger. Once written, nobody can change or delete them, including DOVU.

  1. Step 01

    You define the process

    Who does what, in what order, and what counts as evidence at each step. DOVU publishes the version before anything runs, so there is something to check against. This is a Flow.

  2. Step 02

    People and systems do the work

    DOVU records each step as it happens, signed by whoever did it. Before each step it checks Authority Trail for the permission behind it.

  3. Step 03

    Anyone can check it later

    The record sits outside your systems, on a public ledger neither you nor DOVU can edit. A regulator, a buyer or a court can check it without asking either of you.

What a record contains

What anyone can check without asking you.

Who acted

The person or system, in the role they held, signing for their own step.

What they did

Structured evidence, captured in the shape the process defined.

Whether they were allowed

The permission in force at that moment: who granted it, its limits, whether it had been revoked.

When

A timestamp anyone can check, ordered against every other step.

What it refers to

The exact version approved. Not "the latest".

Where it lives

Outside the systems that did the work. Revoking access never rewrites what already happened.

Try it

Play every role, then check the record without us.

It runs in your browser. Play each participant, sign, revoke a permission, then inspect what the record kept. Everything is simulated.

Try the 3-minute demo

Next step

What can't you prove today?

Thirty minutes with our CEO. Bring the problem.

Book a call Try the 3-minute demo