Your identity travels with the work
Sign with your name and organization identity at release. Downstream editors and distribution partners can inspect the source record without asking your team to assemble it again.
For publishers and rights holders
Encypher brings signing at release and public checking into your publishing workflow. Give editors and distribution partners a source and terms record they can inspect, without rebuilding the evidence for each recipient. Supplied rights terms are not proof of ownership.
Start with one work and a recipient check. No card. See signing plans
$0
to sign and to verify
Portable
identity and terms that travel with the signed work
Public
a free check for editors, readers, and partners
Mark for publishers and rights holders in action
See the plugin setup, signed post status, reader badge, and public verifier in one publishing example.
Watch a story get signedFor each release and review
Sign with your name and organization identity at release. Downstream editors and distribution partners can inspect the source record without asking your team to assemble it again.
Include the terms you supply in the signed record. Give each recipient the same declarations to review, rather than reconstructing them for each handoff. They do not establish ownership or permission.
Use the signer, time, terms, and file-integrity record for editorial, distribution, and support questions. Recipients can check it with the free public verifier, without an account.
See the proof
Inspect the signer, supplied declarations, and integrity result a downstream editor or distribution partner can use in a review.
Check a signed workSee what the free publisher lane covers and which paid controls are available as your program grows.
Review signing plansFor publishers selling ad inventory: a separate simulation of signed and unsigned stock under buyer rules, not evidence of revenue uplift.
Open the AdCP simulationPublishing comes first. If you also sell ad inventory, ask about eligibility for the separate publisher pilot.
Talk to us about the ad pilotStart with one publishing handoff
Choose one work and the editor or partner who needs its source record. Connect your publishing path, then check what reaches them. Edits or format changes may affect verification.
Create a free account, identify the organization signing the work, and confirm its publishing domain.
Use the WordPress plugin, a Ghost webhook, or the API for your own publishing and asset tools.
Sign after the final publish or export step. Ask an editor or distribution partner to verify the received work and inspect its source and terms before expanding.
Sign one work free, then have a recipient check its source and supplied terms without an account. Use that handoff to evaluate your publishing workflow.