Sell digital products with just Stripe + GitHub.

The engine is free and MIT: fork it, edit one config file, and you have a working store with checkout, fulfillment, docs and two themes. Nothing about it expires or phones home. The $29 is HonorBox Pro, a separate suite for a different problem: whether the store you just built is actually working. What the free core cannot tell you is whether a specific order reached the person who paid for it, because an empty ledger and a broken store look identical from the outside and you find out from the buyer. Start free. Buy Pro when you have a store to check. Fork the free engine

Your GitHub account is invited to the product's private repository, usually within minutes and always within a few hours. You keep access permanently, updates included. If the invite doesn't arrive, the recovery path is written down and ends in either access or a refund. If a delivery fails

Because the product is private-repo access, which a download link can't be: per-buyer grants, clean revocation on refund, updates included forever. A scheduled job sends the invite, usually within minutes, with zero infrastructure to run or break. Sellers who want seconds can turn on the optional webhook mode. A download URL is instant, and then uncontrollable. How instant delivery works

Yes. Delivery is a repo invite, so every buyer needs one. Fine for code, templates, courses aimed at technical people, and tools. The wrong channel for lay-reader ebooks, physical goods, or general consumers. Better to know that before your first failed delivery.

Keep it. Nothing here asks you to replace a setup that already works. Pro is the part worth adding, because it answers what a hand-rolled setup almost never answers for itself: is every paid order delivered right now, and is any of the known silent failures live in your store? Point it at what you already run. A minimal config naming your existing payment links and repos, plus one custom field on your payment link asking for the buyer's GitHub username, which is one API call and leaves the link URL unchanged. Reconcile, stats, the refund and dispute guards, the store doctor and the audit's money-path checks then run in full against your setup; the checks that only apply to the engine's layout skip and print why. The free engine is there if you ever want the storefront and the fulfillment glue too, and adopting it is a config file naming those same links and repos rather than a migration your buyers can see. Every line of this is checkable before you pay: the config, the checkout field, what runs in full, what steps aside with the lines it prints, and the limits. What runs on a store you built yourself

No. A restricted key that can only read Checkout Sessions runs the whole poll; it cannot move money, refund, or create anything. Pair it with a fine-grained GitHub token valid for just the product repo. The least-privilege guide in the docs shows the exact toggles. See the exact toggles

HonorBox is not a merchant of record. You sell on your own Stripe account, so tax obligations are yours. That's workable for most small sellers under registration thresholds, and Stripe Tax can automate it beyond that. The tax doc walks through what a small seller actually owes. What a small seller owes

30 days, no questions asked, refunded through Stripe to your original payment method. Repository access ends when a refund is issued.

An independent, MIT-licensed project. It publishes no company name or legal identity, and contact is honorbox@proton.me. There is no long track record here and no point pretending otherwise. What there is instead is a public record: the engine that takes the money is public, this store is built by it, the release history is dated from the first commit on 18 July 2026, and the refund is 30 days no questions. The support page sets out what an anonymous contact does and does not cost you, and what you are left holding if the project stops. Support and what you can check