Architecture, sequence, and dataflow sit in the chapter — a hard idea is a picture first.
These are print-checked figures from the book pipeline, not clip art.
No publisher writes a book for an audience of one. Until now, neither could you.
You pick the genre, the chapters, and the order. Technical books are researched and diagrammed. Story Studio books are written in the voice you set. Then PenMyBook binds the book.
A technical topic and URLs you trust — or tone, point of view, and a world.
Print-checked figures for technical books. Generated art for Story Studio.
Cover, contents, and chapters — digital PDF, KDP print, or Kindle.
When I need a guide that does not exist, I want my topics, my sources, and print-checked figures — so I study one coherent book, not 30 tabs.
Architecture, sequence, and dataflow live in the chapter. Python programs can sit beside the prose; the Reader shows an honesty chip when a program did not type-check clean. Print does not.
When I am writing fiction, a script, or a children’s book, I want tone, point of view, and generated art — so the book holds a voice, not an architecture diagram.
Science fiction, literary fiction, screenplay, and children’s books. Research stays on the technical path.
When the chapters are in, I want a cover, a table of contents, and a format I can actually use.
Digital PDF, a KDP print PDF with a wrap cover, or a Kindle package. You can also edit a chapter, add more, or branch a version.
Learn a stack no single title covers — researched, diagrammed, and bound. An AWS exam path is one example, not the only book this makes.
Turn a curriculum into chapters in your order. Technical subjects get figures. Story subjects get illustrations and the voice you set.
Bring an outline and trusted sources, or set Story Studio and write the novel, script, or children’s book. Your name on the cover, then a file you can read or publish.
Technical books write from the URLs you add and from research, then a reviewer pass rewrites the prose. Story Studio books are grounded in world and voice — not sold as a paper trail.
You design every chapter and subtopic, and you pick the genre before a word is written. Story Studio sets tone, point of view, rating, and audience.
Architecture, sequence, dataflow, and charts — print-checked figures, not clip art. Technical books only; other genres use generated art.
Live progress as research and chapters land — no black box, no silent wait.
A reviewer stage rewrites for quality before the book is bound.
Cover and table of contents included. Bind a digital PDF, a KDP print PDF with a wrap cover, or a Kindle package.
A bound book has a cover, a table of contents, the pictures that belong to the genre, and a file you can download. The tiles below are layout samples, not a screenshot of one finished title.
A technical subject plus URLs you trust, or Story Studio settings for fiction, a script, or a children’s book.
Converse with the topic planner until the chapters and order match your mental model exactly.
Drafted chapters and a reviewer pass, watched live. Technical books add research and figures. Story Studio adds illustrations.
A bound book with a cover and table of contents — read it here, or download the format you need.
“I wanted to clear the AWS SA Pro — so I forged the exact book for my path. My friend read what it produced and didn't want to put it down.”
— PenMyBook, built by its first user for its first problem
PenMyBook started because no book taught LangChain and Pydantic AI together, in the order one learner needed. The same workshop now also writes science fiction, literary fiction, screenplay, and children’s books — illustrated, not diagrammed.
A technical book writes from the sources you provide and from research, then a reviewer pass rewrites the prose. That is not a guarantee every sentence is true, and inline citations appear only when source references are turned on. A Story Studio book is written from the world and voice you set. It is not a researched paper.
You design the chapters and subtopics, and you choose the genre. Technical books get architecture, sequence, dataflow, and charts. Science fiction, literary fiction, screenplay, and children’s books get generated illustrations and Story Studio controls — not those figures.
Each week you can write one free chapter and generate one free cover, then you see real output before you add funds. After that you pay for the chapters, covers, edits, and binds you run. Stop whenever you want; what you have paid for stays in your account. No monthly fee.
Yes. You can bind a digital PDF, a KDP print PDF with a wrap cover, or a Kindle package, each with a cover and a table of contents. DOCX is not an export.
The book stays in your account to read, download, and publish. What you have paid for is not taken back when you stop.
Not available yet — shown so you know where PenMyBook is headed, not to oversell what ships today.
Libraries and tools go stale fast. PenMyBook will flag outdated coverage and let you refresh just the affected chapters from fresh sources.
You can already edit chapters, figures, and the cover. An automated fact-check of the prose is not part of generation. Technical Python shows an honesty chip in the Reader when it did not type-check clean. That chip is not printed.
Ask the editor to rewrite a passage, add chapters to a finished technical book, or branch a version. Then export PDF, KDP print, or Kindle.
Plan it, write a chapter, and pay for the work you run.
One free chapter and one free cover each week. A full book, and the PDF, KDP, or Kindle file, come after you choose to pay for that work.
