Confluent Success: Lessons for Open Source Startups

From Open Source Project to Successful Startup

Launching a startup founded on an open source project is increasingly prevalent, particularly when a founder possesses significant involvement in its initial development. A key advantage of this strategy lies in the pre-existing potential customer base that emerges as the project gains popularity, effectively establishing the top of the sales funnel prior to commercialization.

Early Monetization Strategies

Historically, companies adopting this model often provided support services resembling a help desk, catering to organizations that recognized the value of the open source software but desired a clear point of accountability. Another common approach involved developing an on-premise version enriched with enterprise-level features.

These features typically focused on scalability and security – essential requirements for larger organizations before adopting a new product. Currently, customers generally have the flexibility to deploy solutions either on-premise or within their preferred cloud environment.

The Rise of SaaS

More recently, the prevailing trend has shifted towards building a SaaS (Software as a Service) product. This involves the startup developing a comprehensive solution that manages all backend operations.

This approach allows most companies to adopt the technology without the complexities of self-installation or the challenges of directly utilizing the raw open source code.

Confluent: A Case Study

Confluent provides an illustrative example of a company that has explored various monetization strategies. Built upon the open source Apache Kafka project, Confluent specializes in streaming data solutions.

The company’s founding team initially developed Kafka within LinkedIn to facilitate the real-time movement of substantial user data volumes. Kafka was open sourced in 2011, and CEO and co-founder Jay Kreps subsequently launched Confluent in 2014.

Impressive Growth and Valuation

It is noteworthy that Confluent secured $450 million in funding while operating as a private entity, achieving a final private valuation of $4.5 billion in April. Following its initial public offering in June, the company’s market capitalization has surpassed $22 billion.

This represents significant growth within a relatively short timeframe as a publicly traded company.

Insights from Jay Kreps

During TC Sessions: SaaS last month, I had the opportunity to interview Kreps regarding the development of his open source business and the steps undertaken to monetize his innovations. His insights offer valuable guidance for open source-based startups currently in the launch phase.

Here are some key takeaways:

• Focus on solving a real problem with your open source project.
• Understand your target audience and their needs.
• Develop a clear monetization strategy that aligns with your value proposition.

Expanding into Higher Markets

Kreps noted that upon the company's inception in 2014, numerous large enterprises were already utilizing the open-source product. A key challenge became translating the existing interest in Kafka into a revenue stream for the newly formed startup.

“Different companies within this sector have pursued varying strategies, and the optimal approach is heavily influenced by the nature of the product itself,” Kreps stated. “For Confluent, a crucial early realization was the necessity to operate wherever customer data resided.”

To facilitate access to this data, frequently located within intricate, established systems, the ability to deploy the software in customer-preferred environments was paramount. In 2014, this predominantly meant on-premise installations.

“The greater the degree of legacy systems, data fragmentation, environmental diversity, and business unit complexity, the more vital a robust connectivity layer becomes. Achieving this without dedicated infrastructure proves significantly more difficult,” Kreps elaborated. “Our conversations with these organizations revealed a substantial opportunity we hadn’t initially anticipated.”

Furthermore, they observed that many potential clients were not primarily technology firms and lacked the extensive engineering resources needed to manage the complexities of downloading and maintaining the open-source version, as earlier adopters had.

Consequently, a more comprehensive, packaged solution was required. “We initiated a software offering delivered via subscription, serving companies – and continuing to serve them today – within on-premise infrastructures,” he explained.

The Transition to SaaS

Kreps observed that as the company matured, a significant number of organizations were unable to manage the complexities of on-premise installations. This realization prompted the development of a SaaS version of Confluent.

He explained that certain customers require a more comprehensive, readily deployable solution, akin to a cloud service. This ease of use is crucial, enabling them to quickly implement the technology without the need for extensive in-house engineering expertise.

The move to a cloud-based model necessitated both financial investment and engineers proficient in cloud solution architecture. However, Confluent, being a relatively young startup, faced resource constraints. This contrasts with Microsoft’s experience during its own cloud transition, as Jared Spataro highlighted.

Spataro noted Microsoft’s capacity to simultaneously develop and maintain multiple substantial business lines, including Windows, Office, and its server products, without significant disruption.

Confluent’s situation differed considerably. As an early-stage company with limited resources, Kreps consistently received advice to prioritize the existing on-premise business. He recounted being repeatedly told to maintain focus and avoid pursuing a secondary product.

Despite this conventional wisdom, Kreps believed that pursuing a SaaS offering was essential. He recognized the challenge of allocating scarce engineering resources between supporting the current customer base and building a new cloud platform.

“Balancing the demands of our established software offering, with its large and demanding clientele, alongside the creation of a cloud solution across multiple cloud providers, presented a considerable undertaking,” Kreps stated. “Sustaining growth in the existing business while simultaneously innovating proved to be a significant hurdle.”

A Strategic Shift Yields Positive Results

Recent analysis from Battery Ventures indicates a successful strategic decision. Cloud infrastructure providers, including Confluent, demonstrated significantly faster growth in their Software-as-a-Service (SaaS) offerings compared to their on-premise businesses.

Specifically, Confluent experienced 46% growth in its on-premise sector, contrasted with a substantial 180% growth rate for its SaaS division.

Among the five companies examined, only GitLab’s cloud business exhibited a more rapid expansion. It is reasonable to suggest that a different course of action could have presented considerable challenges.

The Impact of a Free Tier

A pivotal factor in this SaaS growth was the introduction of a free tier in 2019. This initiative, mirroring the earlier open-source model, provided a novel avenue for attracting user interest in the product.

It’s essential for technology-developer data products to achieve a balance between grassroots adoption and top-tier SaaS sales. Success hinges on effectively integrating both approaches.

The free tier also necessitated the provision of support for these entry-level users, with the expectation of converting a portion of them into paying customers over time.

Implementing the free tier presented a unique challenge, as it required a shift in focus. The company had to prioritize user acquisition over immediate revenue generation.

This move was somewhat unconventional, as Confluent was effectively reversing the typical progression of starting with self-service, then adding sales support, and finally targeting enterprise clients.

Lessons for Open-Source Startups

Confluent’s journey from open-source origins to a thriving commercial entity has proven successful. This outcome offers encouragement to startups pursuing a similar path, demonstrating that defying conventional wisdom can lead to prosperity.

However, as Kreps emphasizes, each company’s circumstances are unique. Determining the optimal strategy requires careful consideration of individual factors.

• Key Takeaway: Balancing bottom-up adoption with top-down SaaS is crucial.
• Strategic Insight: A free tier can be a powerful tool for user acquisition.
• Important Note: Each company must tailor its strategy to its specific context.

Ultimately, Confluent’s story highlights the potential rewards of a well-executed strategy, even when it deviates from established norms.