Growing an open source community without growth hacks

When Hyperswitch became my growth charter, the standard advice arrived quickly: launch on Hacker News on a Tuesday, run a star campaign, get influencers to tweet. Some of it we tried. Most of what worked was slower and less interesting to talk about, which is probably why nobody talks about it.

Here is the honest ledger.

What was theater

Star spikes. A good launch day gives you a vertical line on the star chart and a flat line everywhere that matters. Stars from people who will never clone the repo are applause, not community. Pleasant, but you can't merge applause.

Swag-driven contribution pushes. If the reward for a pull request is a t-shirt, you get pull requests worth exactly one t-shirt. Anything that pays people in trinkets for typo fixes floods maintainers and teaches newcomers that open source is a transaction.

Member counts. A chat server with ten thousand lurkers and no answered questions is a worse signal than two hundred people where every question gets a thoughtful reply within hours. Optimize the second number and the first follows.

What actually compounded

The README is the landing page. The biggest single unlock was embarrassingly unglamorous: I rebuilt the repository's front door the way you'd rebuild a homepage. What is this, why does it matter, how do I try it in the next five minutes. Daily visitors grew from 500 to 5,000, and the star count doubled, making Hyperswitch the most-starred open source payments repository on GitHub. Nothing about the code changed. The packaging did.

A rhythm people can rely on. Weekly AMAs, every week, whether five people showed up or fifty. The value wasn't any single session; it was the standing promise that someone from the team would be there, answering. Communities form around rhythms, not events.

Contributor spotlights. Every spotlight put a community member's name and work in front of the whole project. People don't contribute to repositories; they contribute to places where contribution is visibly noticed. This cost almost nothing and may have been the highest-leverage retention work we did.

Teaching the domain, not the repo. Payments knowledge is weirdly enclosed; most of how cards actually work lives inside companies. We explained it in public: how an authorization flows, why retries are dangerous, what a routing decision costs. People came for the payments education and stayed for the project.

The part nobody admits

Community work gets dismissed as unmeasurable, so let me be precise: the community generated 200 qualified leads from firms with over $100M in revenue, and community-driven inbound fed a multi-million dollar pipeline, including one deal now worth about $250K in annual recurring revenue. None of that came from a campaign. It came from people who found the project, learned something, and decided the company behind it was worth talking to.

Community growth is customer success with no contract and no invoice. The work is answering questions with patience, writing context nobody pays you for, and noticing people in public, consistently, for years. There's no hack because the kindness is the product. Everything else is a star chart.