The whole studio, surface by surface.
From the first Markdown chapter to a KDP-ready EPUB and narrated audio — every part of the workflow lives in one transparent project.
A book should be a repository, not a document.
Own the manuscript
Real files on disk in a transparent project folder — no opaque database, no lock-in.
Markdown-first
Every chapter is plain, inspectable Markdown you can read, diff, and move.
Git-friendly
A book behaves like a repository, so changes are reviewable and portable.
Version history
SQLite-backed snapshots protect edits — history without database lock-in.
Build for KDP from the first draft.
- Strict XHTML content documents
- KDP-safe CSS handling
- OPF package + manifest
- nav.xhtml + legacy toc.ncx
- Cover handling
- Metadata fields
- Keyword + description constraints
- Validation report before export
We say KDP-aware, not "guaranteed approval" — the pipeline prepares the artifacts KDP expects and flags what needs review.
Why AI authors need production systems, not bigger prompts.
Sources stay in sources/
Reference material lives beside the manuscript, so AI drafts cite from a stable, inspectable set of files.
A style guide per book
Each book carries its own style.md — voice and conventions travel with the project, not a chat window.
Chapters are real Markdown
Every chapter is a file you can open, review, and correct — not buried output you can't trust.
Snapshots protect edits
Version history guards against runaway changes, so you can experiment and roll back.
Make audio a structured workflow.
Chapter & full-book audio
Render narration per chapter or stitch the whole book — rebuilt from the same source after every change.
Voice casting & pacing
Per-character voice maps and pause cues let you shape how the book is read aloud.
Review before final render
A render-and-review loop keeps you in control — flag chapters that need another pass.
Narration is generated audio for review and playback — we don't claim finished professional audiobook production.
And the details that keep a book honest.
The studio is built from the same production-minded primitives you'd expect from real software.
Version history
SQLite-backed snapshots protect every edit — roll back without database lock-in.
Series support
Define a series and keep volume metadata coherent across every book.
Style guides
A style.md per book keeps voice and conventions with the project.
Custom CSS
KDP-safe CSS overrides for fine control over the exported EPUB.
Structure tools
Front matter, chapters, back matter, and nested sections — reorder by drag.
Validation report
A KDP-aware checklist flags what needs review before you upload.
Join the list for a file-first authoring studio.
We're building EffortlessAuthor in the open. Get launch updates and early access — no pricing or commitment yet.
- Early access to the studio
- Launch updates
- A say in the roadmap