PUCE Video
Neural recompression of idle video libraries, with the result sealed with post-quantum encryption. For archive, not for streaming.
Capabilities
Neural Compression
A neural engine, with our proprietary PQSL layer, that recompresses the uploaded video in batch. Compression is lossy and the ratio compares against the file you uploaded, with no quality guarantee.
Post-Quantum Sealing
The result is sealed with ML-KEM-768 and AES-256-GCM and signed with ML-DSA-65 — tampered with, it does not open.
Viewing the archive
To watch the content, “Play” prepares a standard (HLS) playback on the server. It is a batch preparation, not direct playback of the .puce.
Integrity check
Confirms the file is complete and belongs to the set the platform sealed (consistency). The signer’s public key comes from the platform: an independent proof is not available yet.
From upload to result
What you need to know
Today’s limits, stated plainly. Every published figure is measured; the ones we have not measured are not published.
- The original video you upload is kept in clear on the platform; only the result (.puce) is sealed.
- The ratio compares the result with the file you uploaded. Compression is lossy and without a quality guarantee: quality is not measured per video.
- The key that opens your sealed videos is created and kept in this browser. Save a backup now: if you clear the browser data without one, the videos sealed with this key stop opening.
What happens when I press “Play”?
- “Play” is not direct playback of the .puce: it is a batch preparation on the server, on dedicated GPU infrastructure. Only once it is ready is there a picture.
- Preparation takes a time of the same order as the video length (on a 1080p test film, about 0.72× the length — a single measurement; other content may take more or less).
- During preparation, your recipient key is sent to the server that prepares playback. There is not yet a preparation in which the key stays in your browser.
- The playback is kept as a temporary clear copy, with temporary access. While it exists, anyone with access to your account can watch it, even without your key. It is configured to expire after 1 to 2 days (up to 48 h). The .puce file stays sealed.
- The archive does not give the original file back: recompression is lossy. Export to an H.264 file is not available yet.
Standards & Compliance
Post-quantum key encapsulation for the archive
Signature on every chunk: it only opens if complete and in the sealed order
Symmetric encryption of each video segment
Digest of each chunk, to detect changes
Use Cases
Long-term archive of idle video libraries
Retention of surveillance recordings
Training and e-learning libraries
Post-production rushes and intermediate versions
Measured ratios
Measured on 2026-10-16, one run per material: not an average and not a guarantee. The ratio depends on the content and on the source file.
- Test film 1080p (Sintel, 1.17 GB): 10.08× smaller than the uploaded file (one run, measured through the command line with the file’s native frame rate; uploads through the portal read the same rate from MP4 and MOV files and use 30 frames per second for other formats, where the value can differ; no quality measured).
- Real fixed-camera recording 1080p (1.13 GB): 5.71× smaller than the uploaded file (one run, measured through the command line with the file’s native frame rate; uploads through the portal read the same rate from MP4 and MOV files and use 30 frames per second for other formats, where the value can differ; no quality measured).