Open Collective: The Donation App With a Public Ledger

Most donation buttons are a leap of faith. You send money to a cause, a confirmation email arrives, and then the trail goes cold — you have no idea what happened to the $20 after it left your card. Open Collective is built around refusing that arrangement: it's an open-source donation app and platform whose core premise is that every group raising money has to show, in public, exactly what it did with it.

That's a claim worth checking against the actual code rather than the pitch. Open Collective's own GitHub organization — 103 public repositories, MIT-licensed, still shipping commits the day before this was written — is where that check happens.

What it is, in the project's own words

The platform's main repository README describes Open Collective plainly: "Open Collective is an online funding platform for open and transparent communities." Its stated purpose is to "provide the tools to raise money and share your finances in full transparency."

The org's GitHub profile sums up the pitch in four words — "Make your community sustainable" — and lists its location simply as "Earth," with 2,000 followers and a public repo count north of 100. This isn't one monolithic app; the product is split across a frontend, an API, and a handful of supporting services, each its own repository.

The mechanism: a group, not a bank account

Open Collective's unit of organization isn't a user or a nonprofit entity — it's a "collective," and the project's own community guidelines define that as "groups of people with a shared mission," adding that "people may come and go, but the mission remains." That framing matters for who actually uses this: open-source projects without a legal entity, mutual-aid groups, meetups, and climate or community initiatives that need to collect and spend money but don't want to (or can't) incorporate a nonprofit just to do it.

The same guidelines spell out the transparency obligation directly, not as a feature but as a behavioral rule for anyone running a collective: "Be honest about who you are, what your collective is doing, why you are fundraising and what you want to do with those funds." On most donation platforms, that's a trust assumption. Here, the project frames it as a condition of participation.

What the docs available this session don't spell out is the exact fee mechanics — how much a "fiscal host" (the legal entity that holds funds on a collective's behalf) takes, or how the platform's own cut is calculated.

The project's own issue tracker shows these aren't static numbers quietly buried in a pricing page: open issues reference "tiered Host fees" and a "platform tip" line item as live, actively-discussed product mechanics. That at least confirms the fee model is configurable rather than a single hidden percentage — but a fee structure exists and a specific current rate isn't something this piece can state as fact: opencollective.com's own pricing and terms-of-service pages were unreachable during this session's fact-checking, so no specific host-fee or platform-tip percentage is cited here.

The code behind the pitch

The flagship repo, opencollective/opencollective, functions less as an app and more as a public hub — its own README says "we're tracking all our Issues, RFCs and a few other documents in this repository" — and it's racked up 2,300 stars and roughly 1,600 open issues on that basis alone.

The actual product code lives elsewhere: opencollective-frontend, described on its own GitHub repo page as "A React app powered by Next.js," carries 895 stars and 452 forks; opencollective-api is the Node.js backend with a GraphQL API and a PostgreSQL database.

Both ship under the MIT license, the same permissive terms as the main repo's own LICENSE file (copyright 2023, Open Collective) — anyone can fork the whole stack and run their own instance rather than being locked into opencollective.com specifically.

Worth noting: the hub repo's 2,300 stars are a bit of a mirage as a popularity signal, since it's a documentation and issue tracker, not the app people actually run. The real product repos sit at under 1,000 stars each — a reminder to check what a repo actually contains before treating its star count as a proxy for how widely a tool is used.

Still shipping, as of yesterday

An open-source donation platform is only as trustworthy as whether anyone's still maintaining it, so it's worth checking the commit log directly. The opencollective-api commit history shows a commit dated October 1, 2026 — the day before this piece was checked — covering a dependency update, following one from September 30 adding payment-integration monitoring through Sentry. That's a project being actively worked on in real time, not one coasting on an old launch.

One detail in that commit log is worth flagging on its own: the October 1 commit lists its authors as a human maintainer and "claude" — a visible, public signal that at least part of this donation infrastructure's own maintenance now runs through AI-assisted commits, the same pattern StewardAI has documented in solo and small-team projects built with Claude Code elsewhere on this blog.

Where this donation app's transparency promise has limits

None of this means Open Collective is a frictionless donation app for an individual giver — it's infrastructure for groups, which is a different use case than, say, donating to a single charity through an app on your phone.

There's also no App Store or Google Play listing to point to here: Open Collective is a web platform, and Product Hunt's own listing for it wasn't reachable during this session's fact-checking. That leaves the GitHub repos themselves — code, issues, commit history — as the primary evidence this piece could verify directly.

And as noted above, the specific fee percentages a collective or its fiscal host pays aren't something the public repos spell out in plain language; they live in product and pricing decisions this piece couldn't independently confirm this session.

What this generalizes to

The useful habit here isn't specific to donations: before trusting any platform with your money or your group's money, check whether the thing it claims — "full transparency," "nonprofit," "community-run" — is backed by something you can actually inspect, the same way you'd check whether a nutrition score's formula is public code or a black box, or whether a climate data map's engine is genuinely open source rather than a marketing claim. A platform that hands every group a public ledger by default, and licenses its own code so anyone can fork it, is making a falsifiable claim rather than a branding one — and that's the bar worth holding any "transparent" donation app to, Open Collective included.