Thanks.dev is a sponsorship management platform for open source maintainers. It aggregates inbound funding from multiple sources (GitHub Sponsors, Open Collective, individual invoices), handles compliance, and pays maintainers in their preferred currency. It's a finance layer for OSS maintainers.

What does Thanks.dev do that BreakPoint doesn't?

Thanks.dev handles tax compliance, multi-platform payout consolidation, and enterprise billing for maintainers who get sponsorship from many sources. BreakPoint is not a payments or financial product.

What does BreakPoint do that Thanks.dev doesn't?

BreakPoint finds a new maintainer when the current one leaves. Thanks.dev assumes the current maintainer is staying — it just makes their money flow better. If the maintainer is gone, no amount of payment optimization helps.

Are Thanks.dev and BreakPoint competitors?

No, they're complementary. A maintainer can use Thanks.dev to optimize their income while they work on the project, and use BreakPoint to plan the eventual handoff.

When would I use Thanks.dev vs BreakPoint?

Use Thanks.dev if you maintain an OSS project and want to consolidate your sponsorship income into a single payout. Use BreakPoint if you want to find a project to adopt, or if you need a graceful way to step back from maintaining something.

Yes. A maintainer sets up Thanks.dev for the active period, and BreakPoint for the handoff plan. A contributor uses Thanks.dev (or similar) to fund a maintainer, and BreakPoint to find the next project to adopt if their first choice goes dark.

Comparison

BreakPoint vs Thanks.dev

Thanks.dev is sponsorship management for OSS maintainers. BreakPoint is the second-chance platform for any project. Different layers — money routing vs maintainer handoff. The two work together.

Quick comparison

Dimension	Thanks.dev	BreakPoint
What it is	Sponsorship payout & tax platform	Adoption network for abandoned projects
Solves	"How do I get paid cleanly across multiple sponsorship platforms?"	"How do I find a new maintainer when I leave?"
Primary user	Active OSS maintainer	Stepping-back maintainer + aspiring adopter
Vertical	Code only	8 verticals
Pricing	% of processed sponsorship	Free + Pro $99/mo, Team $499/mo
Integrations	GitHub Sponsors, Open Collective, etc.	GitHub repo metadata, embed widget, public listings

The deeper story

Thanks.dev is a real piece of plumbing that solves a real problem. OSS maintainers in 2026 often get sponsorship from many sources at once: GitHub Sponsors, Open Collective, Polar, individual invoices, a one-off company. Consolidating that into a single payout, with the right tax handling, used to be a nightmare. Thanks.dev makes it bearable.

But thanks.dev assumes the maintainer is staying. If the maintainer is leaving — by choice or by circumstance — all the payment optimization in the world doesn't help. The project goes dark. The users depending on it scramble.

The mature answer: set up thanks.dev while you're active, set up BreakPoint before you step back. The two together cover the full lifecycle. A maintainer who plans for both is the kind of maintainer the open source ecosystem needs more of.