Use case · Audit & compliance
Regulated reporting with verifiable evidence
Produce regulatory and board figures from pipelines that leave a signed, offline-verifiable record of every run — so the evidence behind a number survives longer than a dashboard screenshot.
- Evidence
- Ed25519-signed receipts
- Verification
- Offline, no vendor access
- Products
- Flow · Evidence · Studio
- Status
- Flow and Evidence today; Studio early access
Who it is for
For finance, risk and compliance teams who submit figures a reviewer may question months later, and who are tired of answering with a reconstruction.
What this looks like from the inside
A reviewer asks which inputs produced a figure eight months ago. The pipeline has been edited since, the logs have rotated, and the honest answer is a screenshot and a reconstruction. That is not evidence; it is a story about evidence.
Hosted tools make it worse: the processing happened on infrastructure you cannot inspect, under a retention policy you did not set.
Drawn, not described
The one thing the prose cannot do: show the moving parts and where the boundary is.
01 · run
ingest_orders_daily
- inputs · orders, refunds
- outputs · fct_orders · 1,303,343
- code · git:8e1c4a2
02 · receipt
ed25519:3f9a…c71d
tamper-evident · any change breaks the signature
signed at completion03 · figure
Q3 net revenue
paginated report · page 4 · metric: net_revenue
Step by step
In the order it actually happens.
- 01
The reporting pipeline runs on your infrastructure
Extraction, conformance and the aggregation that produces the submitted figure run as explicit steps in Revoluzen Flow. Each step records its inputs, its outputs, the code version that ran and its result.
- 02
Steward checks the run before anything downstream trusts it
Reliability findings — a step that silently changed its row count, a contract that no longer holds — are raised against the causing step. 37 finding kinds, raised before the figure is used.
- 03
The run is signed the moment it completes
Revoluzen Evidence signs the execution record with Ed25519. Any later change to the record invalidates the signature, so the receipt is tamper-evident by construction.
- 04
The figure and the receipt are filed together
The paginated report from Revoluzen Studio carries the figure; the receipt is retained beside it, with the standalone verifier, for as long as your retention policy requires.
- 05
A reviewer verifies it themselves
Given the receipt and the public key, the reviewer runs the open-source verifier offline. No access to your systems, no access to ours, no live subscription — and no walkthrough of your warehouse.
What actually changes
| Dimension | Today | With Revoluzen |
|---|---|---|
| What you hand a reviewer | A dashboard screenshot and a verbal reconstruction of what the pipeline probably did. | The figure, the signed receipt and a public key. They verify it; you do not narrate it. |
| How long the evidence lasts | Until the logs rotate — typically ninety days — or until the pipeline is edited. | For as long as you keep the receipt. Verification does not depend on logs, the vendor or the deployment. |
| Where the processing happened | On a vendor's infrastructure, under their retention policy, outside your inspection. | On your own servers, with every step's inputs and outputs recorded. |
Which product does what
Each product is adoptable on its own; together they share one catalog, one permission model and one run history.
Revoluzen Flow
Runs the pipelines that produce the reporting dataset, with per-step inputs, outputs and code version recorded on every run.
Product pageRevoluzen Evidence
Signs each run with Ed25519 so the record is tamper-evident and verifiable by a third party without access to your systems or ours.
Product pageRevoluzen Studio
Produces the paginated, scheduled reports from a governed model where every figure traces to its metric and query.
Product pageWhere it runs
Self-hosted on an internal server with your identity provider in front. Receipts are retained alongside the report outputs; the standalone verifier is kept with them so verification never depends on a live subscription.
What you end up with
- 01A signed receipt for every run that produced a submitted figure
- 02Verification by the reviewer themselves — receipt plus public key, offline
- 03Reports whose numbers resolve to a defined metric, not an ad-hoc query
- 04Evidence that outlives log retention, the vendor and the deployment
The honest limits
You would find these out eventually. Finding them out now is cheaper for both of us.
A receipt proves what the executing system recorded and signed. It is strong evidence of execution, not a certification that your business logic was correct.
Revoluzen Studio is in early access; the pipeline and receipt layer are available today.
Revoluzen does not hold SOC 2 or ISO 27001. For a self-hosted deployment the operational controls are yours, and we will help document that.
Asked about this scenario
Can a regulator verify a Revoluzen receipt without Revoluzen software?
Yes. A Revoluzen Evidence receipt is an Ed25519-signed record that verifies with the receipt and the corresponding public key using a standalone open-source verifier, offline, with no access to Revoluzen's servers or an active subscription.
What does a verifiable execution record contain?
A Revoluzen verifiable execution record covers a run's inputs, outputs, code version and result, signed at the moment of execution so that any later change to the record invalidates the signature.
Does using Revoluzen for regulated reporting require sending data to Revoluzen?
No. Revoluzen is self-hosted; the pipelines, receipts and reports stay on your infrastructure, and the software makes no outbound connection to Revoluzen.
Adjacent scenarios
Keep data in-country, in-network
Data residency and sovereignty
Run pipelines, a lakehouse and analytics entirely inside your own network — with no hosted control plane, no telemetry and no outbound dependency — so residency obligations are met by architecture rather than by contract.
Dashboards without the export
On-premises analytics with governed answers
Dashboards, paginated reports and a governed query layer that run inside your network against your own warehouse — where every number on a screen can say which metric and which query produced it.
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.