Listen Now

Today I sit down with Webb Brown, CEO and cofounder of Kubecost. Kubecost provides real-time cost visibility and insights for teams using Kubernetes. Webb tells the story of building Kubecost, starting with the pain points that inspired the open source tool. He talks about the transition from an open source project to becoming a commercial company, and explains the decision to build a company with the same name and branding as the open source tool. Webb talks about Kubecost’s newest initiative, OpenCost, and concludes by offering some lessons and advice for anyone in the early days of an open source startup.  Highlights: Webb explains what Kubernetes cost is (1:27) How the pain points addressed by Kubecost usually manifest (3:04) What the impetus was for building the Kubecost open source tool (5:30) The transition from open source to commercial (6:54) The relationship between a cost-cutting tool and open source (10:48) Kubecost’s new initiative, OpenCost (13:40) The decision to have a company with the same name as the open source project (18:55) Pros and cons that are unique to building an open source company (22:08) Advice for anyone in the early stages of an open source startup (25:22) Links: Webb Email: webb@kubecost.com  LinkedIn: https://www.linkedin.com/in/webbbrown/ Twitter: https://twitter.com/webb_brown Company: https://www.kubecost.com/

Today I sit down with Ev Kontsevoy, the CEO and co-founder of Teleport, a software company that began as an open source project. Teleport is an identity aware multi protocol access proxy that Ev was inspired to create because of the inherent frustrations with security he experienced in his career. Ev talks about how Teleport began as an open source tool and then grew into enterprise. I ask Ev what things he has done differently from his first start-up, Gravity, and we discuss how the open source community culture has bled into the company culture at Teleport. We end by talking about the SaaS version of Teleport and the ways in which the open source version funnels business into the commercial version.  Highlights: Security frustrations that led to the founding of Teleport (1:17) Ev talks about Teleport’s vision and how it began as an open source project (6:33) Ev talks about Teleport’s first customer and a separate open source project, Gravity (12:09) How Ev’s experience with a prior start-up changed his approach to Teleport (18:24) Ev discusses the culture and community at Teleport (21:16) How Teleport chooses which features to keep open source and which ones to offer as commercial (24:38) The SaaS version of Teleport (26:55) The different audiences for the different iterations of Teleport (28:08) Links: Ev Kontsevoy LinkedIn: https://www.linkedin.com/in/kontsevoy/ Twitter: https://twitter.com/kontsevoy Company: goteleport.com

Today I’m joined by Cillian Kieran, the CEO and co-founder of Ethyca, to talk about the privacy challenges that served as the impetus to found Ethyca. In our chat, he explains the overarching goals of the privacy engineering platform. We discuss the decision to begin Ethyca as an open source tool and why that was critical to the mission. Then we talk about the decision to move to a commercial product and how to decide which features to offer as paid versus free. Cillian reviews the differences in his process between his two start-ups, discusses lessons he learned from prior mistakes, and provides advice for aspiring founders of open source start-ups.  Highlights: How Cillian decided to found Ethyca (00:50) Awareness of developers and engineers around privacy issues (3:46) Cillian talks about why he went the open source route (8:15) Moving from open source to commercial product (14:02) Privacy as a human right and how that influences development of features (16:32) How Ethyca manages relationships between engineer and legal teams (19:40) What Cillian did differently at his two start-ups (21:58) We discuss open source start-up success and whether it’s necessary to have a larger world-changing vision (24:52) Cillian discusses mistakes he has learned from (27:56) Cillian offers advice to aspiring founders in the open source community (30:49) Links: Fides open source platform: fid.es Cillian Twitter: @Cillian Company: https://ethyca.com/

Today I’m joined by CEO and founder of LeanIX, André Christ. André begins by describing his business, and then explains how his experiences working in large enterprise inspired him to build a product that would help businesses catalogue their software and optimize their portfolios. André offers advice for companies desiring to sell primarily to enterprise and expounds on the his experience with the differences between traditional enterprise and large enterprise. We discuss LeanIX’s transition to become a global company based in Europe, and conclude our talk with some advice from André to potential founders.  Highlights: André describes his his company LeanIX (00:48) The experiences that led André to found LeanIX (2:50) LeanIX’s decision to focus on enterprise customers (7:45) Advice for companies that want to focus on selling to enterprise (9:47) The difference between traditional enterprise and very large enterprise like Amazon (15:19) Transitioning to becoming a global company based in Europe (19:49) The surprisingly fragmented world of global tech (24:50) LeanIX’s decision to expand into other products (26:30) André’s advice for anyone considering starting a company (27:57) André shares about scaling mistakes and how LeanIX has learned from them (31:48) Links: André LinkedIn: https://www.linkedin.com/in/andrechrist/ Twitter: https://twitter.com/christ_andre Company: https://www.leanix.net/

Today I chat with Keith Basil, GM of Edge Computing at SUSE. We begin by reviewing the definition of edge: Keith explains how SUSE breaks edge computing down into 3 categories, and then talks about the shared understanding of edge by the industry at large. I ask Keith about the overlap of edge products with non-edge products, and then we discuss the maturity of the edge landscape and Keith explains how SUSE helps clients with infrastructure. We wrap up by talking about managing feature bloat and SUSE’s decision to have their entire code base be open sourced.  Highlights: Keith breaks down the 3 categories of “edge” as defined at SUSE (1:14) We discuss the industry understanding of edge technology (5:34) Keith defines “edge watching” (8:44) We discuss the relationship between cloud native and edge native (10:22) The overlap of edge products and non-edge products (14:25) The maturity of the edge landscape and how SUSE help clients with infrastructure (17:04) How SUSE manages feature bloat (23:37) SUSE’s decision to have their entire code base be open sourced (26:15) Links: Keith Twitter: @noslzzp Company: https://www.suse.com/

Today I talk with Shaun O’Meara, the global field CTO at Mirantis. We begin by discussing the integration of Docker Enterprises with Mirantis approximately three years ago. We discuss the challenges of integrating companies, including incorporating new technology, processes, and customers and merging two very different work cultures. Shaun offers his advice for anyone considering selling to enterprises and emphasizes the role of partnering with customers and becoming part of their process. Shaun talks about the expectations and realities of merging Docker and Mirantis, including the challenges of a licensing model change. We conclude our time by discussing the differences between selling to small companies versus selling to enterprises.  Highlights: How integrating Docker Enterprises with Mirantis affected Shaun’s role as CTO (1:09) How incorporating Docker technology helped Mirantis build different value for customers (3:39) We talk about the effects of combining the work cultures of Docker and Mirantis (5:40) Shaun offers advice for people considering start ups or selling to enterprise, including the importance of partnering with customers (8:47) Shaun talks about his expectations of merging Docker and Mirantis versus reality (12:56) We talk about the licensing model change through the transition (14:34) Shaun talks about outsourcing versus what Mirantis does in augmenting and supporting teams (17:55) We discuss the differences between selling to small companies and enterprise (20:06) Links: Shaun LinkedIn: https://www.linkedin.com/in/shaun-omeara/ Company: https://www.mirantis.com/

Today I sit down and chat with John McBride, senior software engineer at VMware. We begin by talking about John’s address at KubeCon, “Risks of Single Maintainer Dependencies and How to Mitigate Those Risks.” We discuss the definition of security and then John identifies some of the other non-security risks posed by single maintainer dependency. We talk a little bit about mitigating the risks and about building trust and community around single maintainer projects. We conclude our time by speculating on the extinction of single maintainer dependencies.  Highlights: John introduces himself and talks about his interest in mitigating the risks of single maintainer dependencies (00:55) We have a conversation about the definition of security (4:54) John talks about the other, non-security risks of single maintainer dependency (10:00) We discuss how to mitigate the risks of single maintainer dependency (12:04) John talks about building trust and building community around single maintainer projects (16:48) John answers my question “Do you think being a single maintainer is ultimately an anti-pattern, a non best practice?” (23:56) Links: John Twitter: @johncodezzz Company: https://www.vmware.com

Today I talk with Catherine Paganini, Head of Marketing and Community at Buoyant. We begin by discussing the Cloud Native Glossary and how it is helping to make cloud native concepts more accessible for people around the world. Catherine talks about nurturing community in open source projects, and about the function of documentation. Catherine and I discuss pitfalls in building open source communities, and Catherine talks about her strategy for recovering from mistakes. Catherine concludes the conversation by talking about balancing her roles as head of marketing and community at Buoyant. Highlights: Catherine talks about how the Cloud Native Glossary started, how it has grown, and how it helps to make education about the cloud accessible and easy to understand  (1:00) Catherine discusses about how the Cloud Native Glossary is being used (5:47) Catherine and I talk about nurturing community in an open source project (8:22) Catherine discusses empowering end users through efforts like the Linkerd Anchor Program (11:28) Catherine talks about the function of documentation (14:05) I ask Catherine, “What do you see people getting wrong when it comes to nurturing community?” (15:29) Catherine talks about recovering from mistakes (18:49) Catherine discusses walking the line between being head of marketing and head of community (23:47) Links: Cloud Native Glossary: https://glossary.cncf.io/ Linkerd: https://linkerd.io/ Linkerd Anchor Program: https://linkerd.io/community/anchor/ Catherine LinkedIn: Catherine Paganini Twitter: @cathpaga Company: https://www.buoyant.io

Today I talk with Yann Léger, CEO of Koyeb, the serverless developer platform that allows businesses to safely and easily deploy applications. We begin by talking about Yann’s decision to base the company on serverless, and the true meaning of cloud native. Yann then discusses Koyeb’s relationship with Kuma, and Koyeb’s posture towards open source projects. The conversation concludes with Yann sharing mistakes he’s learned from in the process of building Koyeb and offering advice to other potential technical founders.  Highlights: Yann talks about the decision to leave his position at Scaleway and start his own company (1:44) Yann discusses choosing to base his company on serverless (3:14) Emily and Yann talk about the meaning of cloud native (6:00) Yann talks about Koyeb’s relationship with Kuma (9:40) Yann discusses Koyeb’s open source projects (11:46) Yann shares mistakes he has learned from in the process of building Koyeb (15:25) Yann answers the question “What are the disadvantages of being a technical founder?” (18:06) Emily and Yann discuss the challenges of remote working (22:00) Yann’s advice for anyone considering becoming a technical founder (23:15) Links: Yann LinkedIn: Yann Léger Twitter: @yann_eu, @gokoyeb Company: https://www.koyeb.com/

Today I chatted with Dirk Hohndel, chief open source officer at the Cardano foundation. We begin by defining an open source ecosystem, and then talk about what different open source ecosystems might look like and how they are maintained. Dirk talks about best practices for steering an open source ecosystem, and then we discuss the role of foundations in open source projects. I ask “how do you define success for an open source project” and we end with a discussion on the best practices for running open source project foundations. Highlights: We talk about the meaning and maintenance of an open source ecosystem (1:31) The differences between an open source ecosystem and a community (11:06) Dirk talks about best practices for steering an open source ecosystem (13:00) The role of a foundation in an open source project (18:04) Dirk discusses other iterations of open source projects that can be successful (22:19) Dirk answers the question “how do you define success for an open source project?” (24:43) We discuss best practices for running an open source project foundation (27:49) Links: Dirk  Twitter: @_dirkh Company: cardanofoundation.org

Today I sit down with Romaric Philogène, CEO and founder of Qovery, a platform that helps developers build, deploy, run, and scale applications.  Romaric begins by talking about his first two start-ups, both social networks, and then we discuss the difference between creating consumer-facing products and products for developers. We then talk about marketing in the US as it compares to the global market. We discuss Qovary’s relationship to open source and the idea of fostering community around a company’s culture. Romaric concludes by offering advice to developers on the value of being a skilled communicator.  Full Description / Show Notes Highlights: Romaric talks about his first two startups that preceded Qovery (3:26) The differences between building a consumer facing product and creating a product for developers (5:55) Romaric talks marketing in the US vs marketing in Europe  (11:50) Romaric answers the question “what are things you’re doing differently now that you’ve learned from previous efforts?” (17:00) The value of community building in marketing to developers (19:28) Qovary’s relationship with open source (20:46) Building community around your company vs just a product (25:00) The importance of communication as an engineer (28:47) Links: Romaric Twitter:@rophilogene Company: https://www.qovery.com/

Today I’m chatting with Avery Pennarun, CEO of Tailscale. Tailscale is a VPN service that makes devices and applications accessible anywhere in the world by enabling encrypted point-to-point connections using the open source WireGuard protocol. Avery begins by talking about his experience building a start-up while he was a college student and how things have changed as he leads his current start-up. Avery recommends the book “Crossing the Chasm” and we discuss market segmentation as it relates to creating a successful start-up. Avery explains how Tailscale has been successful in implementing market segmentation strategies. We conclude our conversation by talking about goal setting and the importance of quality. Highlights: Avery talks about his first start-up experience as a college student (1:10) Avery recommends “Crossing the Chasm” and discusses how it influenced his start-ups (7:54) We discuss market segmentation strategy (13:29) Specific marketing strategies used at Tailscale (18:41) Avery talks about mistakes he’s made while building his start-ups (22:24) Goal setting in start-ups (24:42) We talk about the importance of quality in building word of mouth success (29:49) Avery answers the question “How do you maintain an identity as an engineer when you are also a serial entrepreneur?” (33:23) Links: Avery Twitter: @apenwarr @tailscale Company: https://www.tailscale.com

Today I chat with Kiersten Gaffney, CMO of Codefresh, a software delivery platform. Kiersten begins by defining her role as CMO. We then discuss the unique challenges of product strategy with open source projects. Kiersten talks about the importance of maintaining both a top-down and bottom-up approach when taking a project from open source to enterprise, and then explains some of the most common mistakes she’s seen when companies undergo this process. We discuss how technical a team should be when marketing open source and conclude the conversation by talking about analysis paralysis in start-ups and how to avoid it.  Highlights: Kiersten answers the question “What do CMOs do all day?” (1:49) Product strategy with open source products (2:58) How open source projects fit into marketing efforts (6:10) Kiersten’s advice on how to maintain both a top-down and bottom-up approach (11:28) Is there a magic formula for taking a project from open source to for profit? (13:02) Biggest mistakes when taking a project from open source to enterprise (15:54) Emily asks how technical a marketing team should be for an open source project (22:53) Kiersten and Emily discuss the tension between engineering and marketing (24:24) Analysis paralysis in startups (26:35) Links: Kiersten LinkedIn: https://www.linkedin.com/in/kierstengaffney/ Twitter: @kierstengaffney Company: https://codefresh.io/

In this short summation episode, I talked a little more about why I think Deepfence's open source strategy is so genius. 

Today I sat down with Sandeep Lahane, founder and CEO of Deepfence, a security preventive and detective solution for cloud and container native environments. Sandeep began by explaining both the open source and enterprise components of Deepfence. Threatmapper is a multi-cloud platform for scanning, mapping, and ranking vulnerabilities in running containers, images, hosts, and repositories, and Threatstryker is a commercial product that offers runtime attack analysis, threat assessment, and targeted protection for infrastructures and applications. We then talk about the inexhaustibility and the ever-changing landscape of cybersecurity. Sandeep explains the impetus for launching Deepfence and the process of getting to Threatmapper and Threatstryker, and then talks about his journey from working as a systems programmer to launching a tech startup. We discuss the tense relationship between security and development in the industry, and end the conversation with some words of advice for engineers considering the entrepreneurial plunge. Highlights: What is the difference between Threatmapper and Threatstryker at Deepfence? (00:55) Sandeep explains how the Deepfence commission product builds upon the open source one (2:14) Discussing the inexhaustibility of the cybersecurity landscape (11:40) The genesis of Deepfence (13:58) Sandeep discusses the business benefits of having an open source project (14:57) Sandeep talks about his journey from systems programmer to tech startup (17:20) Emily and Sandeep discuss the tense relationship between security and development (21:19) Sandeep gives advice to engineers considering entrepreneurship (33:57) Links: Sandeep https://deepfence.io

Some short thoughts on marketing in the open source ecosystem, drawn from my conversation with Eric on Wednesday. 

Today I sit down with Eric Hendricks, the technical marketing director at Red Hat. Red Hat delivers open source solutions that make it easier for enterprises to work across platforms and environments. Eric begins the conversation by discussing his start as a technologist and how he decided to make the move to marketing. Eric then discusses the challenges of bringing marketing savvy into the devops space, including the unintended consequences of marketing buzzwords. I ask Eric about the relationship between marketing and open source, and Eric talks about how many of Red Hat’s community marketing efforts are driven through upstream communities. We then discuss the concept of the buyer in open source versus start ups, and how the difference is that the “big ask” in open source projects is emotional investment. Eric concludes the conversation by talking about the impact of his current role as a technical marketer as compared to the impact of a founder or IC.  Highlights: Eric answers the question “At what point did you start to see yourself and did other people see you as a marketer?” (5:53) The stigma around marketing and the problem with marketing buzzwords in devops (10:22) Emily and Eric discuss the shared vocabulary problem that can arise with newer concepts in tech (14:35) Eric talks about equipping his product’s “champions” with all the resources they need to communicate need and efficacy to potential buyers (15:39) Emily asks Eric about the relationship between marketing and open source (19:50) Emily and Eric discuss the concept of “the buyer” with open source (25:14) Eric answers the question: “how are you able to have more of an impact in your current role than you would as an IC?” (29:30) Links: Personal website: www.itguyeric.com Company website: www.redhat.com Twitter: @itguyeric Company: @rhel Podcasts: RHEL Presents, Into the Terminal

I'm trying something new this week — adding an extra episode with some key takeaways from the interview earlier in the week. In this one, I talked about the education battle many cloud native companies face, the problem of open source projects that are too good and understanding pain points for different personas. 

Today I’m joined by Omri Gazitt, founder of Aserto, an authorization company that offers cloud native authorization as a service. We discuss the differences between ID authorization and authentication and the problems associated with educating developers on the distinctions. Omri also talks about the evolution of authorization from server software all the way to cloud native authorization. He then expounds on the strategic nature of the decision to open source or not, and offers advice to developers based on his experience as both an engineer and an executive.  Highlights: The beginnings of Aserto (7:50) Omri talks about what it was like to be part of a startup, Neon, in the 90s (10:49) Emily and Omri discuss what authorization was like pre-cloud native (13:32) How integration became the strategy used by Aserto to begin to solve authorization problems (17:10) The decision to open source and how organizations should be strategic when considering open source  (18:55) Omri discusses his unique perspective as both a former tech engineer and executive in forming his start-up (25:08) Omri talks about a missed opportunity in the early stages of Aserto (28:56) Links: Omri LinkedIn: Twitter Company

I’m joined by Mark Grover, one of the founders of Stemma, a data catalogue for building decentralized data informed cultures. In essence it is a “Google Search” built for data scientists, data analyst, business leaders, and more. Stemma is striving to solve data documentation and relevance issues by keeping data cataloguing up to date and current. In this episode Mark covers his transition from the data team at Lyft to establishing Stemma. He discusses how he identified the need for a source of truth for ETA data, and how the data scientist in these teams should be the end all for this knowledge. Starting with building Amundsen, Stemma expands on the groundwork laid there to bring data to the user and open-source community’s needs. Highlights: An introduction to Mark and Stemma (00:00) The history of Stemma (00:45) How open source helped solved data cataloguing problems (4:40) The decision to found Stemma (07:40) How Stemma’s relationship with Amundsen has evolved (13:20) The unexpected challenges and unexpected eases (18:35) Navigating the co-founding experience (23:35) Mark’s vision for Stemma’s future (28:54) Mark’s tips for aspiring founders (32:54) Links: Mark LinkedIn Twitter Company