Stop guessing whether AI wrote it. Prove that a person did.
Most AI detectors work after a document is finished — they guess. Solus works while it's being written. AI is stopped at the source, not sniffed out afterward, and the proof travels with the file. As the student types, Solus runs 30 checks on how the document was written — 20 cryptographic, 10 behavioral — and seals the result into the file. If a document was written in Solus Editor, you don't have to trust a probability: anyone, anywhere, can open the file and see the evidence for themselves.
Every keystroke tracked. Every paste cordoned off. Every submission verifiable — deterministically. Free for students, free for individuals, free for a teacher's first course.
Most schools do have something — a detector, a content filter, a lockdown browser, version history. Every one of those answers the question after the writing is finished, or only on hardware you control. None of them can tell you that a specific person wrote a specific document. That's the gap, and right now Solus is the only tool that closes it.
Detectors read the finished text and return a probability. The vendors' own documentation says the score isn't proof, and false positives cluster on exactly the students least able to argue back — English-language learners and anyone who writes in a formal register. When a student denies it, a percentage gives you nothing to show.
Proxy and DNS blocking works on your network, on your devices, during your hours. The essay gets written at 11pm on a personal laptop over a phone hotspot. A blocker also can't distinguish a student who didn't use AI from one who used it somewhere you can't see — absence of a blocked request isn't evidence of anything.
Lockdown covers the proctored exam. It doesn't cover the take-home essay, the research paper, or the lab write-up — which is where most of the writing, and most of the AI, actually lives. It also ends the moment the session ends; nothing about the resulting document is verifiable afterward.
Version history stores periodic snapshots, not the writing process — and nothing signs it. A student who pastes 800 words and then edits them can produce a history that looks broadly like composition. It's a useful hint. It is not something you can put in front of an integrity panel.
Often you can. You just can't prove it. Experienced teachers are right a great deal of the time and still lose the conversation the moment a student pushes back, because a professional judgment and a documented record are not the same object in a dispute.
Captures the writing as it happens, in the editor, and seals it into the document. 30 checks — 20 cryptographic, 10 behavioral — confirm the file wasn't altered, wasn't pasted in against policy, and wasn't transcribed from a screen. The proof travels with the file, and anyone can re-run it without an account and without our servers.
Ranked left to right by how commonly schools already use them
| Solus | Turnitin AI | GPTZero · Copyleaks · Originality | Google Docs history | Lockdown & network blocking | Grammarly Authorship | |
|---|---|---|---|---|---|---|
| What it looks at | Every keystroke, as it's typed | The finished text | The finished text | Periodic snapshots | The network and the device | Typing inside a third-party editor |
| What you get back | A deterministic proof | A probability | A probability | Raw history to interpret | Blocked, or not | An authorship report |
| Stops AI text entering the document | ✓ | — | — | — | Partial | — |
| Catches transcription off a phone or second screen | ✓ | — | — | — | — | — |
| Works off campus, on a personal device | ✓ | ✓ | ✓ | ✓ | — | ✓ |
| Proof cryptographically bound to the document | ✓ | — | — | — | — | — |
| Re-verifiable by anyone, without the vendor's servers | ✓ | — | — | — | — | — |
| False-positive risk on ELL and formal prose | None — not a classifier | Documented | Documented | n/a | n/a | n/a |
| Essay text readable by the vendor | No — encrypted on the student's device | Uploaded | Uploaded | Stored by Google | n/a | Uploaded |
| Cost to one teacher | First course free | Institution license | Paid per seat | Free | Institution license | Paid per seat |
Comparison describes what each category is structurally able to do, based on publicly documented behavior as of September 2026 — not a ranking of product quality. Solus is designed to sit alongside these, not necessarily to replace them; several schools run Solus and Turnitin together.
The certification that a document was written keystroke by keystroke by an enrolled writer whose typing pattern matches — not generated, not pasted, not transcribed. Two independent axes have to pass: cryptographic provenance and behavioral consistency with the writer's baseline.
Most tools grade the finished text and guess. Solus is the writing environment — the editor captures every keystroke, signs them, and produces a portable proof that anyone can check without our servers.
You know part of the story. Solus does the input-time capture too, then goes further in three specific ways. First, the document is the proof — a signed .solus file that carries its certificate; the record travels with the file and doesn't depend on our servers to verify. Second, the editor enforces policy at input: paste can be blocked, sealed for later review, or required to carry a citation — the rules act on the keystroke, not the report. Third, verification is two-axis: cryptographic provenance and a behavioral match against the writer's own established typing baseline. That closes the phone-transcription gap that pure input-time observers can't.
Yes — as a companion, not a primary defense. The paste blocker and behavioral checks already stop the two paths plagiarism travels through. For teachers who want a second-opinion report, Solus includes cross-submission matching within your institution (catches cross-class copying and cross-semester recycling), plus an optional paid web-content add-on. For licensed academic journals, run Solus alongside Turnitin. Details →
Students open Solus and write their essay. Nothing extra to install, nothing different to do. The record builds itself as they work.
Every keystroke is recorded and time-stamped as they type
Submitting seals the document with a cryptographic signature
Teachers receive a signed authorship certificate — evidence, not a score
AI detectors judge the finished paper.
Solus verifies the writing process.
Schools mandate Solus. Students write. Teachers verify. The cryptographic certificate doesn't care about AI detector scores — it shows exactly what was typed.
See how schools use SolusLaw firms, consultancies, and publishers use Solus to provide clients with a chain of custody for human-authored deliverables. Free for individuals. Team dashboards for organizations.
See enterprise featuresInstead of guessing whether finished text looks AI-generated, Solus records the writing process while it happens — and seals that record into a verifiable certificate.
Every character typed in Solus is recorded with a timestamp and signed into an append-only log. Edits, deletions, and revisions are all captured — the full writing process, not just the final text.
External content — pasted text, dropped files, or imported images — is captured into a separate record, not blocked. The teacher sees exactly what came from the keyboard versus what was brought in from elsewhere, with full timestamps.
Each .solus file contains a certificate signed with ECDSA-P256. Any modification to the document — even a single character — invalidates the signature and is immediately detected during verification.
Every keystroke is timestamped and hashed. The editor looks and feels like any word processor — the signing happens invisibly in the background.
On save, Solus seals the keystroke log, paste events, and document content into a single .solus file signed with the student's ECDSA-P256 key pair.
The teacher opens the .solus file in the teacher dashboard or drags it to verify.soluseditor.com. The full 30-check verification runs in seconds — no account required.
Your teacher dashboard shows exactly what was typed versus pasted — with timestamps, keystroke counts, and a clear breakdown of the writing process. No more gut feelings. No more student disputes that go nowhere.
See how teachers use SolusInstitutional licenses for classes, departments, or whole universities. Join codes, seat management, batch verification, and CSV export. SSO and Canvas LTI integration coming in 2026.
See institutional optionsFree for the individuals doing the writing — students and professionals, permanently. Free for a teacher's entire first course. Paid only when an organization needs management tools across many classrooms.
For students. Full keystroke signing and verification. Always free, no exceptions.
Everything a teacher needs to collect, verify, and grade — free for your first full course. No card, no application, no approval.
After that, classes you already made keep working — starting a new course is $299/yr. See pricing
Department ($1,499/yr) and Institution plans for schools deploying at scale.
For professionals who need a verifiable record of their own writing process.
Manager visibility, audit trail, and client-ready verification reports.
SSO, API, compliance agreements, white-label, and dedicated support.
Drag a .solus file here. The 30-check verification (20 cryptographic + 10 behavioral) runs entirely in your browser — nothing is uploaded to any server.
or click to browse
Works with all Solus documents. No account required.
Essays are encrypted in the student's browser before anything leaves the device, using a key wrapped for their teacher. Our servers hold ciphertext. There is no switch we could flip to read a document, because we don't have the key.
Not student writing, not keystroke timing, not anything else. We don't train models, and we don't hand data to anyone who does. This isn't a setting you have to find and turn off.
No data sales, no advertising, no third-party trackers profiling minors. Institutions can sign a FERPA Data Processing Agreement, and export or delete everything on request.
Drag a .solus file onto the verifier and all 30 checks execute in your browser. Nothing is uploaded. You can disconnect from the internet and the result is identical.
The behavioral checks use timing between keypresses within the document being written. Solus doesn't watch other apps, other tabs, the camera, or the microphone — and it only runs while the editor is open.
Students write in Solus free at write.soluseditor.com. Teachers can verify any .solus file without an account.