Project management service Zenhub raises $10M as it goes beyond GitHub

Zenhub got its start in 2014 as a project management service for developers that was deeply integrated with GitHub. While the company has expanded its feature set over the years, users always needed a GitHub account to use it, even as its user base expanded beyond the original developer audience to include non-technical users on marketing, customer and product teams, for example. Until now, those users needed GitHub accounts, too, at an additional cost for the employers; starting today, Zenhub users won't need a GitHub license anymore. The company, which is also announcing a $10 million Series A funding round led by Vancouver, Canada's Yaletown Partners, is launching Zenhub Issues today, its new issue management experience that will allow non-technical users to create issues and track projects within the service -- all without a GitHub account.

As Zenhub co-founder Aaron Upright told me, this doesn't mean the company is moving away from GitHub -- that's still very much the core of what it does. "We're moving away from GitHub as a platform, but we're now providing an independent way on top of GitHub issues for teams to create tasks and manage and track work," he explained.

Image Credits: Zenhub

He noted that the company's users don't want GitHub access to be a limiting factor for who can collaborate with development teams. What happens today is that the development team uses Zenhub and the non-technical teams use Asana, Trello, Monday.com or similar services -- but that makes it harder for them to collaborate with the technical teams.

"The use case that we're really trying to unlock with Zenhub Issues is to give everyone a way to collaborate on Zenhub," Upright said. "Developers can still connect to GitHub and be working in GitHub. But now we have a new task type and a new issue type for non-technical people to come in and collaborate with their developers in the same interface."

Given the current financial environment, many companies are looking to reduce how much they spend on their software licenses, so this is also a good strategic move as it allows these users to consolidate their project management activities into a single service -- all while the developers can still work within the Zenhub extension in GitHub and the non-technical users don't have to interact with the GitHub issues.