Capabilities

Put a checkable Content Credential in every file.

Krusade handles C2PA manifest construction and signing. Your team keeps publishing; the resulting file carries its provenance with it.

Signed by Krusade; Team can attach a DNS-verified organization name, with a CA-trusted certificate later. Trust model

Protect a file Check a file

Early access. Signing and public verification are live for images, documents, video, and audio. Read current API details.

What your team can do

Embed

The credential travels with the file

Krusade writes a signed C2PA manifest into supported images, documents, video, and audio. It is not a separate receipt or database record.

Check

Anyone can check

Anyone can inspect the embedded credential in Krusade's public verifier, Adobe Content Credentials, or c2patool.

Detect

Changes become visible

The manifest binds to the signed asset. A conforming verifier reports whether the file and its assertions still validate after an edit.

Identify

Add an organization name

Team accounts can verify a domain and attach that organization name to credentials signed under Krusade's current shared certificate.

Describe

Carry useful metadata

Add creator, rights, licensing, AI-use preferences, and supported IPTC, EXIF, XMP, and CAWG fields to the manifest.

Automate

Sign from your workflow

Use the API, CLI, SDKs, CMS integrations, or webhooks without building certificate and manifest plumbing yourself.

How it works

One file, one portable record

01
Protect
Krusade attaches a Content Credential to the file. You download the protected copy.
02
Distribute
Publish or share the protected file as usual. The credential travels with it.
03
Check
Anyone checks independently — no account, and no need for Krusade to stay online.

Provenance recovery

Invisible watermarking & soft-binding

Social networks, messaging apps, and downstream pipelines often strip EXIF and C2PA metadata on upload. Soft-binding embeds a resilient, keyed invisible watermark into the media before signing, enabling provenance recovery even when metadata is completely removed.

Resilient provenance recovery

When metadata is stripped downstream, verifiers can detect the embedded watermark signal and resolve the asset's signing identity and original credential record.

Identity recovery, not DRM

Positioned strictly as an identity and provenance recovery tool for publishers—not digital rights management (DRM), content encryption, access control, or a digital asset manager (DAM).

Technical detail

Supported standards

Under the hood, Krusade speaks the major content-authenticity standards—verified against Adobe's reference tooling—so your proof works everywhere, and you never touch the plumbing.

C2PA: The core content-provenance manifest every signed file carries.
IPTC Metadata: Embed IPTC photo metadata (creator, copyright, captions) into the manifest.
EXIF Metadata: Attach camera/EXIF data such as make, model, and capture settings.
AI Opt-Out / Training Preferences: Declare whether the asset may be used for AI training and mining (CAWG).
XMP Metadata: Carry Adobe XMP packet data alongside the manifest.

Plus, Krusade extras

Licensing: Attach a Creative Commons or rights statement to the asset.
Web3 Provenance: Record wallet / NFT provenance references for on-chain assets.
Signer identity: Optionally embed the signer's verified-email name and address (opt-in).
Soft-binding recovery: Keyed invisible watermark enabling provenance lookup when platforms strip metadata.

See pricing