Audarel is pre-release. There is no trial or self-service signup yet.
Know why the data
can leave.
Executed data-use terms should become controls a release is actually checked against, not a PDF nobody opens. That is what we are building. We are talking to the teams doing this review by hand today.
In development · speaking with early teams · no trial yet
A complete, reproducible release record, from executed terms to signed evidence.
The same confirmed controls and release artifacts produce the same result.
Named reviewers own confirmations, exceptions, approvals, and release authority.
Every evidence pack retains hashes, versions, decisions, and source citations.
A policy document is not an operating control.
Audarel connects the executed agreement to the proposed data, recipient, purpose, environment, users, retention period, and transfer method. AI can extract candidate terms; a steward confirms them; deterministic code evaluates the release.
Illustration · not a live accountGenomics cohort · release 2048
Evidence completeExecuted DUA and amendment version lockedCalculation and receipt dates preserved
ReadyDUO purpose and population terms confirmedCompared to signed closing evidence
ReadyPayload fields checked against the allowlistReviewer action remains explicit
ReadyDAC approvals and evidence hashes preservedSource document hash retained
ReadyA mockup of the release record Audarel is designed to produce. It is not a screenshot of a working account.
Source-cited controls
Each confirmed control keeps the agreement clause, citation, reviewer, and version that made it operational.
Explainable preflight
Every block or condition identifies the proposed value, expected term, affected fields or rows, and rule reference.
Defensible evidence
Approvals, exceptions, attestations, connector state, policy bundles, and release runs stay bound to one record.
From signed terms to governed release.
Replace the spreadsheet, shared-drive folder, email approval chain, and last-minute query review with one versioned operating record.
Confirm the agreement
Upload the executed DUA, DSA, DPA, approval, or amendment. Review extracted purpose, fields, population, users, retention, redisclosure, publication, environment, and transfer terms.
Preflight the release
Attach the schema, payload, authorized-user list, or query manifest. Evaluate the exact proposed release against confirmed terms and current institutional controls.
Approve and prove
Route tiered or quorum approvals, resolve exceptions, generate policy bundles, detect connector drift, and freeze signed JSON and PDF evidence packs.
The agreement-to-release control plane.
Audarel focuses on the work that broad catalogs, CLM systems, ticket queues, and warehouse permissions leave disconnected: proving that this specific use of this specific data is authorized now.
Data-use agreement management
Version executed agreements and amendments; extract candidate obligations; keep reviewer-confirmed controls tied to source clauses.
Explore the workflowRelease preflight
Evaluate purpose, recipient, environment, transfer, fields, rows, retention, publication, redisclosure, users, dates, and DUO terms before data leaves.
Explore the workflowData access governance
Connect business purpose and contractual authority to access decisions without pretending another static role is sufficient context.
Explore the workflowPolicy as code
Compile confirmed controls into versioned, machine-readable policy bundles and preserve the exact input and decision version for re-performance.
Explore the workflowApprovals and exceptions
Configure sequential tiers, all/any/quorum groups, attestations, exception owners, due dates, remediation, and reviewer notes.
Explore the workflowRelease evidence packs
Generate encrypted, hashed PDF and JSON snapshots containing controls, artifacts, findings, runs, approvals, exceptions, policies, and connector state.
Explore the workflowBuilt for the teams who sign off before data moves.
The workspace gives privacy, legal, research, security, and data owners a common record without collapsing their distinct responsibilities into one opaque score.
Research data governance
Operationalize DUAs, DUO limitations, Library Cards, DAC quorum decisions, controlled-access cohorts, and time-bounded approvals.
See the fitPrivacy and legal operations
Trace each proposed disclosure to confirmed purpose, recipient, retention, transfer, redisclosure, and publication terms before approval.
See the fitData platform and clean-room teams
Produce a machine-readable desired policy, bind it to the approved release, and detect drift between governance intent and connector state.
See the fitChoose by evidence continuity, not feature count.
A CLM repository, a ticket workflow, and a broad governance suite can each hold part of the process. Compare whether the exact agreement, proposed data, deterministic result, human authority, and enforcement state remain joined.
| Buying criterion | Audarel | Manual workflow | Enterprise suite |
|---|---|---|---|
| Primary job | Prove a proposed release matches confirmed data-use terms | Coordinate documents, tickets, spreadsheets, and email | Catalog, classify, secure, and govern broad data estates |
| Policy source | Executed agreement clauses plus institutional controls | Reviewer interpretation across disconnected artifacts | Central policies, tags, roles, and platform configuration |
| Decision proof | Inputs, rule version, findings, approvals, exceptions, hashes | Depends on local process discipline | Depends on purchased modules and implementation |
| Human authority | Explicit steward confirmation and accountable approval tiers | Commonly embedded in email or ticket status | Configured roles and workflow owners |
| Start path | Upload one agreement and synthetic release | Assemble a process and train every participant | Discovery, taxonomy, integrations, configuration, rollout |
There is no price here yet.
Audarel is not generally available, so publishing a monthly figure would imply something you can buy today. When there is a plan to sell, it will be published on this site. Until then, get in touch and tell us what your release review actually costs you now.
Early access and design partners.
Tell us how data releases get reviewed where you work.
We are more interested in the workflow you have now, and where it breaks, than in whether you are ready to buy anything.Questions before the first release.
Does Audarel decide whether an agreement is legally sufficient?+
No. AI may propose structured terms from a document, but an authorized steward confirms every operational control. Your legal and governance teams remain responsible for interpretation and release authority.
Does it replace a data catalog, IAM, or clean room?+
No. Audarel supplies the agreement-aware decision and evidence layer. It can produce policy bundles and track connector state, while catalogs, identity systems, warehouses, and clean rooms continue to enforce technical access.
What can a release preflight check?+
Confirmed purpose, recipient, environment, transfer method, dates, retention, authorized users, field allowlists and requirements, row predicates, publication, redisclosure, DUO codes, Library Cards, approvals, and required evidence.
Can we reproduce an old decision after the agreement changes?+
Yes. Agreement versions, release runs, decision-engine versions, artifact hashes, findings, approvals, exceptions, and evidence snapshots are preserved so reviewers can compare what changed.