Content Provenance
on Akamai EdgeWorkers
Enterprise-grade content provenance deployed through Akamai Property Manager. EdgeWorker responseProvider with EdgeKV caching across the entire Akamai network. White-glove deployment. No origin changes.
How It Works
White-glove deployment managed by our team. No engineering resources required from your side.
Deploy the EdgeWorker
Our team deploys the Encypher EdgeWorker to your Akamai Property Manager configuration. The responseProvider handler intercepts HTML responses at the edge with no origin changes.
Configure EdgeKV
EdgeKV provides native TTL caching for signed content plans. The EdgeWorker connects to your Encypher account through a dedicated API backend.
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.
Works With Your CMS
The EdgeWorker detects and protects article content automatically across every major publishing platform. No per-CMS configuration needed.
WordPress
Self-hosted and WordPress.com
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
Enterprise Features Included
Akamai deployments include every Enterprise feature. Unlimited volume, full compliance, and dedicated support.
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 Google Docs, Slack, social media, and AI prompts, so you can trace content wherever it travels.
EdgeKV Native Caching
Signed content plans are cached in EdgeKV with native TTL. Subsequent requests for the same article resolve from cache with no API round-trip across the entire Akamai network.
Your Site Never Breaks
If anything goes wrong, the EdgeWorker serves your original page unchanged. Provenance is additive. It never degrades your site availability or reader experience.
Enterprise Content Provenance on Akamai
White-glove deployment. EdgeKV caching at every Akamai edge node. Unlimited volume. Full compliance. Dedicated support.