Self-host Jingwei for image attribution and verification

Review the source and run image protection and verification in your own environment. Built for teams and privacy-sensitive setups that need control over deployment and updates. It is not a mirror of jwprotect.com and does not claim feature parity.

Run image protection and verification in your own environment, and manage deployment, updates, and integrations yourself. It is suited to technical teams, privacy-sensitive setups, and internal workflows.

Visible deterrents, attribution signals, and verification are parts of a layered protection workflow They do not guarantee prevention of all theft, AI training, wash-out, screenshots, downloads, or platform re-encoding Detection does not independently prove legal ownership, image authenticity, or AI-generation origin

The verification page can read and summarize supported C2PA / Content Credentials information already present in a file. JWProtect’s current protection workflow does not issue, write, or generate C2PA Content Credentials.

Is the hosted site identical to self-host? No. Features, dependencies, deployment needs, and release timing may differ. Follow the jingwei-selfhost README. Does self-host upload images to jwprotect.com? No. Processing runs on the machine where you run the stack, and images are not uploaded to jwprotect.com. What setup do I need? Typically Docker / Docker Compose or an equivalent runtime, plus the configuration steps in the README. This is not a no-skill, one-click install. Does JWProtect self-host prove legal ownership? No. It provides visible deterrents, attribution signals, and a verification flow. Detection is not legal ownership or proof of authenticity.