Partnerships & loops

Open-source a useful piece

Release a free component. The paid product sits next to it.

Visit github.com
Cost
Free

Free to use. No paid tier is needed to list or post.

Verdict
slow burn

Slow burn: a free component draws users who may upgrade.

Difficulty
Hard

Gatekept or reviewed, or needs an existing audience or reviews first.

Effort
High

About 10 or more hours a month, mostly during launches or a regular posting habit.

First result
1 to 3 months

A rough range for one person working on it part-time.

Payoff
Compounds

keeps growing while you keep at it.

Best for

Developer products with a useful free core.

Not for

Products where the core cannot be shared.

Pros

  • Draws developers who may upgrade
  • Builds trust

Cons

  • Large time commitment
  • Free users may never pay

The full guide

Last verified 2026-10-30

Links checked 2026-10-31 · All links answer

Fee and rule changes

No price or fee changes recorded since we started checking on 2026-10-31. Changes appear here when a price or fee on this channel's pages changes.

How we know

Checked 2026-10-31 by reading each link's page and comparing the prices and fee percentages on it. We do not read logged-in pages, and we cannot check a page that blocks automated reads.

01What it is and who is there

Open-sourcing a useful piece means releasing part of your product, such as a library, component or self-hosted version, as free and open-source software. Developers find it on GitHub, package registries and communities, and some become users of your paid product. It builds trust and reputation, but it takes real maintenance.

02Cost and what you actually pay for

Hosting on GitHub is free. The cost is maintenance: issues, pull requests, releases and docs.

03Is it right for you?

It fits developer tools, AI products and infrastructure where a free core is useful by itself. It fits poorly when the core cannot be shared or when you cannot maintain it.

04Before you start

  • Decide which piece to release and which stays paid.
  • Choose a license that fits your goals.
  • A README, contributing guide and code of conduct.

05Step-by-step: how to distribute here

  1. Release the piece with a clear README and license.
  2. Publish it to the right package registry.
  3. Launch it on Hacker News and relevant communities.
  4. Link the paid product from the README where it fits.
  5. Answer issues and merge good pull requests.
  6. Ship regular releases.

06What to post or submit

README section:

## Need more?
[Project] is free and open source. [Paid product] adds [features] for teams that need [benefit]: [link].

07Common mistakes and do-nots

  • Do not release code you cannot maintain.
  • Do not change the license in ways that surprise users without clear notice.
  • Do not make the open-source version deliberately broken.

08How to measure it

  • Track stars, downloads and contributors.
  • Track sign-ups from the README.
  • A realistic test: three months.

09Time budget

  • Before: 5 to 20 hours.
  • Ongoing: 3 to 8 hours a month.

10Pair it with

11Sources

Sources