Monetize your README. Every sponsor is opt-in.
No tracking scripts
Zero analytics, zero pixels. We count impressions on our server, never in your readers' browsers.
Static SVG. Zero JavaScript.
One image, no runtime, no redirects. GitHub's camo proxy caches it for sub-millisecond renders.
One line. Fully reversible.
Plain Markdown. Remove the line and the badge is gone — no contract, no notice period, no leftover data.
[](https://badgemint.com/r/your-repo)One line of markdown. Real revenue.
This is the actual badge endpoint — /b/{repo-slug} — rendered live. GitHub's camo proxy fetches it for every README view.
Sold badge
Sponsored state
[](https://badgemint.com/r/demo)
Unsold badge
Default state
Let readers know you're open to sponsorship. The badge stays in this default state until you accept a bid — no extra steps needed.
[](https://badgemint.com/r/your-repo)
Impressions on /demo
Each badge render that reaches us is logged. Coarse buckets protect the count oracle.
How it works
Add one line
Paste one line of Markdown. The badge renders immediately and stays in its default state until you approve a sponsor.
Approve sponsors
When a company submits an offer, you see the sponsor, message, CPM, and budget. Accept or reject with one click. Nothing appears without your approval.
Get paid
Every eligible impression is counted. You receive your share through Stripe Connect.
Funded by sponsors. Controlled by you.
Every sponsorship is opt-in. Every impression is logged. Everything is exportable.
Every sponsor is opt-in
Nothing appears on your README without your approval. Accept or reject any sponsor, for any reason, and pause sponsorships at any time — your badge immediately returns to its default state.
Conservative, privacy-first counting.
GitHub aggressively caches README images through its camo proxy, so many views never reach our servers. We only bill sponsors for requests we actually receive and never store raw IPs — counts stay conservative by design.
Every request is logged
Each badge request records the repository, sponsor served, timestamp, and a salted SHA-256 IP hash. Raw IP addresses are never stored.
Coarse public counts
Public statistics are shown in ranges (25+, 100+, 1k+, etc.) to prevent traffic probing. Sponsors see the same bucketed numbers.
Export everything
Sponsors can export impression logs. Maintainers get per-day, per-sponsor reporting. No black-box metrics.
What if something goes wrong?
Worst-case scenarios, and how the badge handles each one.
If we shut down
Your badge reverts to a plain link. No broken images, no 404s, no leftover dependencies. Swap for any other sponsor with one line.
If a sponsor turns bad
Pause them from your dashboard. Your badge reverts to default within a minute — they don't come back without your explicit re-approval.
If you change your mind
Remove the badge line from your README. No contract, no notice period, no eviction email. Pull the line and it's gone.
Reach developers at the moment of adoption.
The GitHub README is the highest-attention page in a developer's evaluation flow. You sponsor the maintainer; we place your badge directly on their README — opt-in, measurable, and verified.
Placements feel ambient, not pushed.
A badge sits inside the README the developer is already reading — not a popup, not a banner, not an interruption. The placement earns attention because it answers the question they came for.
Sponsor only repositories relevant to your product.
Filter by language, topic, or repo size. You choose which projects wear your badge — you don't buy impressions on pages you wouldn't want to be seen on.
Pay only for verified README impressions.
Bot traffic, duplicate fetches, and stale camo-proxy caches are filtered upstream. The bill reflects eyeballs the maintainer's audience actually cast.
Founding cohorts onboard in batches — current categories: developer tooling, infrastructure, AI dev-tools. Talk to us →
Join the private beta.
No sponsors or maintainers are live yet. We're onboarding both sides in private batches before launch — validating supply before demand.
Founding sponsors are being onboarded from developer tooling, infrastructure, and AI dev-tools.
Our launch cohort focuses on repos with 2k–50k stars, but maintainers of any size are still welcome to apply. Dev-tool companies looking to reach developers inside the projects they use should also reach out first.
Paste the badge. We'll handle the rest.
We're onboarding repos in small batches. Drop your email and we'll reach out.
Join the waitlistJoin the waitlist
Be first in line when we launch. We'll onboard both sides in small batches.
Maintainers
- • One line of Markdown
- • Approve every sponsor
- • Paid through Stripe Connect
- • Full transparency
Sponsors
- • Target by language and star count
- • Contact maintainers directly
- • Transparent billing
- • Reach developers inside projects they use