Fund a open-source tool dream in Delhi without equity

Many people think the only way to raise money is to sell part of what they build or to borrow. On cohero, backings are gifts. You keep full ownership of your open-source tool dream and everything it becomes.

An open-source tool needs more than public code: installation, tests and contributor guidance make it usable. Fund a defined technical scope with visible changes and reproducible examples.

  1. 01

    Gifts, not investments

    A backing is a voluntary gift towards a goal. Nothing is sold, no ownership changes hands and no return is promised. Backers support a person; you keep control.

  2. 02

    Why milestones still matter

    Without contracts, Backers rely on transparency. You post proof for each milestone so they can review your progress and choose to support your dream directly with confidence.

  3. 03

    What you owe Backers

    Honesty: a true story, proof for each milestone and updates in chat. Not profits or repayment. Because Backers can pay milestone by milestone, they only send further support as you prove progress.

How Backers are protected

14-day review per milestone

When proof is posted, each Backer has 14 days to review the proof, ask for more info, and decide whether to keep supporting your next milestone.

0% commission — direct gifts, nothing taken

Backers pay exactly what they choose directly through your payment methods. cohero takes 0% commission on backings, so you keep what is sent. Any refunds or disputes are handled directly between you, the Backer and your payment provider.

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 ₹760,000. Backers pay you directly, funding the goal all at once or milestone by milestone as you post proof for each step.

  1. Milestone 1

    ₹190,000 · 25%

    Publish the technical scope

    Post a repository link, a design note and a minimal runnable example explaining the problem and the planned interfaces.

  2. Milestone 2

    ₹266,000 · 35%

    Implement the core tool

    Share tagged source changes, automated test output and a recorded example showing the main function with sample inputs.

  3. Milestone 3

    ₹190,000 · 25%

    Check compatibility and docs

    Upload a compatibility matrix, fresh installation results and draft documentation tested against the current version.

  4. Milestone 4

    ₹114,000 · 15%

    Prepare contributor release

    Post release notes, contribution instructions and an issue triage plan with links to the final examples and known limitations.

Budget example

A typical cost split for a open-source tool dream in Delhi, shown in INR. Backers pay you directly using your accepted payment methods.

Example goal

₹760,000

  • Core engineering and maintenance₹532,000 · 70%
  • Test infrastructure and hosting₹76,000 · 10%
  • Documentation and worked examples₹76,000 · 10%
  • Release and community support₹76,000 · 10%

What you receive

Backers give
₹760,000
0% platform commission
−₹114,000
You receive
₹646,000

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

Do I have to pay Backers back?

No. Backers send gifts directly to your own payment account. cohero never holds funds or reverses payments; any dispute or refund request is handled between you and the Backer through your payment provider.

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.

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

More open-source tool guides

Open-source tool dreams in other cities

Other tech dreams