sponsorflare is a Cloudflare Workers-based sponsorship and usage-billing layer developed by Jan Wilmake in January 2025. It enables developers to monetise their open-source tools and APIs by combining GitHub Sponsors with usage-based billing, deployed at the edge without a traditional backend.[1]
The core thesis: the standard path for monetising developer tools (Stripe + database + auth server) is heavyweight and discourages adoption. sponsorflare wraps the GitHub Sponsors flow with Cloudflare's infrastructure to create a lightweight, edge-native billing layer that any developer can drop in front of their Worker or API.[2]
A sponsorflare-protected endpoint checks for a valid GitHub Sponsor token before serving responses. Users who haven't sponsored are prompted to do so; sponsors get access proportional to their tier.
sponsorflare was integrated as the primary monetisation layer for uithub starting in November 2024, when Wilmake added a billing mechanism that charged API consumers based on usage.[3] The cloudflare-sponsorware repository on GitHub attracted attention from other founders in the agent-payments space.[4]
In early 2025, Wilmake pitched sponsorflare to Cloudflare's DevRel team as a potential collaboration — a reusable pattern for thousands of developers to monetise agent tools via GitHub Sponsors. He presented it as one of three key assets (alongside Workers for Platforms experiments and Durable Objects research) in discussions with Peter Saulitis (Cloudflare NYC) and Ricky (Cloudflare).[4]
The proposal was for a 6-month DevRel partnership; these negotiations stalled through March–April 2025 and were ultimately not formalised.[4]
github.com/janwilmake/cloudflare-sponsorware