GitHub City VS RepoAccess

RepoAccess's answer:

It is not a billing platform. RepoAccess is a single-purpose access-grant worker you host yourself on Cloudflare, wired to the payment provider you already sell with. A buyer pays and is invited to the GitHub team that carries your private repo; a refund or chargeback takes it back. Nobody sits between you and GitHub, there is no per-sale cut, and your checkout stays yours.

Revocation is per product, not per person: a buyer who owns two of your products and refunds one keeps the other, because membership is reconciled against live GitHub state rather than the worker's own records.

RepoAccess's answer:

Two groups solve this, and the differences are not the same in each.

The billing platforms - Polar, Dodo Payments, GitHub Sponsors, Anystack, GitPaywall - hand you a checkout and take a percentage of every sale forever. They are also Stripe-bound, which locks out sellers across much of the CIS, MENA, Africa and Asia. RepoAccess inverts that: you keep your provider, your margins and your region, and the grant logic runs on your own infrastructure.

The self-hosted tools - HonorBox, Pay2Clone, SellRepo, Lemonrepo - share that premise, so the differences are narrower and more concrete. Provider coverage: HonorBox is Stripe-only, Lemonrepo is a Lemon Squeezy template; RepoAccess ships Stripe in the open-source core and adds Paddle, Lemon Squeezy, Gumroad, Razorpay and Telegram Stars.

Buyer identity: no "Login with GitHub" - GitHub's own invitation is the check, so nothing extra holds your buyers' accounts.

And what a refund actually does: revocation is per product rather than per person, pending invitations are cancelled, membership is reconciled against live GitHub state rather than a local record, and chargebacks follow a separate path that never restores access on its own.

The core is open source, so the code holding your GitHub credentials is code you can read before you run it.

RepoAccess's answer:

Developers who sell code as a repository: SaaS boilerplates and starter kits, paid courses with a codebase, AI notebooks, private modules, paid community resources. Anything delivered as a repo rather than a download.

It fits solo sellers and small teams who already have a payment provider and do not want a platform between them and their buyers, and it is especially relevant to sellers outside Stripe's footprint, who are excluded from most of the alternatives by default.

RepoAccess's answer:

I needed to sell access to a private repo and found that every ready-made answer assumed Stripe. Stripe was not available to me, and the tools built on top of it were therefore not available either - the problem was not the GitHub part, it was that the GitHub part came welded to somebody else's checkout. So I separated them: a small worker that takes a webhook from any provider and does the GitHub work, running on infrastructure I control. The core is open source because the thing holding your credentials should be readable.

RepoAccess's answer:

TypeScript on Cloudflare Workers, with Cloudflare Workflows for the durable grant and revoke chain, Hono for routing, and the GitHub REST API for invitations and team membership. It deploys with Wrangler to your own Cloudflare account and runs inside the free plan for hundreds of sales a day.