Your docs domain, your book
The shop lives on a domain you own, with the certificate handled. Our sitemap deliberately leaves out author shops, so we never compete with you in search for your own title.
Sell your technical book from a domain you own
You wrote the manual your team needed, and no publisher was involved. The usual next step is a page on someone else's domain, under their branding, in their search results. That was a fair trade when the store was the only way anyone would find you. It stopped being one the day your newsletter outgrew it.
Does it handle code blocks, diagrams and monospace properly?
Yes. The in-browser reader uses your EPUB's own CSS, so a book that looks right in Calibre or Apple Books looks right here, syntax highlighting included. Preformatted text is wrapped instead of clipped. That's the one override we apply, because a code listing running off the edge of a phone is the most common way a technical EPUB fails in a paginated reader. SVG diagrams scale. What it won't do is run your code. There's no embedded terminal and no sandbox, so if an executable book is the product, this isn't the platform for it.
What you get
Ship a new revision without republishing anything
Upload a corrected EPUB and every past buyer's permanent link serves the new file. No store review, no queue, no email asking readers to re-download. Errata reach people who bought the book eighteen months ago, on the link already in their inbox.
A sample that's a real chapter
Choose how much of the book to give away and the sample is cut into a genuine EPUB. The rest of the file physically isn't inside it. Readers open it in the browser with no download and no account.
Site licences without a licensing system
No DRM and no device limit: a copy is a file, and a team that buys one gets a file. Every copy carries the buyer's name and a licence code, so a book that turns up on a paste site leads back to one purchase.
0% of every sale, at any volume
Cards are charged on your own Stripe account, so you're the merchant of record and the money is in your balance before we know it happened. No royalty, no split, no payout schedule, because nothing passes through here to take a share of.
Bitcoin, if your readers ask for it
Each order gets a fresh address derived from an extended public key only you hold. It's optional per shop, and it settles into your wallet, not an account here.
Bring the file you already have
Keep writing in whatever already works: Markdown and pandoc, Asciidoctor, Quarto, mdBook, Leanpub's own builder, LaTeX if it has to be. Inkwharf doesn't build books and has no opinion on how yours got made. It takes the EPUB that falls out at the end, checks it against the spec, and puts it behind a checkout on your own domain.
Coming from Leanpub?
Leanpub is a writing toolchain with a bookstore attached. Inkwharf is a bookstore you own, with no toolchain. If you write in Markdown and want the book built for you, stay on Leanpub. If you already have an EPUB and an audience, there's no reason to hand over a fifth of every sale, plus a membership if you want the toolchain unthrottled.