Sponsor models OSS: GitHub vs Open Collective

The sustainability of open source projects depends on the ability to raise funds efficiently. In 2026, the two dominant platforms for OSS monetization are GitHub Sponsors and Open Collective. Both solve the open source sustainability problem, but with significantly different models, fees, and features. In this article, we analyze the pros/cons of both solutions with real data and operational strategies.

The problem of OSS sustainability in 2026

In 2025-2026, according to GitHub's Octoverse survey, 60% of OSS maintainers work part-time on projects that have millions of downloads. Yet, the vast majority receive no compensation. This creates a burnout problem, project abandonment, and misaligned incentives between users (who gain value) and developers (who provide free labor).

The two main sponsorship platforms seek to close this gap:

• GitHub Sponsors: natively integrated into GitHub, leverages the already-established relationship between developers and the platform, minimal fees, payments via Stripe.
• Open Collective: independent platform, total financial transparency, multi-currency support, asset sharing between teams, "fiscal-first" model.

Choosing between the two is not trivial and depends on project size, governance model, sponsor geographic base, and transparency needs.

GitHub Sponsors: the native approach

GitHub Sponsors was launched in 2019 and represents GitHub's native offering for project monetization. The approach is embedded: the "Sponsor" button appears directly in the repository profile, next to Star, Fork, and Watch.

How GitHub Sponsors works

GitHub Sponsors allows maintainers to enable sponsorship via their personal or organizational GitHub profile. Sponsors choose a contribution level (e.g., $5, $10, $25, $100/month) and GitHub handles billing via Stripe, depositing funds into the developer's bank account.

The technical flow is:

# 1. Enable sponsorship in your GitHub profile
# Settings → Developer Settings → Sponsors
# Connect your bank account via Stripe
# (or PayPal, if available in your region)

# 2. Configure sponsorship tiers
# Levels: $5, $10, $25, $100 (customizable)
# Description: what sponsors receive (badge, mention, private repo access, etc.)

# 3. Add the button to your README
# GitHub Sponsors badge and direct link in the repository

# 4. GitHub processes billing
# Recurring payments via Stripe Connect
# Monthly settlement to your bank account

# 5. Analytics dashboard
# GitHub dashboard: earnings, sponsor count, retention rate

GitHub Sponsors fees

GitHub does not apply commissions on direct sponsorships. However, there are indirect costs:

• Stripe Connect fee: 2.2% + $0.30 per transaction (on recurring payments). This is the main cost.
• Currency conversion: if you receive sponsors from non-euro countries, Stripe applies a 1-2% markup on the exchange rate.
• Minimum payout: GitHub pays when you reach $25 in balance (some regions may have higher minimums).

In total, the net cost on a $5/month sponsorship is about $0.41 (Stripe fee), leaving you $4.59. On $100/month, the cost is about $2.50 (25% less than the equivalent percentage).

Open Collective: the transparent and collaborative approach

Open Collective was founded in 2015 with a different ideology: total financial transparency and support for teams/collectives (not just individuals). The platform is built around the concept of a "virtual financial organization" that collects funds, makes all expenses public, and distributes contributions among team members.

How Open Collective works

Open Collective acts as a financial intermediary: sponsors pay Open Collective (via Stripe, PayPal, or bank transfers), and Open Collective deposits funds in a virtual account for the project. The project can then request funds (withdrawal) and specify exactly how they were spent.

The flow is:

# 1. Create a Collective on Open Collective
# https://opencollective.com/create

# 2. Configure the fiscal transition
# Open Collective supports 3 models:
# a) Open Collective Host (OCUSA - manages taxes for you)
# b) Independent Fiscal Sponsor (e.g., Open Collective Europe, Software Freedom Conservancy)
# c) Your own legal entity (if you're already a company/non-profit)

# 3. Define sponsorship tiers
# Levels with descriptions, badges, private repo access, etc.

# 4. Add the fundraising module to your site/README
# 

# 5. Receive transactions
# Sponsors pay via Stripe, PayPal, bank transfer
# All payments are recorded publicly in the "Ledger"

# 6. Request funds (withdrawal)
# Specify an expense: salary, server, merchandise, event, etc.
# Open Collective moderators approve (for OCUSA Host)

# 7. Receive payment
# Bank transfer, check, or donation to another Collective

# 8. Transparent finances
# All contributors, expenses, and balance are public
# Ledger visible at https://opencollective.com/yourproject/transactions

Open Collective fees

Open Collective applies a 5% commission + Stripe fee (2.2% + $0.30) on every payment received. Additionally, if you withdraw funds, you pay a 2% withdrawal fee on the total withdrawn (some methods have additional fees).

Based on a $100/month sponsorship on Open Collective:

• Stripe fee: $2.50 (2.2% + $0.30).
• Open Collective fee (5%): $5.00.
• Amount received in OC account: $92.50.
• If you withdraw $92.50: withdrawal fee (2%) ≈ $1.85.
• Amount in your bank account: $90.65 (~90.6% of original donation).

vs. GitHub Sponsors on the same $100 donation: ~$97.50 net (2.5% total Stripe cost).

Open Collective's advantage is not in cost, but in transparency, ease of team collaboration, and multi-currency support.

Feature comparison: GitHub Sponsors vs Open Collective

Revenue models and monetization strategies

The choice of platform is closely tied to the monetization model you intend to use. There are three macro-categories:

1. Individual sponsorship (solo)

Individual freelancers or solo maintainers benefit from GitHub Sponsors. The platform is simple, the cost is minimal, and it doesn't require complex governance. Cash flow is direct: sponsor → GitHub → Stripe → your account.

Ideal case: 20-50 sponsors at $5-$25/month. Monthly revenue: $200-$500. Total fees: ~2.5%. Net revenue: $195-$487.

2. Team/collective sponsorship

If the project has multiple maintainers, core contributors, or complex governance, Open Collective is the right choice. It allows you to:

• Share the balance among team members without intermediary bank transfers.
• Track who contributed and how much they received.
• Make spend requests (spend requests) that document the work done.
• Maintain transparency with sponsors (who see where their money goes).

Ideal case: Collective of 3-10 developers. Total raises $1000-$5000/month. Each member requests expenses ($500-$2000 for work done). Total transparency in public ledger.

3. Multi-tier sponsorship + upsell

Mature projects combine both platforms:

• GitHub Sponsors: base of small sponsors ($1-$25/month). Public announcements, badges, private repo access.
• Open Collective: enterprise sponsors ($500-$5000/month), visibility in public site, partner roles.
• Extra monetization: consulting, training, SLA support, certifications.

Ideal case (mature projects like Babel, Next.js, Vue.js):

• 100+ small sponsors on GitHub: $5000-$15000/month.
• 10+ enterprise sponsors on Open Collective: $10000-$50000/month.
• Consulting/support: $20000-$100000/year.
• Total: $15000-$65000/month in recurring revenue.

Real case studies (2026)

Babel (JavaScript transpiler)

Babel uses both platforms. GitHub Sponsors has ~800 sponsors totaling $25000/month. Open Collective (host: Open Collective Foundation) has $15000/month from enterprise sponsors. The team of 3-4 core maintainers divides contributions based on work done (tracked via spend requests). Total transparency: every expense is documented in the public ledger.

Model: 50% GitHub Sponsors (small) + 50% Open Collective (enterprise) + grants (Mozilla, Shopify).

Next.js (meta-framework React)

Next.js is maintained by Vercel (company). Sponsorship is a secondary revenue source. They use both platforms, but the larger revenue comes from:

• Vercel Cloud hosting (main product).
• Grants from foundations (Google, Microsoft).
• Corporate sponsorship (IBM, Google, etc.).

GitHub Sponsors: ~$8000/month. Open Collective (host: SFC): ~$5000/month. Total sponsorship: ~$13000/month, but it's a minor fraction of Vercel's total budget.

rustfmt (Rust code formatter)

Community-driven project. Uses Open Collective with Software Freedom Conservancy host. ~$3000/month from 150+ sponsors. The core team (4 developers) divides funds via spend requests. Total transparency: all expenses are public and approved by the community.

Model: 100% Open Collective + occasional grants (Rust Foundation).

Limitations and trade-offs

GitHub Sponsors: why doesn't it scale for teams?

GitHub Sponsors works well for individual developers but has three critical limitations for teams:

• No governance support: sponsorships go to a single GitHub account (or organization). To divide funds between members, you need manual transfers.
• No public transparency: your earnings aren't visible to sponsors. This can create distrust (why doesn't the project publish its budget?).
• No fiscal support: you're responsible for taxes. If the project is an international collective, it becomes complex.

Open Collective: why is it "slower"?

Open Collective has two perceived limitations:

• Higher fees (5%): every $100 of sponsorship costs $5-$10 in total commissions. On small projects, this weighs (e.g., $100/month becomes $90 net).
• Expense approval: when you withdraw funds, you must describe the expense and the moderator team approves. This adds latency (typical 24-48 hours) but also increases fiscal responsibility.

Technical setup: configuring both platforms

Enabling GitHub Sponsors

# 1. In the repository, create .github/FUNDING.yml
# This enables the "Sponsor" button in the repo profile

cat > .github/FUNDING.yml << 'EOF'
# GitHub Sponsors
github: [your-username]

# Optional: add Open Collective
open_collective: your-project

# Optional: other services
patreon: your-patreon
custom: ["https://example.com/sponsor"]
EOF

# 2. Verify the button in the repository
# GitHub → Repository → "Sponsor" button should be visible

# 3. In README.md, add a "Sponsor" section
# # Sponsoring
# If you love this project, support it with a donation:
# - [GitHub Sponsors](https://github.com/sponsors/your-username)
# - [Open Collective](https://opencollective.com/your-project)

# 4. Monitor analytics
# Settings → Sponsorships → View analytics

Configuring Open Collective

# 1. Go to https://opencollective.com/create
# Select type: "Open Source Project"

# 2. Choose a host (fiscal sponsor)
# Options:
# a) Open Collective Inc (OCUSA) - USA based, supports € and $
# b) Open Collective Europe (OCEA) - Europe, supports € mainly
# c) Software Freedom Conservancy (SFC) - ideal for non-profit FOSS

# For European projects, I recommend OCEA

# 3. Complete the profile
# Project name, description, logo, website, repository URL

# 4. Configure sponsorship tiers
# Example:
# - $5/month: "Supporter" (badge, mention in README)
# - $25/month: "Contributor" (badge, private Discord access)
# - $100/month: "Sponsor" (logo in site, email newsletter mention)
# - $500/month: "Partner" (custom benefits, README logo)

# 5. Add embed to README
cat > README.md << 'EOF'
## Support this project

[Support on Open Collective](https://opencollective.com/your-project)

EOF

# 6. Add embed module in HTML/Markdown
# 

# 7. Request your first funds (spend request)
# See official tutorial for approval process

Practical recommendations for choosing

Use GitHub Sponsors if:

• You're a solo maintainer or small team (1-2 people).
• You want to minimize fees and administrative complexity.
• Your project has a sponsor base primarily in Europe/US.
• You don't have strong public transparency requirements.
• The sponsor base is small (< $1000/month).

Use Open Collective if:

• The project has a team of 3+ core contributors.
• You want to maximize transparency toward your sponsors.
• The geographic base of sponsors is international.
• You have complex governance and expense tracking needs.
• You intend to use complex fiscal models (fiscal sponsor, non-profit, etc.).
• Revenue > $2000/month (fee cost becomes negligible in percentage).

Use both if:

• The project is mature and has worldwide visibility.
• You want to offer multiple sponsor options (GitHub as entry point, Open Collective for transparency).
• You plan to scale revenue in the medium-long term.

Frequently Asked Questions (FAQ)

Can I use both GitHub Sponsors and Open Collective at the same time?

Yes, in fact it's recommended for mature projects. There's no conflict: two different channels, two different audiences (GitHub for small sponsors, Open Collective for transparency + enterprise sponsors). Many projects (Babel, Vue, Next.js) do this.

If I change hosts on Open Collective, do I lose my funds?

No. The funds remain in the Collective's account. Changing hosts simply means changing who approves expenses and manages fiscal compliance. It's an administrative process, not a data loss.

Does GitHub Sponsors support one-time (non-recurring) donations?

Currently, GitHub Sponsors only supports recurring sponsorships (month/year). For one-time donations, use Open Collective's "Donate" button or tools like Stripe Donations.

Do I need to report sponsorship revenue for taxes?

Yes, always. Sponsorship revenue is gross income. If you're a freelancer, you must report it on your tax return. Open Collective with fiscal sponsor simplifies this part (the fiscal sponsor handles 1099s and tax forms). GitHub Sponsors doesn't—you're responsible for tax reporting.

How much revenue can I expect from an open source project?

It depends on project size and maturity:

• New projects (<1 year, <100 stars): $0-$100/month (few early-adopter sponsors).
• Established projects (1-5 years, 1000+ stars): $200-$2000/month (50-300 small sponsors).
• Mature projects (5+ years, 10000+ stars): $2000-$20000+/month (no limits, depends on project relevance).

Octoverse 2025 data shows that the median OSS maintainer receives $50-$500/month. The top 5% receive $5000+/month.

What happens if the project is abandoned?

If you withdraw funds from Open Collective and abandon the project, the balance remains yours. If instead you want the funds to go to a fork or another maintainer, you can transfer the Collective to a new owner via Open Collective admin panel.

Conclusion

In 2026, GitHub Sponsors and Open Collective are the two dominant platforms for open source project sustainability. GitHub Sponsors is the right choice for individuals and small teams, with minimal fees and native integration. Open Collective is ideal for collaborative teams and public transparency, with a slightly higher cost but much more robust governance.

The best strategy is to start with GitHub Sponsors (simplicity, zero platform cost) and add Open Collective as the project grows and your team expands. Combining both platforms allows you to capture sponsors at different engagement levels and maximize total revenue.

In the next article of the series we'll address advanced OSS sustainability elements: grants and foundations (Mozilla, Google), dual-licensing and open-core, and corporate sponsorship. Stay tuned.