Your docs domain, your book
The shop resolves at a domain you own, with the certificate handled. This site's sitemap deliberately omits author storefronts, so the platform never competes 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 there was no publisher involved. The usual next step puts it on a page at someone else's domain, under their chrome, in their search results — which was a fair trade when that store was the only way anyone would find you, and stopped being one the day your newsletter outgrew it.
Does it handle code blocks, diagrams and monospace properly?
The in-browser reader renders your EPUB's own CSS, so a book that looks right in Calibre or Apple Books looks right here — syntax-highlighted blocks included. Preformatted text is wrapped rather than clipped, which is the one override applied, because a code listing running off the edge of a phone is the single most common way a technical EPUB fails in a paginated reader. SVG diagrams scale. What it will not do is run your code: there is no embedded terminal and no sandbox, and if an executable book is the product, this is not 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 version queue, no email asking readers to go and fetch it — errata reach people who bought the book eighteen months ago on the link that was already in their inbox.
A sample that is 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 is not inside it. Readers open it in the browser without downloading anything or making an 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
A card charge is created on your own Stripe account, so you are the merchant of record and the money is in your balance before we know it happened. There is no royalty, no split and 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 is an option per shop, not a requirement, and it settles into your wallet rather than 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 does not build a book and has no opinion about 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 is no reason to hand over a fifth of every sale — and, if you want the toolchain unthrottled, a membership on top of it.