Standards over silos
We build on open specifications because provenance that only works inside one system is not provenance. If you would rather extend a standard than invent a moat, you will fit here.
CAREERS
Hashproof is a small team working on content provenance: the infrastructure that lets anyone confirm where a piece of media came from and what happened to it. If that problem pulls at you, we want to hear from you.
Three commitments that shape what we build and how we talk about it.
We build on open specifications because provenance that only works inside one system is not provenance. If you would rather extend a standard than invent a moat, you will fit here.
We hold ourselves to claims a third party can check. That discipline runs from the cryptography through the way we write about the product. No fabricated numbers, no superlatives standing in for evidence.
A handful of primitives, done carefully, beats a sprawling feature list. We would rather get signing, resolution, and verification right than ship ten half-built surfaces.
We do not always have a formal listing open. When we grow, it is usually in one of these areas.
C2PA manifest handling, signing pipelines, and the HTTP surface. TypeScript and a Fastify service today, with performance-sensitive paths moving toward Rust and WASM.
Perceptual hashing, soft-binding resolution, and forensic analysis. Work where signal processing meets adversarial robustness.
Anchoring, peer federation, and the reliability of a service other systems depend on for trust.
We hire ahead of formal listings when we meet the right person. Send what you have worked on and what you want to work on next to careers@hashproof.ai. A link to code or writing beats a resume.
Curious how the system works first? Start with the method page.