Launching today
HonorBox
Sell digital products with just Stripe and GitHub
61 followers
Sell digital products with just Stripe and GitHub
61 followers
Your storefront is a static site on GitHub Pages. Checkout is a Stripe Payment Link on your own account. A scheduled GitHub Action delivers each sale by inviting the buyer to your private repo.
HonorBox
The Stripe + GitHub combo is clever since it skips a database entirely — repo as the product store, Stripe as the ledger. What happens if a buyer needs a refund or you want to revoke access after the fact, does that require manually editing repo permissions? Also curious how you're handling license key delivery if a product needs one, since that's usually the part that turns "just Stripe" into a real backend.
HonorBox
@leo404 No manual permission editing. The free engine keeps your books in a ledger and delivery is one scheduled Action, so revoking is removing the collaborator, one call or one click, and the reconcile pass will tell you if paid access and actual access ever disagree. Pro automates the refund case end to end: a refund guard watches Stripe and revokes the buyer's repo access on its own when a refund lands. On license keys, you're right that this is where 'just Stripe' usually grows a backend, which is why I kept keys out of the delivery path entirely. Access IS the repo invite. If your product itself needs keys, Pro ships an ed25519 license module: keys signed in CI, verified offline in your app with drop-in snippets for JS and Python, still no server
HonorBox is listed across Payments, Developer Tools, Productivity, and Social & Community, which makes me wonder about the first target user. Is this mainly for makers/dev teams handling rewards or recognition, or is the payment angle more central? A concrete example workflow would help place it quickly.
HonorBox
@mia_qiao Payments is the whole point, the category spread is just tagging. The first target user is a developer selling a code-shaped product to other developers: a CLI, a template pack, a course that lives in a repo, a paid tool. Concrete workflow: fork the template, edit one config file, run the init script with a restricted Stripe key and it creates the product, price and payment link for you, turn on GitHub Pages and the store is live. Your buyer clicks buy, pays on Stripe, types their GitHub username at checkout, and a scheduled Action invites that username to your private product repo. The storefront I sell from is this exact engine unmodified, so the demo is the source.
This is such a clever use of tools developers already trust. Stripe handles the money, GitHub handles access, and HonorBox just connects the two.
How long does it usually take from payment to getting access to the private repo? And what happens if the buyer uses a different email for Stripe and GitHub?
Really smart idea. Congrats on the launch!
HonorBox
@john_heaton06 Thanks! Usually within minutes, always within a few hours in the default polling mode, and there's an opt-in webhook mode if you want it near-instant. The email question is the nice part: emails never have to match, because delivery doesn't key on email at all. Checkout asks for the buyer's GitHub username as a custom field and the invite goes to that username, so their Stripe receipt can go anywhere. And since GitHub expires an unaccepted invite after seven days, the engine re-issues it before that happens, a buyer who missed the notification doesn't lose what they paid for.