WordPress
Self-hosted and WordPress.com
Fastly IntegrationContent Provenance
Content Provenance
on Fastly Compute
Sign everything you serve, without touching your CMS.Deploy a Fastly Compute service that adds invisible provenance markers to every article at the edge. Named backends, KV Store caching, and fail-open semantics. No CMS changes. Free for all publishers.
How it works
How It Works
Three steps from zero to signed articles on Fastly. One Compute service, one backend configuration.
1
Deploy the Compute Service
Add the Encypher Compute service to your Fastly account. The service uses named backends for API communication and KV Store for edge caching. No changes to your origin server.
2
Route Traffic
Point your Fastly service at your origin. All HTML responses pass through the Compute service, which detects article content and applies provenance markers before delivery.
3
Protect Every Article
Every article on your site receives invisible provenance markers at the edge. When that content is copied, scraped, or republished, you can trace it back to its source.
Zero-Code Configuration
Configuration examples
Configure with HTML Meta Tags
Control article detection, declare rights, and assign per-block licenses directly from your HTML. No rebuilds, no API calls, no dashboard configuration required.
Article Selector
Override automatic content detection with a CSS selector that targets your article region.
<meta name="encypher-selector" content=".story-body">
Document-Level Rights
Declare usage terms and license for all content on the page. Embedded in the C2PA manifest.
<meta name="encypher-rights" content="All rights reserved."> <meta name="encypher-license" content="CC-BY-4.0">
Per-Block Rights
Assign different licenses to different content blocks. The worker maps each block to the sentences it contains.
<div data-encypher-rights="(c) 2026 Your Publication"
data-encypher-license="CC-BY-4.0">
<p>Your original reporting.</p>
</div>Rights Cascade
The worker resolves rights in order: block-level attributes on individual elements, then document-level meta tags, then your organization's rights profile in the Encypher dashboard. Block-level and document-level rights coexist: document rights serve as the default for content not covered by a block-level attribute.
Works with your stack
Works With Your CMS
The Compute service detects and protects article content automatically across every major publishing platform. No per-CMS configuration needed.
Ghost
All Ghost-powered publications
Squarespace
Blog and article pages
Webflow
Rich text content blocks
Substack
Newsletter and post pages
Hugo / Jekyll
Static site generators
News Wires
AP, Reuters, and wire formats
Custom HTML
Any site with configurable selectors
Plans and limits
Free vs. Enterprise
Full content provenance is free for every publisher. Enterprise adds leak detection, C2PA compliance, granular licensing, and unlimited volume.
| Feature | Free | Enterprise |
|---|---|---|
| Content provenance on every article | ||
| Sentence-level content tracking | ||
| Automatic CMS compatibility | ||
| Zero performance impact | ||
| Designed to preserve site availability | ||
| Article selector override via meta tags | ||
| Document-level rights and license declarations | ||
| Per-block rights via HTML data attributes | ||
| Monthly article volume | Unlimited (fair use) | Unlimited, incl. AI-output at scale |
| Leak source identification | - | |
| C2PA manifest compliance | - | |
| Attribution analytics dashboard | - | |
| Dedicated support and named account manager | - |
Architecture
Built for Publisher Sites
Designed for reliability at CDN scale. No performance impact on your site, no risk to availability.
Works With Every CMS
Automatic content detection across WordPress, Ghost, Squarespace, Webflow, Substack, Hugo, news wires, and custom HTML. No per-CMS configuration needed.
Invisible, Persistent Protection
Provenance markers are invisible to readers. They survive copy-paste into document editors, messaging tools, social media, and AI prompts, so you can trace content wherever it travels.
KV Store Edge Caching
Signed content plans are cached in Fastly KV Store at the edge. Subsequent requests for the same article resolve from cache with no API round-trip.
Your Site Never Breaks
If anything goes wrong, the service serves your original page unchanged. Provenance is additive. It never degrades your site availability or reader experience.
Protect Every Article on Fastly
One Compute service. KV Store caching at every edge node. Know where your content goes when it is copied, scraped, or ingested by AI.