Lyberty
← Surfaces01 Campaigns02 Relationships03 Finance04 Operations05 Artifacts06 Governance
Surface 06 · GovernanceReplaces the job of: Vanta · Drata · Auth0 · OneTrustLive in all deployments

Approvals and receipts captured while the work happens.

Lyberty records who approved a launch, which rule allowed it, what changed, and where the evidence came from. When finance, legal, or an auditor asks, the answer is a link instead of a reconstruction.

Read the docs
What this view gives you

Known actor for every action

Every person, workflow, and integration has a known identity; no shared credentials.

Approval workflows native

Risky actions require the right approval before they happen.

Audit trail while work happens

Evidence is recorded during the launch, close, or workflow instead of rebuilt weeks later.

Frameworks built in

SOC 2, ISO 27001, GDPR, CCPA, and SOX control mappings can be prepared from the evidence already captured.

Auditor portal

Read-only link with revocation. No more 200-row CSVs over email.

Work this can reduce
TaskSimilar toolsLyberty
SOC 2 / ISO prepVanta / Drata ($1-5k/mo)control evidence support
Audit log aggregationDatadog + glue + Notionnative
Permissions / RBACAuth0 + customincluded
Approval workflowsSlack + screenshotscaptured
Auditor handoffdays pulling docsone link
01 · Approvals you can prove

Who can do what. What changed. Who approved it.

Not PDFs · not screenshots

approval rules — in force6 rules · 276 checks · 24h
fulfillment.under_500Under $500 · auto-approve204 checks● auto
ledger.month_closeMonth-close · human approval12 checks● human
agent.external_writesAgents cannot write outside org perimeter8 checks● block
pii.accessPII reads require scoped token · 24h42 checks● scoped
finance.refundsRefunds over $1,000 · approver set F6 checks● approver
experiment.shipShip experiments above 95% confidence only4 checks● gate
02 · Compliance without the rebuild

Evidence is easier when the work keeps its receipts.

Not a quarter-long project

SOC readiness
● mapped
Control evidence can be collected from runs
ISO mapping
● mapped
Annex A controls can map to policies
Restricted data
● gated
Requires signed authorization and safeguards
DPA support
● supported
Erasure and export workflows depend on configuration
Payment data
● restricted
Full card data is prohibited unless separately authorized
02 · The difference

Vanta · Drata · OneTrust gives you the tool. Lyberty ties it to the rest of the business.

Under the hood

Vanta · Drata · OneTrust
A tool that sits on top of your stack and asks it to prove things later.
EvidenceCollected on a schedule
ControlsMapped to tools in a dashboard
AuditPull evidence and hope it matches
Workflow approvalPolicy docs for the future
DriftDiscovered at audit time
Lyberty
Approvals and evidence captured while the work happens.
EvidenceCaptured as work happens
ControlsMapped to how work actually happens
AuditSend the evidence link
Workflow approvalSensitive actions can require approval checks
DriftFlagged when evidence is missing

The surface is just the view.

All six surfaces share the same record. Adopt one, and the others are already reading from what you wrote — no sync, no export, no reconcile.

See every surface