How Documenso got 4,000 stars and grew an active GitHub community
Oct 11, 2023
Contents
Each month, we speak to a team enrolled in PostHog for Startups about the way they work. This time, we spoke to Documenso about how they’ve grown their GitHub community.
Documenso, the open-source alternative to Docusign, launched in November 2022 and has grown rapidly. The project has over 4,000 GitHub stars at the time of writing and the team track their Star progress closely, viewing it as a vital community metric.
“We track Star, Forks and Contributors on a weekly basis,” says Florent Merian from Documenso. “Stars are mainly useful to us as a social proof. They show that users trust us, and encourage others to do the same — but they also inspire us in the work we do.”
Over the past year Documenso has put a lot of effort into growing its presence on GitHub, and learned several lessons about what does (and doesn’t) work...

1. Start small, stay transparent
Every journey starts with a single step, and for Documenso that was encouraging the team and their friends to star the repo. This alone helped them reach their first 50 GitHub stars.
“Those first 50 stars were mostly from friends and team members,” says Florent. “After that, we turned to the open-source community.”
The open-source community was an obvious place for the team to focus initially, but what really provoked interest and engagement wasn’t the open-source software — it was the open-source culture.
“We try to be as transparent as possible and share everything publicly, even revenue details,” says Florent. “This helped us engage with users on Twitter and, whenever we saw threads about open-source software or the like we were able to get involved and link back to GitHub.”
Putting it into practice: Ask friends and family to star your repo, then widen the request to relevant communities you can reach out to. Closed source teams can find communities unique to their industry, and provoke conversations there.
2. Centralize the community
A hard-learned lesson for Documenso was that the team started off trying to build a following in Slack, which they came to realize wasn’t the best platform for their users. Eventually, they decided to migrate to Discord as a community hub.
“Switching to Discord was a key moment for us,” says Florent. “We like Slack, but wanted to double down on our community building and make the whole project community driven — which meant we needed to move to a more developer-friendly environment.”
As the community settled in, the team created topics for conversation and tried to encourage GitHub contributions and bug reports. This focus on GitHub was essential because, while Discord was a great place to engage users, GitHub was the real heart of the project.