Draftline exists because I'm a writer who got tired of choosing between three kinds of compromise, and because I happen to be a developer with enough stubbornness to spend a year doing something about it instead of complaining.
I'm a developer by trade, and developers are spoiled. Our tools find the problems we can't see in our own mental model — they map every function, track every variable, and flag the contradiction the moment we type it. Writers get a word count.
Draftline treats a novel the way an IDE treats a codebase. Plotlines are functions. Characters are variables. The character codex already maps the cast across the entire story, and the continuity engine I'm building on top of it, which I call PlotWalker and which is not yet enabled in the beta, is meant to surface a slipped eye color or a fact learned two chapters early while you are still drafting, rather than in a beta reader's margin note six months later.
Spell check was a given. Grammar check should have been, since Microsoft Word shipped it in Office 95, and I was dumbfounded to find that prose editors mostly still don't have it. So Draftline does, as a deterministic rules engine that runs entirely on your machine and never sends a sentence anywhere.
Contextual usage detection covers the territory between spelling and grammar, where nothing is technically wrong but a copy editor would still reach for a pencil. Everything it finds appears inline, as a suggestion you keep or ignore:
Every trendy writing app right now is trying to write your story for you, and the writing world is rightfully up in arms about it. I had no interest in building another ghostwriting app, so the editor itself contains no AI at all. The AI Studio is a separate plugin, disabled on a fresh install, and even when you switch it on it cannot send a word anywhere until you connect a provider of your own. What it does, once you have, is edit prose you already wrote.
I also built the thing I kept seeing writers ask for on Reddit: AI detection rates, shown to you. Plenty of authors want to use Claude or ChatGPT or Gemini as an editor and worry their book will be flagged as AI-generated afterward. In Draftline, if an edit pass costs a passage your voice, you can see that in the detection panel and reverse it before the chapter ever leaves your machine.
And every suggestion arrives in an inline diff view, borrowed directly from how code editors and version control show changes. You accept or reject each one individually, instead of squinting at a block of rewritten prose and trying to work out what the machine touched.
Under the hood, the tools are plugins you can turn off: the spelling and grammar engines, character detection, Read Aloud, the AI Studio, and the manuscript analysis all have a switch in Settings, and the editor keeps working with any combination of them disabled. I built it that way because I wanted to be able to give you everything and still let you write with as much or as little help as you want.
If you want a silent page and nothing else, you turn it all off. If you want the full studio running while you draft, you turn it all on, and the only cost is a few more panels.
The truth is that I wrote Draftline for myself, but I was proud enough of what it became that I wanted to give it to the world. I considered making it another paid program, and I decided to open source it instead, so that every writer, hobbyist and professional alike and regardless of what they can afford, could use it. The first-time indie author and the bestselling novelist download the same app.
Will there ever be a pro tier? Maybe someday, for convenience features that carry real cloud costs, such as syncing across devices or hosted backup. What I can promise is the part that matters: the editor itself will always be free, full-featured, and open source.
On your machine, in your own files, and in a cabin with no bars on the phone if that is where the book gets written.