use case / github repo access
The product is the repo. Sell it that way.
Boilerplates and starter kits age badly as zip files. Selling repository access gives buyers the code, the history, and every future commit — and Keyplar automates the invitations so you never touch a collaborator list.
the usual way
What you'd otherwise be building
- 01
Manual invites don't scale
Checkout at 2 am, buyer waits until you wake up to be added. Every sale is a chore, and every refund a repo you forget to clean up.
- 02
Zips go stale on day one
The moment you fix a bug, every previously delivered zip is outdated. A repo pulls; a zip rots.
- 03
Access that leaks
Shared zip links float around. Repo access is bound to one GitHub account and revocable at any time.
with keyplar
How Keyplar handles it
- Buyer claims once with their GitHub username; the invitation to every included repo goes out automatically
- One benefit can grant several repos — the kit, the examples, the private issue tracker
- Roles per repo: read for code access, triage if buyers should file issues
- Refunds and cancellations remove collaborator access and withdraw pending invites
- Pair with a subscription product for sponsorware: access lives while the subscription does
Example setup
Next.js SaaS Starter Kit
one product · 3 benefits attached
acme/starter-kit + acme/examples · read
Setup walkthrough & env template
Private Discord invite
granted on payment · revoked on refund
order.paid → delivered
Stop being your own collaborator bot.
Attach a GitHub benefit and every sale invites itself — refunds clean up too. Free for 14 days.
14-day trial · $29/mo after · cancel anytime