01 / MAKE
Document the work while it is being made.
The maker records the current stage, short progress notes, photos, materials and expected completion. The client receives one private link and can follow the work without creating an account.
How Kvisl works
Kvisl begins when the physical work begins. It follows one object through production, transfer, certification and its long-term digital identity.
Start creating ↗01 / MAKE
The maker records the current stage, short progress notes, photos, materials and expected completion. The client receives one private link and can follow the work without creating an account.
02 / HANDOFF
For in-person pickup or local delivery, Kvisl uses a single-use six-digit Handoff Code. For shipping, the record keeps carrier, tracking and receipt information with the work.
03 / CERTIFY
Once the work is completed, Kvisl can produce a printable Certificate and Production Record PDF from the maker, material, production and delivery information already stored in the archive.
04 / RECORD
After delivery, the progress page becomes the finished work’s permanent digital record. Its Digital ID, production history, handoff evidence, certificate, Physical Link and SHA-256 record hash remain connected to the physical work.
What the client sees
During production, the client sees only the useful state of the work: current stage, latest update, progress images and expected completion.
After handoff, the archive can also be reached from a separate Physical Link carried by the object itself.
Four capabilities
Offline-first
Kvisl can be installed as a PWA. Progress notes and selected photos created from the Piece tools screen are held in a local IndexedDB queue when connectivity disappears, then retried when the connection returns or Kvisl is opened again.
Physical Link
Kvisl generates one long-lived, non-enumerable URL for the work. The maker chooses how to carry it: NFC, QR, engraving, print or another method. Kvisl provides the link and resolver, not the NFC-writing hardware.
Maker’s final message
Before handoff, the maker can leave a short written message, audio note, or both. When the production record locks, that final message locks with it and becomes part of the permanent physical record.
Data sovereignty
Locked production facts remain immutable. Timeline updates and media sit outside that core, so the maker can hide them from the client or permanently remove them while Kvisl retains only an audit event that content was removed.
Record integrity
When a work is handed over or shipped, Kvisl locks its core production metadata. A SHA-256 hash is generated from that locked record.
Public verification can recompute the hash from the stored production data and compare it with the saved value. The Physical Link is an object-to-record entry point, not a claim that ordinary NFC hardware itself cannot be cloned.
Open verification ↗