For enterprise application portfolios
Put one provenance control across every AI application.
Start with one team's completed outputs, including Microsoft Word, Excel, and PowerPoint files. Scale the same Mark API, organization identity, public verification path, and coverage record across a portfolio of 40 or more applications.
1 to 40+
applications on the same marking contract
Office
DOCX, XLSX, and PPTX join text, images, audio, video, and PDF
Identity
CAWG identity included, plus white-label root-CA issuance
Flagship workflow
Scale one Mark integration from one team to 40+ applications
A small team and a global portfolio use the same content contract. The difference is volume, operating controls, organization identity, and coverage management, not a second product.
Workflow
- 1
Choose the completed-output boundary
Each application submits completed text, media, PDF, DOCX, XLSX, or PPTX content after generation finishes and before the output reaches the customer, archive, or final document.
- 2
Mark through one shared API contract
The application receives signed content, a document ID, and a verification path. The same request model works across business units and formats.
- 3
Seal final evidence packages when needed
Where a workflow produces a final report, filing, or evidence package, Seal authenticates that finished file without replacing the output-level Mark record.
- 4
Measure portfolio coverage
Record submitted, marked, and failed outputs by application so legal and governance teams can see where the control is active and where a workflow bypasses it.
Illustrative application portfolio
Where is the provenance control active, and where is it failing?
Compare submitted, marked, and failed outputs by application. This example shows the portfolio view an economic buyer can use to separate active controls from coverage gaps.
| Application | Outputs submitted | Marked | Failed | Coverage | Audit export |
|---|---|---|---|---|---|
| Support assistantReady | 1,248 | 1,240 | 8 | 99.4% | Ready to export |
Expanded exception Support assistant output SA-1842 Failed - modified after markingIllustrative record: the submitted output was marked, but a later file no longer matched the signed state.
| |||||
| Legal draftingReady | 416 | 410 | 6 | 98.6% | Ready to export |
| Marketing toolsCoverage gap | 960 | 624 | 336 | 65.0% | Review required |
Evidence received
- Per-output C2PA provenance and public verification result
- Organization certificate chain and RFC 3161 signing time
- Application-level record of successful and failed submissions
- Final-file integrity record where Seal is applied
Rollout path
- Begin self-serve with one team on a Mark plan
- Prove the workflow on one production application
- Standardize the completion call and evidence fields
- Move to Enterprise for portfolio volume, white-label identity, deployment, and governance controls
The evidence covers outputs submitted by the integration. It does not claim visibility into applications, passages, edits, or failures that bypass the marking boundary.
Enterprise provenance in action
From completed content to a verifiable provenance record
Follow the signed-in dashboard from synthetic text to a verified record: sign through the live API, verify the signature on its own, and read the CA-backed trust verdict and its C2PA manifest.
Schedule a workflow reviewGovernance and review
A policy sets the rule. A record shows what ran.
Portfolio governance needs a written control and application-level evidence. Open each part to see what the record can, and cannot, establish.
Where it is required
Where provenance proof is required
Courts, regulators, and clients are asking for documentation that standard AI governance frameworks cannot produce. Open a use case for its workflow and evidence requirements.
Building for the EU AI Act? Read the EU AI Act compliance guide.
For technical readers
How document and passage provenance work together
C2PA authenticates the document as a whole. Encypher markers carry sub-document attribution; both layers bind to the same transparency-log record.
Enterprise capability
We didn't adopt the text-provenance standard. We wrote it.
Built on the C2PA open standard
Encypher authored the C2PA standard for unstructured text and co-chairs the Text Provenance Task Force alongside these member organizations. Logos indicate C2PA membership.
FAQ
Frequently asked questions
Questions from legal, compliance, and IT teams at law firms and regulated enterprises evaluating Encypher.
Build the record before you need it
The time to establish document provenance is at creation, not during litigation or regulatory review.