- 01
Direct impact
No fund in between. You choose the dream, see the milestones and watch the proof arrive. A small backing can complete a milestone when several Backers join in.
- 02
Transparent by design
Every dream shows its goal, milestones and progress. Dreams are reviewed before they go live, and money moves only when proof is posted.
- 03
A relationship, not a transaction
Chat with the Dreamer and follow updates. Many Backers return because they enjoy watching a plan become something real, knowing they helped.
How Backers are protected
14-day review per milestone
When proof is posted, each Backer has 14 days to release their share or ask for more. Money not released in time goes back to the Backer.
15% fee, deducted — never added
Backers pay exactly what they choose. The 15% fee comes out of each backing: CN¥1,000 gives the Dreamer CN¥850. The fee is kept if money is returned.
Gifts, not shares
Backings are gifts. No shares, equity, interest or repayment, and Dreamers keep full ownership. Nothing on cohero is an investment or a loan.
Example milestone plan
An example plan for a open-source tool dream with a goal of CN¥53,000. Backers fund the whole goal, but each milestone's money stays held until you post the proof and Backers release it.
Milestone 1
CN¥13,250 · 25%
Publish the technical scope
Post a repository link, a design note and a minimal runnable example explaining the problem and the planned interfaces.
Milestone 2
CN¥18,550 · 35%
Implement the core tool
Share tagged source changes, automated test output and a recorded example showing the main function with sample inputs.
Milestone 3
CN¥13,250 · 25%
Check compatibility and docs
Upload a compatibility matrix, fresh installation results and draft documentation tested against the current version.
Milestone 4
CN¥7,950 · 15%
Prepare contributor release
Post release notes, contribution instructions and an issue triage plan with links to the final examples and known limitations.
Risks to plan for
- R1
Dependencies break compatibility
An upstream change can make installation fail even when the tool code is unchanged. Define supported versions early and budget for automated compatibility checks and fixes.
- R2
Maintainer workload expands
Support requests can displace planned development work. Limit the funded feature scope and reserve the final milestone for contribution guidance and a manageable issue triage plan.
- R3
Examples hide setup problems
A tool may run only in its creator’s environment. Include fresh installation tests on the supported setups and fund documentation fixes before presenting the release as complete.
Questions and answers
Why fund an open-source tool if anyone can use the code?
The dream can fund the engineering, testing and documentation needed to make public code useful. Explain the specific work being supported and provide repository evidence rather than implying Backers buy exclusive access.
What counts as proof when the work is mostly maintenance?
Link to resolved issues, source changes and test results that show the supported versions still work. Include a reproducible example or installation check so Backers can assess maintenance beyond a list of commits.
Do Backers get anything in return?
Backings are gifts, so there are no shares, interest or repayment. You get a clear view of the progress you made possible and a direct line to the Dreamer.
Budget example
A typical cost split for a open-source tool dream in Nanjing, shown in CNY. Backers are charged the equivalent in US dollars.
Example goal
CN¥53,000
- Core engineering and maintenanceCN¥37,100 · 70%
- Test infrastructure and hostingCN¥5,300 · 10%
- Documentation and worked examplesCN¥5,300 · 10%
- Release and community supportCN¥5,300 · 10%
What you receive
- Backers give
- CN¥53,000
- Platform fee (15%)
- −CN¥7,950
- You receive
- CN¥45,050
Ready when you are
Sign in or create an account to publish a dream or back the ones you believe in.
Sign in / Create account