DOVU

Nobody has to take your word for it.

Records of who did what, and who allowed it, that anyone can check.

DOVU writes each permission, action and approval somewhere neither party controls. Regulators, buyers and courts can check the facts for themselves, without seeing anything you haven't chosen to share.

Record DEMO-EVT-002
Who
Atlas Payments Agent automated · acting for Treasury
What
Approved payment · £1,200
Allowed by
Priya Morgan · limit £5,000 granted 14:00:00 UTC
When
2026-09-09 · 14:00:30 UTC
Checked by
Anyone. Written by neither party.

Permission valid at the moment of action. Revoked 14:02:00 UTC. Both remain true.

Example record. A payment agent acted within a limit its manager granted. The limit was revoked two minutes later. Both facts stay on record.

Backed by

  • InMotion Ventures The venture arm of Jaguar Land Rover.
  • Creative UK The national body backing the UK creative industries.
  • Hedera Foundation Stewards of Hedera, the public ledger our records are written to.

In plain terms

Businesses make claims every day.

  • Claim A payment was approved.
  • Claim An agent was allowed to act.
  • Claim Carbon was removed.

Those claims usually live in the business's own system, where records can be changed.

DOVU writes the record somewhere it cannot be edited later: what happened, who did it, who allowed it, and when. Anyone can check it.

The problem

Every system writes its own account of what it did.

When a regulator, a customer or a court asks whether something happened the way you say it did, you hand over a file your own software wrote. They have to accept your account of events. Most of the time that is fine.

When money, ownership or liability is on the line, it is not.

DOVU records the same events somewhere neither you nor the person questioning you controls. Your claim stops being a claim.

Underneath every industry

Two parts of one platform.

  • Permissions

    Authority Trail

    Who was allowed to do what, on record.

    About Authority Trail
  • Processes

    Flow

    Reusable instructions for a process, with a record of every step.

    About Flow

How it works

How a record is made.

Read the long version
  1. Step 01

    You define the process

    Who does what, in what order, and what counts as evidence.

  2. Step 02

    People and systems do the work

    DOVU records each step as it happens, signed by whoever did it.

  3. Step 03

    Anyone can check it later

    Revoking a permission stops future actions. It never erases past ones.

Confidentiality

What's public is proof. Not your data.

We don't ask you to publish your business data, your customer records or your commercial terms. What goes on the public record is narrow: that an action happened, when, and that it was authorised.

The evidence itself, the documents, the numbers, the relationships, stays inside your systems. You decide who sees it and when. The public record proves a specific fact existed at a specific time. It doesn't reveal what that fact says.

Next step

What can't you prove today?

Thirty minutes with our CEO. Bring the problem.