Verifiable data transfer for isolated laboratory systems.
The dispatch record is signed together with the work order, classification and target system.
No site policy: files are checked only against the edition's limits. What a site policy does
Two ways to put the same licence on another device. You only do this once per device.
On this device (the one that already has the licence) press Show licence as a code. On the other device open Receive, choose the live camera and point it at the code.
Do this on the device that needs the licence. Open kionel-license.json with a text editor
(Notepad on Windows, TextEdit on Mac, or any notes app), select all of it, copy, and paste it into the box below.
It is plain text that starts with {"schema" — copy all of it, from the first { to the last }.
Loaded once per browser. Keep kionel-license.json on a shared drive:
you load it again after the browser's data is cleared, in a private window, or on another browser or computer.
Test-lab mode only. The receiving device signs real transfer results with its own identity.
How will the file leave this PC?
Several files? Select them together: they travel as one ZIP, with a list of each file's SHA-256 inside it that the signed records cover too.
Signed into the record as declared by the person at this PC. It is not a login: the record proves what was written and when, not who typed it.
Only need proof, not the file?
Seal the file here: the file stays on this device, and a signed record of its SHA-256, size, time and work order is made with this device's key. The record is shown as one code — scan it with the receiving device (Receive → Live camera) to carry the proof out. If the file itself travels on a USB stick, put the downloaded record next to it: the receiving device checks the file against the record and signs the delivery receipt.
How will the receiver read this screen?
Best for small files: results, CSV, method files up to a few hundred KB.
Tip hold the camera steady; nothing to record or open.
Best for up to a few MB; PDFs and images.
Tip film until the countdown on this screen says Enough.
Best for phone videos that are a little blurred or compressed: far more of its images are read.
Tip full screen, camera 30–50 cm away, no glare; best read from a recording.
Text, CSV, XML, JSON and instrument logs shrink 4–10× before sending. PDF, JPEG, ZIP and Office files are already compressed and are sent as they are, so the original file — and its SHA-256 — stays exact.
This device sends. On the other device — a laptop, tablet or phone with a camera — open the same page and press Receive. Then point this device's camera at the code shown there.
Scan this with the other device's camera app to open the page.
On the device that receives, press Receive → Show a code. Type the 12-character code here and press Send. This PC then only shows codes and the receiving device only reads them.
This PC has a microphone? Then nothing needs typing. Press Listen here, and on the receiving device press Pair by sound. The sound carries nothing secret: you still compare the codes on both screens before anything is sent. The microphone is only used on this page and nothing is recorded.
For a PC with a printer. The file is printed as encrypted codes; the receiving device scans the pages with its camera, in any order, now or years later. A few smudged or torn codes do not matter. How it works
Connect this PC's serial port to the receiving computer's. With a cable that carries only this PC's transmit line, nothing can travel back: a low-cost one-way link. On the receiver choose Receive → Serial cable, type its code above (or load its receiver card), and use the same speed on both sides. Wiring and speeds
For logs, reports or recipes that appear in a folder on this PC. Each new or changed file is encrypted to the receiving computer's card, signed and sent over the cable; the receiver keeps listening and writes each file with its receipt into its own folder. Needs the receiver card (below) and Chrome or Edge.
Create the card once on the receiver (Receive → Receiver card) and load it here. To change receivers, remove the card or load a different one.
⚠ Sending shows rapidly flashing images. If you or anyone nearby has photosensitive epilepsy, do not look at the screen while it sends.
What to do, step by step
1 · How are the two devices connected?
Type this one-time code on the sending PC, under "This PC has no camera?".
The sending PC has a microphone? Skip the typing: press Listen for the receiver there, then:
For pages printed with Kionel. Enter the code that was shown when they were printed (or that is printed on them), then point this camera at the pages, one at a time, in any order.
A one-time setup for instrument PCs without a camera. The card holds this device's public keys; load it on the sender once, through a route your lab trusts. After that the sender shows codes and this device reads them — no reply, and no code comparison.
What you give up: the card's key is long-lived, so the forward secrecy of the two-way transfer does not apply, and the protection rests on the card having been installed on the right sender.
Retire the key if a sending PC is lost or should no longer send here: every card made so far stops working. Then create a new card and load it on the PCs that should keep sending.
2 · How will this device read the sender's screen?
Film the sending screen with this device's camera app, then Kionel reads the video. You do not have to hold still, and if the video ends too early, record again — what was collected is kept.
Film at 1080p and 30 fps. Keep the whole sending screen in the picture, in focus, without glare. To read the video on another device, copy the original by cable or Quick Share, or send it as a document: messaging apps compress videos and the codes become unreadable.
Already filmed the sending screen? Open the video here — now or later, on this device. If it was filmed on a phone, copy the original by cable or Quick Share (or send it as a document): messaging apps shrink videos until the codes cannot be read.
For a sending PC connected to this computer by a serial cable (RS-232 or a USB serial adapter). The data arrives without a camera or a screen, and a one-way cable lets nothing go back. Wiring and speeds
The file came on a USB stick or by another route?
Add the sealed record that was made on the sending PC (.seal.json), or scan its seal code with this
camera. Then add the file itself: this device checks it against the record and signs the delivery receipt.
This device accepts files from any sender and records which key signed each one. After a delivery you can choose to accept only that sender.
Each received file and its signed receipt are written straight into a folder you choose, for example one your LIMS or data system already watches.
Leave empty to keep the sender's file name. Fields:
{name} {workorder} {class} {operator} {date} {time},
taken from the signed record. The extension is kept, a field that is empty is left out, and the receipt is named after the file.
An independent authority confirms when the receipt existed. Only the receipt's fingerprint (SHA-256) is sent, through kionel.com, to DigiCert's timestamp service; the file never leaves this device. Needs internet on this device.
Every file this device sent, received or sealed, kept in this browser with its signed record. Export it for your audit-trail review, or print a review report for your quality unit.