Blog
Build in public
How to Sell Access to a Private GitHub Repo: Every Option Compared (2026)
Pillar comparison of every way to sell access to a private GitHub repo: GitHub Sponsors, MoR platforms, specialist storefronts, no-code, self-hosted tools, and the GitHub rules and hidden costs behind them.
Selling GitHub Repo Access for Telegram Stars: The Payment Rail with No Bank in the Loop
The Telegram Stars route for code sellers: a bot as the whole storefront, no bank or card processor anywhere in the loop, and automatic GitHub repo access delivery from a Cloudflare Worker.
Selling GitHub Repo Access with Paddle as Your Merchant of Record
Provider guide for sellers Stripe does not serve: Paddle as Merchant of Record carries tax and disputes, RepoAccess turns the Paddle webhook into a GitHub team invite and revokes access on a refund or chargeback.
Lemon Squeezy Is Becoming Stripe Managed Payments: What It Means If You Sell GitHub Repo Access
The migration read for sellers delivering paid GitHub repos through Lemon Squeezy: what is actually changing, what breaks, and how a Lemon Squeezy webhook becomes a GitHub team invite and a refund becomes a revoke on a delivery layer you own.
How to Sell Access to a Private GitHub Repo Without a SaaS in the Middle
Launch write-up for RepoAccess: an open-source Cloudflare Worker that grants GitHub team invites on payment and revokes them on refunds and chargebacks.
Edge-Native Feature Flags Without LaunchDarkly: Cloudflare Flagship for Indie SaaS
Feature flags as an ownership problem: a D1 baseline you fully control, the Flagship binding when it outgrows you, plan gating, kill switches, and the OpenFeature escape hatch.