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 for later, and the proof travels with 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.
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 29-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 optionsEducation and Professional tiers with the same commitment: free for the individuals doing the writing, paid for the organizations that need management tools.
For students. Full keystroke signing and verification. Always free, no exceptions.
For teachers who need verification tools, submission workflow, and class management.
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 29-check verification (19 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.
Students write in Solus free at write.soluseditor.com. Teachers can verify any .solus file without an account.