Kafka escaped LinkedIn: how its creators built Confluent around data in motion
Jay Kreps, Neha Narkhede and Jun Rao founded Confluent in 2014 after creating the Apache Kafka streaming platform while working at LinkedIn.
Kafka had been designed to move large volumes of events between systems in real time, replacing brittle point-to-point data pipelines with durable streams.
Confluent’s present-day business makes more sense when viewed through those early choices. The company repeatedly reused existing expertise rather than reinventing itself from nothing.
LinkedIn open-sourced Kafka before its creators left
Kafka was released as open-source software and became an Apache project, allowing organisations far beyond LinkedIn to adopt the technology.
This was an important turning point because it expanded what Confluent could offer or the markets it could address. The effect becomes clearer when viewed as part of the longer sequence of changes that followed.
Confluent turned the open-source project into a commercial platform
The founders built enterprise management, connectors, governance and support around Kafka rather than keeping the technology as an internal infrastructure tool.
This was an important turning point because it expanded what Confluent could offer or the markets it could address. The effect becomes clearer when viewed as part of the longer sequence of changes that followed.
Confluent Cloud shifted streaming into a managed service
The company increasingly delivered Kafka-compatible infrastructure as a cloud service, removing much of the operational burden of running clusters.
This shift also changed how customers consumed the technology. Instead of treating software or infrastructure as a one-off purchase, the relationship became more continuous, with updates, capacity and services delivered over time.
The 2021 Nasdaq IPO made real-time data infrastructure a public company
Confluent began trading on Nasdaq under the symbol CFLT in June 2021.
For Confluent, access to public markets was more than a branding milestone. It increased financial transparency and created another route to fund expansion, acquisitions or long-term product development.
Flink expanded the platform from moving events to processing them
Confluent invested in Apache Flink and stream processing so customers could analyse and transform data while it is still in motion.
This was an important turning point because it expanded what Confluent could offer or the markets it could address. The effect becomes clearer when viewed as part of the longer sequence of changes that followed.
Why the database stopped being the only place data waits
As of 18 September 2026, confluent now offers a cloud-native data-streaming platform built around Kafka, Flink and a large connector ecosystem.
Seen chronologically, the company is less a collection of unrelated products than a chain of decisions in which one capability created the conditions for the next.
For TechnologyBlog.co.za, this page is intended to serve as the company-history cornerstone for future Confluent coverage, so product and company-news articles can link back to one factual brand background instead of repeating the full origin story.
Primary sources reviewed include Confluent’s founder announcement and corporate materials.
