Solus creates a chain of custody for student writing. When a student submits a .solus file, you get a cryptographic certificate showing every keystroke, every paste, and the exact order events happened — evidence, not a probability score.
Individual access · reviewed within 48 hours · or try the verifier free now
The student writes in Solus and clicks "Submit." The .solus file is sealed with their ECDSA-P256 key and sent to your class dashboard. You get a notification.
The submission appears in your class list with a verdict badge — Verified Human, Partial, Unsupported, Enrolling, or Tampered. Click to open the full certificate view.
See the essay text alongside the verification report: keystroke count, paste events, keystroke composition, timestamp chain, and the full 29-check audit (19 cryptographic + 10 behavioral).
Leave inline comments and a grade. Export the entire class's results to CSV for your LMS. The certificate stays attached to the submission record permanently.
Every .solus file embeds a cryptographic certificate with objective, machine-verifiable facts.
The total number of keystrokes, with a signed hash of the full timing log. You see the count; the log proves it's authentic.
Every paste event is logged with its content hash and character count. Pasted text is quarantined, not blocked — you see exactly what was pasted.
A behavioral score derived from the writer's typing dynamics against their own baseline. Distinguishes composition (thinking as you type) from transcription (typing from a phone or second screen). Reported as a 0–100 value with an absolute floor of 55 for the Verified Human™ badge.
Start time, end time, and a chain of intermediate hashes proving the document was written continuously — not assembled from fragments.
The ECDSA-P256 public key used to sign the document, tied to the student's Solus account. Proves which account produced the file.
Axis A · Provenance Integrity — 19 cryptographic checks confirm the file hasn't been touched since it was signed. Axis B · Human-Origin Support — 10 behavioral checks confirm the writer's typing pattern matches their enrolled baseline. Both green = Verified Human™.
The certificate is cryptographically signed — it can't be selectively altered. If the signature verifies, the data is authentic. If the student claims their low keystroke count or high paste count is a bug, you can ask them to demonstrate the bug occurring in a new document. Solus logs are deterministic: a document written by a human will always produce a plausible keystroke pattern. A low-keystroke document with high paste volume is what it looks like.
Yes. The public verifier at verify.soluseditor.com (or the Verify page on this site) lets anyone drag and drop a .solus file to run the full 29-check verification — no account required. Everything runs entirely in your browser using the SubtleCrypto API. Nothing is uploaded.
Five possible outcomes. Verified Human™ — both axes green; the badge is awarded. Partial — provenance is intact but one or more behavioral checks came back mixed (borderline composition score, low keystroke count for the word count, etc.) — review in context. Unsupported — file is cryptographically clean but the writer isn't enrolled yet, so the behavioral axis can't run — common for legacy files and new users. Enrolling — provenance intact, writer's baseline still building; the badge will unlock on future submissions. Tampered — a cryptographic check failed; the file was modified after signing. Treat this last one as a serious finding.
No. Solus works offline for writing and local saving. The keystroke signing is entirely local — it uses the device's cryptographic hardware, not a server. Students only need internet to submit to your class dashboard. They can write offline and submit later.
Yes. Students can open the local verifier in Solus to see their own certificate before submitting. This is intentional — we believe transparency builds trust. Students know exactly what you'll see. There are no surprises.
Document content is encrypted with AES-256-GCM. X Point's servers never see the plaintext of essays. You (the teacher) can decrypt and read the essay through your dashboard because you hold the class decryption key. But X Point cannot read your students' essays — only you can.
Apply for institutional access and we'll set up your first class within 48 hours.