For everyone whose buyers live on GitHub
Sell digital products with just Stripe + GitHub.
0% platform fee, $0/month, no server. A static storefront on GitHub Pages, checkout through your own Stripe account, and a GitHub Action that delivers every sale while you sleep.
This store runs on the engine it sells. Fork the free core and open your own stand.
An empty ledger looks the same whether nobody came or your store is silently broken. Pro is the suite that tells those apart, before your first sale and on every push after it.
- Conformance suite: 16 checks for the known ways this architecture loses money quietly, each proven able to fail, wired to a CI gate that goes red when your setup drifts
- Catches a dead buy button (a deactivated link still answers HTTP 200), a price on the page that differs from what the link charges, a pasted URL that makes every sale unmatchable, and a live 100%-off coupon
- Store doctor: preflight your config, payment links, and fulfillment permissions before launch
- Reconcile: cross-checks Stripe against GitHub to prove every paid order actually reached its buyer, and names the ones that didn't
- Ops bots: auto-acknowledge new support issues, auto-revoke repo access when Stripe refunds
- Stats: tracker-free sales analytics rendered from your Stripe data, one command
- 4 more storefront themes; the terminal theme is published in the free repo as a full code sample
- License-key module: ed25519 keys signed in CI, verified offline in your app (JS + Python)
- Commerce playbook: pricing, the first ten sales, EU VAT, multi-product catalogs (table of contents is public)
- Priority support label on the issue tracker
New
10 specialist agents and 14 discipline skills for Claude Code, designed as one system and installed in one command.
- 10 specialist agents: reviewer, debugger, planner, tester, security, perf, refactorer, docs, simplifier, captain
- 14 discipline skills: TDD, verification-before-done, PR authoring, accurate changelogs, safe shipping
- Six safety hooks: git, shell, exfil, scope and secret guards, plus post-edit format (commented, auditable shell, with test suites)
- CLAUDE.md starter templates for solo and team repos
- One-command installer with dry-run, conflict detection, and clean uninstall
- Free tier on GitHub: 3 agents + 3 skills, MIT, try before buying
30 days, no questions asked, refunded through Stripe to the card you paid with. And because the engine is MIT-licensed and delivery is a private repository your GitHub account keeps, what you buy does not stop working if this project does. It is new, and the release history says exactly how new.
Five themes, one config line
Real screenshots of this same storefront rebuilt with each theme. Terminal is in the free repo as a full code sample, so Pro adds the other four.
How the honor box works
Fork the stand
Fork the free, MIT-licensed engine and edit one config file. Your storefront builds to GitHub Pages; hosting costs $0, forever.
Put out your goods
Create a Stripe Payment Link for each product and drop the URL in the config. Buyers pay you directly on your own Stripe account, so the money never sits with anyone else on its way to you.
Let the box collect
A scheduled GitHub Action polls Stripe, invites each buyer's GitHub account to your private product repo, and keeps your books. No webhooks, no server, no database.
The one hard requirement: your buyers need GitHub accounts, because delivery is a repo invite. The second thing to check is your volume. At ten sales a month of a $29 product the fee you would save against a merchant of record is about $8, and for that $8 they do your VAT, which is the better trade; the first guide below has the arithmetic. This earns its keep at volume, or when owning the Stripe account and the customer relationship matters to you for its own sake.
Side by side
Fees as published on each vendor's own pricing page, checked July 2026. Polar is the closest comparison: it delivers private-repo access natively and instantly, and it handles your VAT. If you want a merchant of record, one of the first three is the better tool, and the guides below say when.
What you can check before you buy
This project is days old, so it has no track record to point at. These are the substitutes, and every one of them is something you verify yourself rather than something we assert.
scripts/fulfill.js is the entire fulfillment path: poll Stripe, match the order, invite the buyer. No dependencies, no framework, readable in one sitting, and public before you pay a thing.
The store you are standing in is generated by the engine it sells, from a config file in the public repo. The checkout you would go through is the one your buyers would. It is the same artifact, not a demo of one.
Every change tagged, with notes naming the limits as well as the features. It also shows exactly how young this is, which is worth knowing before you spend anything.
The engine is MIT and that cannot be withdrawn later, by us or anyone. Your store runs on your Stripe account and your GitHub Action, so no server of ours sits in the path of a sale, and nothing switches off if this project goes quiet.
Straight answers
What exactly do I get when I buy?
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
Why is there no instant download?
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
Do my buyers need GitHub accounts?
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.
Do I need HonorBox Pro to use the engine?
No, and you should start on the free core. It is a working store: checkout, fulfillment, docs, two themes. What it does not do is tell you whether a specific order actually reached the person who paid for it. An empty ledger and a broken store look identical from the outside, and you find out from the buyer. Pro is the half you want once money is moving: sixteen checks for the known ways this architecture loses money quietly, run against your own account on every push. Buy it when you have orders to prove, not to feel like you have started.
Does the fulfillment bot need my full Stripe secret key?
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
What about VAT and sales tax?
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
Refunds?
30 days, no questions asked, refunded through Stripe to your original payment method. Repository access ends when a refund is issued.
Who's behind this, and how new is it?
An independent, MIT-licensed project. It publishes no company name or legal identity, and contact is honorbox@proton.me. It is also new: the first commit is dated 18 July 2026, so there is no track record here and no point pretending otherwise. What there is instead: the engine that takes the money is public, this store is built by it, the release history is dated, 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
Guides
Gumroad, Lemon Squeezy, Payhip, Paddle, plain Stripe, DIY: the real fees and when each one wins.
The two big platforms against your own Stripe account: fees from their live pricing pages, the per-sale math, and when not to DIY.
The complete guide: checkout, delivery options, refunds, and the tax paragraph nobody writes.
Private-repo delivery done right: access control, revocation, invite limits, and token discipline.
The direct route: Stripe checkout, GitHub delivery, the running costs added up, and when a marketplace earns its cut.
