Why we built Castwright

A novel is not a monologue. When you read a book, every character speaks in a distinct register — the gruff inspector, the clever child, the old woman who has seen too much. Your inner ear conjures them without being asked. The words on the page carry the instruction; your imagination executes it.

A single narrator, however accomplished, cannot do that. They can signal the shift — a pitch drop here, a softened consonant there — but every voice still passes through the same throat, the same timbre, the same rounding of vowels. The performance is real, often beautiful, but something of the book’s interior plurality is lost in transit.

We built Castwright because we wanted to hear fiction the way we read it: many voices, distinct, simultaneous, the ensemble the author wrote. The technology to do that locally, privately, on ordinary hardware has quietly arrived. The Kokoro engine produces clean, expressive English synthesis. Qwen’s voice-design model lets you describe a character and hear them. Coqui will let you lend your own voice to the narrator — voice cloning is in development for the next release. None of it requires a cloud account or a subscription to a large company’s API. It runs on your machine, with your books, and it stays there.

The full-cast form restores something specific: the pause before a character speaks, the recognition that this is a different person now, the accumulation of a voice over hours of listening. A minor character who appears three times becomes someone you remember. The antagonist’s tone stops being filtered through the narrator’s interpretation and arrives directly. The book sounds like itself.

That is the thing we set out to build, and it is what Castwright is. The public beta opens soon — join the waitlist and we’ll tell you the moment it’s ready.