Your draft doesn't need another AI trying to write it. Kaizen R/W scans your manuscript, surfaces the small number of notes worth your attention, and learns what's intentional so the next pass gets quieter.
Upload a chapter. Get a handful of editorial notes. Teach the ones you disagree with. Each pass gets quieter. Reads chapter by chapter. Remembers across the manuscript.
Free tier included. No API key required. Your draft stays local until you run a scan.
Mara kept the lantern low as she crossed the ruined nave. The glass underfoot gave back almost no sound. At the altar she stopped, not because of the body, but because of the impossible neatness of it. Someone had arranged the dead boy's hands.
The first time she saw Daniel after the fire, he smiled in It made her distrust the kindness before she trusted the grief.
Outside, bells were already starting.
Kaizen isn't scoring your prose. It's learning how your manuscript should be read. The loop is simple: surface the few notes worth attention, respond once, and let the next pass get quieter.
Mara kept the lantern low as she crossed the ruined nave. The glass underfoot gave back almost no sound.
The first time she saw Daniel after the fire, he smiled in exactly the same way and she distrusted the kindness before she trusted the grief.
Outside, bells were already starting. Not an alarm. A welcome.
The highlighted line isn't a mistake. It's how this narrator judges people before the story proves her wrong.
She kept walking past the chapel entrance, where someone had left candles burning in glass jars.
She smiled the way people do when they have already forgiven themselves. The warmth in her expression was aimed at no one in particular.
It was a small chapel. The kind of place that always smelled like stone.
Voice: This sharpens character judgment while potentially flattening ambiguity. Worth attention, but not necessarily wrong.
Click Explain why, Got it, or Later on the left. Each one shapes how the AI reads future passages. That is the Kaizen loop: small decisions now, cleaner scans later.
notes from the first scan across a chapter
intentional patterns taught: a repeated metaphor, a character's dialect, a deliberate fragment
notes on the next scan. Only the ones worth your attention remain.
Kaizen reads what is already on the page. It keeps the manuscript at the center, surfaces notes in plain editorial language, and adapts when you explain what is deliberate.
The scanner marks only the passages worth another look: pacing, repetition, continuity, voice. Not a wall of generic AI feedback.
Open one note, make a decision, and keep reading.
Hover for the table of contents, jump chapters, filter marks, and keep your place. The interface stays quiet so revision still feels like reading.
Move fast without turning the book into software management.
When a line break, repeated image, broken grammar, or sharp judgment is intentional, explain it once. Future scans reuse that context instead of arguing with you again.
That is the difference between an AI tool that talks and one that learns.
Kaizen fits the stretch after draft one and before an editor or beta reader sees the manuscript. It's for writers who want higher-signal feedback without flattening voice.
Narrow on purpose: a better first reader for revision.
Writers need a product that's clear about where manuscript text lives, when it gets sent, and what happens in between.
Your manuscript, marks, and dictionary stay in your browser. Kaizen doesn't keep a server-side copy of your draft.
When you run a scan or interpretation, only the relevant text is sent over HTTPS through a stateless proxy to the provider you chose.
Your key stays in browser storage and is used only for the request you triggered. It's not kept in a server-side database.
You can always see what was flagged, what you taught it, and what got dismissed. No hidden background passes. No mystery state.
| What | Where |
|---|---|
| Manuscript, marks, dictionary, settings | Stored locally in your browser |
| Relevant chapter text for scans | Sent on request through a stateless proxy |
| Full manuscript, API keys, browsing data | Never stored server-side |
No. It reads the manuscript you already wrote and points to places worth another look. You decide what to change.
No. It helps you do a stronger revision pass before your pages go to other humans. It's a first reader, not the final authority.
Most AI tools show up during drafting. Kaizen shows up during revision. It focuses on reading your existing manuscript, then reducing repeat noise as it learns your intent.
That is the point of the teach loop. Explain an intentional choice once and future scans should get quieter around it.
No. The free tier is hosted and ready to use. You can start reading without configuring anything. Bringing your own key is an option for writers who want a different provider or unlimited use.
Novels, novellas, and short fiction in revision. Best for draft two through final. This isn't a first-draft tool and not a grammar checker.
It reads chapter by chapter, with marks persisted across the full manuscript. A cross-chapter summary is available on the Pro tier.
The relevant chapter is sent through a stateless proxy to the AI provider. Nothing is stored server-side. Your full manuscript never leaves your browser unless you ask for a scan.
The free tier includes generous limits for scanning and reading. Pro is $20 a month for heavier use and stronger readings. Or bring your own API key for unlimited use at your provider's cost.
Before. It helps you do a stronger revision pass so your pages arrive cleaner when they reach other humans.
Enter your email and start reading in minutes. Free tier included.
We send one email with your personal reading link. No passwords, no accounts, no newsletter.
