Sell your GitHub repo. Keep 95.5%.

Your boilerplate, starter kit, or codebase is a product. Paywall it and get paid directly via Stripe.

Works with any URL: repo links, deployment guides, ZIP downloads, private docs.

Code as a product

Sell Next.js starters, SaaS boilerplates, scripts, CLI tools, or any codebase buyers would pay for.

Any delivery URL works

GitHub repo invite links, Dropbox ZIPs, Google Drive folders, private documentation, anything with a URL.

Instant access after payment

Buyer pays and unlocks the link instantly on the confirmation page. Backup link sent by email too. No manual onboarding needed.

Decide your delivery method

You have a few options: a private repo invitation link (buyers get added as collaborators), a ZIP exported to Google Drive, a PDF setup guide, or an invite to your private docs site. A ZIP on Drive is the simplest — one link, no manual invite management. A private repo link is more premium and gives buyers direct access to future commits.

Create your paywall

Paste your delivery URL into unseal.link, write a clear title and description that explains what the codebase includes, what it builds, and what stack it uses. Set your price. Developers buying boilerplates are professionals — be specific about what's included, what isn't, and what skill level the buyer needs.

Share on developer channels

Post on Hacker News (Show HN), IndieHackers, Twitter/X dev community, or relevant dev newsletters. GitHub README badges work well too — add a 'Buy' badge that links to your paywall. Developers find products through search and community, so write a clear title that matches what they'd type.

Buyers unlock instantly

Buyer pays via Stripe and unlocks the link instantly on the confirmation page. Backup link sent by email too. If you're using a private repo invite link, you'll need to manually add them as a collaborator after payment — your dashboard shows each buyer's email. For ZIP delivery, everything is fully automated with no manual steps.

Keep 95.5%

We take a 4.5% platform fee. Stripe fees apply separately. No monthly plans, no hidden cuts.

Frequently asked

Can I sell a public repo?

Technically yes, but it doesn't make much sense to paywall something anyone can already access for free. The better approach for public repos: sell a companion resource — a comprehensive setup guide, a video walkthrough, a deployment checklist, or a private fork with premium additions. The public repo builds trust and drives traffic. The paid companion is what people pay for.

What happens if I want to update the repo after selling?

If buyers have a private repo invite link, they're already collaborators and get updates automatically via git pull. If you used a ZIP file on Google Drive, update the ZIP and future buyers get the new version — existing buyers have the old one. If the update is significant, you can export your buyer list from your dashboard and email them with a note about the update.

Do buyers need a GitHub account?

Only if you're delivering via a GitHub repo invite link. For ZIP-based delivery, buyers just need an email address — they download the file directly from Google Drive or wherever you host it. Most developers buying boilerplates already have GitHub accounts, so this isn't usually a friction point in practice.

How is this different from GitHub Sponsors?

GitHub Sponsors is a recurring donation model — supporters pay monthly to support your open source work. unseal.link is a one-time product sale — buyers pay once and get a specific thing. They're not substitutes. If you maintain open source work and want ongoing support, Sponsors makes sense. If you're selling a discrete product (a boilerplate, a course, a codebase), a one-time paywall sale is the right fit.

Turn your code into income

Free to list. 4.5% fee per sale.