Skip to content

Revoluzen Flow v1.0.1 — Apache-2.0

Prove · Verifiable receipts

Revoluzen Evidence

Signed, independently verifiable receipts for what ran. Hand someone the receipt and the public key and they can check it themselves — offline, with no access to our software, our servers or your systems.

Revoluzen Evidencereceipts / run 4812 / verify
receipt · run 4812ingest_orders_dailysigned 02:14:09 UTC
pipeline
ingest_orders_daily · v14
completed
2026-10-18T02:14:09Z
code
git:8e1c4a2
inputs
orders sha256:91f3…a0c2 · refunds sha256:4be7…17d9
output
gold.fct_orders · 1,261,118 rows · sha256:c07a…5e31
checks
37 kinds · 0 findings
signature
ed25519:3f9a2c…c71d
chain · 4811 → 4812 → next2.1 KB · json
verify · offlinekey · finance-data.pub
  • signature valid for this key
  • content hash matches the receipt
  • chain intact · prev 4811 → 4812
  • no network access used
resultverified

Verification needs the receipt and a public key — nothing else. Not the pipeline, not the database, not us.

License
Open source
Signature
Ed25519
Verification
Offline
Verifier
Standalone tool

Who it is for

For regulated teams, data processors and anyone who has had to reconstruct what a job did eight months after it did it.

01Where it sits

The prove plane

Each product is adoptable on its own; together they share one catalog, one permission model and one run history.

01

Move

  • Flow
  • Flow Enterprise

02

Govern

  • Catalog

03

Answer

  • Studio

04

Operate

  • Console
  • Mobile

05

Prove

  • Evidence
How the planes connect
02Capability

A receipt, not a log line

A log says a system believes something happened. A signed verifiable execution record lets a third party confirm it, without trusting the system that produced it.

capability · 02Evidence
  1. 01Covers inputs, outputs, code version and result for a run
  2. 02Signed with Ed25519 at the moment of execution
  3. 03Tamper-evident: any change to the record invalidates the signature
03Capability

Verification that does not need us

This is the part that matters. If verifying a receipt required our server, the proof would only be as durable as our company. It does not.

capability · 03Evidence
  1. 01Verification needs the receipt and a public key — nothing else
  2. 02The verifier is a standalone open-source tool
  3. 03Works offline, in an air-gapped environment, years later
  4. 04Proof outlives the subscription, the vendor and the deployment
04Capability

What it is good for

The situations where 'trust me, it ran' has a real cost.

capability · 04Evidence
  1. 01Regulatory submissions: send the figure and the receipt together
  2. 02Processing on behalf of clients: show exactly which records a job touched
  3. 03Disputes: settle what ran from signed evidence, not expired logs
  4. 04Internal controls: evidence that a control actually executed
05Specification

The details, in one table

The facts a technical evaluator checks first, without having to read a datasheet.

LicenseOpen source
Signature schemeEd25519
VerificationOffline, receipt + public key
VerifierStandalone, independent of the platform
Key custodyYours

Open source

The verifier stands alone

Revoluzen Evidence ships as its own open-source package, separate from Flow, so an auditor can verify a receipt without installing the orchestrator at all.

Open-source commitments
06Before you commit

What this does not do yet

You would find these out eventually. Finding them out now is cheaper for both of us.

01

A receipt proves what the executing system recorded and signed. It is strong evidence of execution; it is not a proof that your business logic was correct.

02

Key custody is your responsibility. If you lose the private key, you cannot sign new receipts; if you leak it, the signature stops meaning anything.

03

Receipts are most useful when they are retained deliberately. They are evidence, which means somebody has to keep them.

Run it yourself, then decide.

Revoluzen Flow is Apache-2.0 and installs in one command. If it fits, we can talk about the parts that are not open source.