AI detectors are broken. They flag honest students, miss actual cheating, and turn every accusation into a fight neither side can win — because they're trying to answer the wrong question. Solus flips the problem. It's a writing environment AI can't use in the first place, where every keystroke, paste, and input is recorded as it happens. Authorship becomes provable, not probable.
If any of the below sounds like your week, Solus was built for you.
You can't grade with confidence. Every AI-detector flag turns into an argument you can't win.
Every submission carries a report showing exactly how the document was written. Not an accusation. Evidence.
Your own writing gets flagged as AI. You have no way to prove otherwise.
Write in Solus and every document ships with proof it's yours — keystroke by keystroke. Not a probability. Verifiable.
You're stuck between two failure modes — miss real cheating or punish innocent students.
Institutional verification of authorship. No black-box classifier. No false positives. Just evidence.
How do you prove to a skeptical client that your draft is really yours?
Send them the .solus file. They drop it into the public verifier. Deterministic proof of authorship — no account, nothing uploaded.
AI detectors ask: "was this text generated by a machine?" — a question no one can answer for sure. Solus asks a different question — "how was this text actually written?" — and captures the answer as it happens.
.solus file.Nothing here is a probability. Every check either passes, fails, or explicitly skips — and you can see the result of each one individually. The Verified Human™ badge is only awarded when both axes come back clean.
The archive is intact. The certificate hasn't been altered. The keystroke ledger still reproduces its commitment. Plain-English: nobody has touched this file since it was signed.
Any single failure → verdict is tampered.
The typing pattern in this document matches the writer's own historical rhythm. Composition beats transcription. No synthetic input. Plain-English: this person actually typed this, and their fingers know it.
Hard fail → unsupported. Partial → limited.
The premise sounds invasive on paper. It isn't. Here's what actually happens.
Document text is sealed with AES-256-GCM and wrapped for the intended recipient (usually your teacher). Solus's servers never hold the decryption key. Nothing you write is legible to us — ever.
When someone drops a .solus file into the public verifier, the file is not uploaded anywhere. All 29 checks run locally using the Web Crypto API. You can disconnect from the internet before dropping a file and it still works.
No opaque "authenticity score." The report shows 29 separate pass/fail results with plain-English explanations. If something fails, you know exactly which check and why — not a probability, not a mystery.
The behavioral checks look at typing dynamics (dwell, flight, burst rhythm) and event ordering. They don't read your essay. Teachers see the writing when they open the doc; the verifier can score behavior without ever decrypting content.
Just do your work. Solus learns your typing rhythm silently in the background. About 8,000 keystrokes across three or more days is enough.
Your baseline is sealed. Now every submission runs both verification axes against your own history.
Verified Human™ is awarded when provenance is intact and the typing pattern matches your baseline.
Try the public verifier with any .solus file, start writing free, or spin up a teacher account with a 60-day pilot — no card, no approval, no wait. Teachers can also preview the institution portal in a self-serve sandbox.