Support
Get help
Email Support
For account issues, billing questions, and general inquiries.
[email protected]API
API Issues
For integration problems, rate limiting, and technical errors.
[email protected]Security
Security Reports
For vulnerability disclosures and security concerns.
[email protected]FAQ
What does Krusade do?
Krusade operates content authenticity for you. We sign the files you publish, run the signing and verification infrastructure, and manage the certificates and keys. Each signed file carries a Content Credential (the C2PA open standard) that anyone can verify without an account.
Do I need to manage certificates or keys?
No. Krusade signs under its own certificate and handles key custody and rotation. We do not issue certificates today. Bring-your-own certificate / DIDs is planned on Enterprise.
How do I sign a file?
Use the browser flow on the Sign page, or call the signing API (POST /api/v1/sign). The browser flow is the quickest way to try the product; the API is for CMS, CDN, and pipeline integrations.
How do I verify a file?
Use the Verify page in the browser, the CLI (krusade verify), or the public REST API. No account required — verification is free.
What happens if Krusade goes offline?
Signed files carry their proof with them and still verify in any conformant tool (Adobe Content Credentials, c2patool). Verification does not depend on Krusade staying online.
What happens if a platform strips the metadata?
The credential lives in the file; if a platform removes it, verify reports no credentials. Krusade's invisible watermark is a detect/report signal today — it is not DRM, and hosted recovery of a stripped credential is not shipping yet. Do not treat watermark detection as proof of authenticity by itself.