AquaNode · Provable Data Governance.
AquaNode is a self-hosted governance layer between your data and everyone who uses it. Define who may access or change which records, under which terms. Every accepted interaction becomes part of a verifiable record. Your data can stay in your existing storage.
A file may sit in cloud storage, be changed by an application, shared with a partner, and used by an AI agent.
Each system controls access and keeps its own record, leaving no single view of who was allowed to do what, under which terms, and what actually changed.
One example: a counterparty risk record inside a bank.
AquaNode applies the same governance layer to people, applications, and AI agents.
Before a change is accepted, AquaNode checks who is acting, what they are allowed to do, and under which terms. If accepted, the interaction becomes part of the verifiable record.
Access
People · Applications · AI agents
AquaNode
identifies the actor · checks the terms
accepts or rejects the write · records what happened
Storage
existing storage · your own infrastructure
AquaNode does not run your workflow. It governs the data your workflow touches.
That can be your ERP system, a partner application, a document workflow, or your own software.
AquaNode uses a signed access grant to define the permission. The grant carries the terms under which the action is allowed. Before a write is accepted, AquaNode checks the grant against the rules governing those records.
Today
Counterparty
risk record
Each system keeps its own access rules and its own log.
With AquaNode
Risk engine
wants to update the counterparty risk recordAllowed
Write accepted.
Signed entry added to the record.
Grants can be scoped, time-bounded, and revoked.
Auditable access records
Every accepted action leaves a signed record of who acted and under which terms, independently verifiable by an auditor or partner.
Identifiable actors
People, applications, and AI agents act under their own cryptographic identity, so accepted actions stay attributable to the actor that performed them.
Contract-based access
An access grant carries the terms under which an actor may act and keeps them connected to the resulting record.
Each accepted change becomes a signed revision, cryptographically linked to the one before it. Alter an earlier revision afterwards, and verification fails at that point.
created · verifies
changed · verifies
altered afterwards
no longer verifies
The break becomes visible at exactly that step.
Built so anyone with the record and the relevant public keys can verify the chain, even offline and without an AquaNode account.
How much sits inside the node depends on how you deploy it.
Default deployment
Content + record
AquaNode can keep the content together with its verifiable record and keep both available and synced.
Notary mode
Fingerprints + identities
The content remains in your existing storage. AquaNode retains the cryptographic fingerprints and identity information needed for verification.
Either way, AquaNode can run on infrastructure you control and in the jurisdiction you choose. No public ledger is required.
When someone needs to verify a record, its fingerprints can be checked without handing over the underlying content itself.