A while back I shared Hummint here as a beta: instead of running a finished text through an AI detector, it records how the text was actually written and turns that into proof you can verify (timeline, checkpoints, a hash).
It's not a demo anymore. Billing is live, but it stays free for 5 proof packs a month and anyone who just needs to verify a certificate never pays or signs up. Since launch it also went fully bilingual (EN + IT it started as an Italian product), got a Chrome extension and a WordPress badge so the proof works outside our editor, added QR codes on certificates, an editor that adapts to students/teachers/journalists/writers, a try-before-signup demo on the homepage, and a full redesign.
One thing I keep debating: the proof is strongest when you write inside Hummint, but nobody wants to switch editor. The Chrome extension is our attempt to meet people where they already write. As writers yourselves would you rather write in a dedicated space for stronger proof, or have it capture whatever you do, wherever you do it?
The core idea is simple: instead of trying to guess whether a final text looks AIgenerated , Hummint creates verifiable evidence around how the text was written.
We re building a proof layer for human writing: writing sessions, revision signals, timestamps, hashes, AI disclosure, and a shareable certificate.
I d love feedback from students, professors, journalists, editors and makers:
Hummint certifies the human writing process. It records writing behaviour and generates a verifiable cryptographic certificate. A reliable alternative to AI detectors, which currently do not work.
For writers, students, lecturers and journalists
