Private testing · Waitlist open
Write in a browser. Build the printed book with one click.
Imprimatur turns a manuscript written in your browser into a print-ready 6×9 PDF and a store-ready EPUB, and reviews the prose and builds the index on the way. No LaTeX, no InDesign, no code anywhere in the path.
The control plane, from the inside
The control plane, from the inside
64The page count is a fact
Other tools multiply words by a guess about typography. Imprimatur composes the real book in the real typeface at the real trim size, so 371 pages is a measurement, not a projection.
The EPUB is validated here
epubcheck runs as part of the render, not afterwards. If something is wrong you learn it now, and not from a store rejection three days later.
Your text is never code
Each render runs with no network, a read-only filesystem and no privileges, in a container thrown away when it finishes. The prose review and the index run in that same container. There is nothing in the path for a manuscript to execute.
In the editor
What sits beside the manuscript
An image library
PNG and SVG, and two files with one name are one picture: the SVG prints sharp at any size, the PNG goes in the ebook. No PNG? One is drawn from the SVG when the book is built.
A prose review
Rules for the book’s language, a spelling check, and a terminology sheet that is yours: the form this book writes and the forms to flag. A gate you set withholds the downloads while a must-fix remains.
An analytic index
Select a word, mark it, add a sub-entry. The index is generated with true page numbers, and a checker names the terms with no main reference, the near-duplicates and the orphan sub-entries.
Statistics that are facts
Words per chapter, an ebook reading time, and the page count from the last build rather than a guess. Writing per day shows the words you removed beside the ones you added, because editing is most of writing.
A history of sittings
Every writing session is recorded, with what it added and what it removed, and any one of them can be restored. Undo works too.
Import from Markdown
Paste or choose the manuscript you already have. Whatever a book cannot hold is named, line by line, rather than silently dropped.
The part nobody advertises
A 348-page edition once shipped with fifteen blank pages printed into it.
That is what happens when chapters end on the wrong side and nobody counts. Imprimatur counts — blank pages, widows, missing glyphs, a font that quietly substituted itself — and puts every one of them in the report before the file leaves. And the prose review reads the words before a single page is set.
Written with it
The pipeline has already made a book you can buy.
Kubernetes 101, 371 pages, written in evenings and typeset by the same two-pass build. Imprimatur is that toolchain with the terminal taken off the front.
See the book →Bring your own agent
Your agent can work the manuscript. Only if you open the door.
Any tool that speaks MCP — Claude Desktop, Claude Code, a local model — can list your books, read a chapter, write into it and build the book, with a token you mint and can revoke. Imprimatur runs no model and holds no key: nothing of yours reaches a model unless you connect one.
Over stdio today, with Claude Desktop, Claude Code and any local MCP client. The remote connection follows the public launch.
- OffThe default. No agent can see the book.
- Read-onlyAn agent can read and build, never write.
- Read-writeAn agent can also edit the manuscript. Every change lands in the history and can be restored.
Where Imprimatur actually is, today
- No public sign-up yet. Accounts exist for invited testers; the waitlist is the only door.
- No pricing, because it is not decided.
- No collaboration or comments yet. Every writing session is kept and can be restored.
- Editor, live ebook preview, one-click print PDF and validated EPUB, prose review, analytic index and your own agent all work today.
Be there when it opens.
One email. Nothing else, ever.