Vancouver startup Codezero has raised a $3.5 million seed funding round led by Ballistic Ventures, a venture capital firm dedicated exclusively to funding entrepreneurs and innovations in cybersecurity.
This investment marks a significant leap forward in Codezero’s mission to reimagine multi-cloud, collaborative microservices development.
With the new capital, Codezero is set to grow its sales and marketing teams and expand its partner network.
“Multi-cloud, microservices-based architectures have become essential for digital business transformation. However, developing microservices across disparate cloud environments can force tradeoffs between developer productivity and security. Codezero eliminates these tradeoffs,” said Reed Clayton, Co-founder and CEO of Codezero.
“Our mission is to empower DevOps teams with collaborative, multi-cloud infrastructure that prioritizes both security and developer productivity. As a cybersecurity-focused VC firm, Ballistic shares in this mission, and we’re thrilled to be a part of their portfolio.”
The “developer security problem” refers to a complex set of risks and vulnerabilities arising from the multiple levels of access and control that developers require over various staging and production systems. This situation is fraught with unintended risks, given that developers often require elevated permissions to create, manage, and deploy software and infrastructure.
Codezero Teamspaces is an identity-aware overlay network. This means developers can instantly create environments consisting of services spanning local, cloud, and even their colleagues’ computers. They can do this without needing to know anything about the underlying infrastructure, networking, or direct access to credentials.
Ballistic Ventures’ investment adds to the support from its existing, impressive list of angel investors and advisors, including Thomas Dohmke (GitHub CEO), Nick Caldwell (Microsoft, HubSpot, and Peloton), Marty Weiner (Pinterest and Reddit), and James Routh (AMEX, CVS, KPMG, and JPMorgan Chase).
Leave a Reply