StreamNative is the commercial company behind Apache Pulsar. Founded in 2019 by Pulsar's original creators, it plays the same role for Pulsar that Confluent plays for Kafka: it employs the core committers, sells a managed cloud service, ships an enterprise distribution, and acts as the de facto commercial steward of the underlying open-source project.

This page is about the company. For the open-source project itself, see Apache Pulsar.

The plain-English summary: StreamNative is what happens when the Confluent playbook is run on a streaming platform that did not win the streaming category. That is not a knock on the engineering — the people running StreamNative are some of the deepest distributed systems engineers in the field — but it is the commercial reality the company has to navigate.

The Founding Story

In 2019, Matteo Merli and Sijie Guo — two of the original creators of Pulsar at Yahoo — left Verizon Media (the post-acquisition home of Yahoo's tech) to found StreamNative. They were joined by several other ex-Yahoo Pulsar committers, immediately giving the company a concentration of Pulsar expertise that no other vendor could match.

The pitch was straightforward and modeled directly on Confluent's: Pulsar was technically excellent, adoption was growing in pockets, and large enterprises needed someone to operate, support, and extend it commercially. StreamNative raised a Series A in 2021 of around $23 million, led by Prosperity7 Ventures (Saudi Aramco's growth fund), with participation from earlier investors. Subsequent funding has been more modest than Confluent's trajectory.

Matteo Merli has remained one of the most prolific Apache Pulsar PMC members; Sijie Guo has been the public face of the company. The two-founder structure — one CEO, one CTO/architect — is the standard pattern for OSS-commercial companies of this generation.

The Product Lineup

StreamNative sells essentially the same shape of product Confluent does, scaled to its smaller market.

StreamNative Cloud. Fully managed Pulsar as a service, available on AWS, GCP, and Azure. Customers get Pulsar brokers, BookKeeper, ZooKeeper (or its replacement), monitoring, and the operational layer abstracted away. This is the strategic priority.

StreamNative Platform. The on-prem distribution with enterprise features (authentication, authorization, multi-tenancy management, monitoring, the StreamNative console UI). Targets banks, telcos, and enterprises that cannot or will not run on public cloud.

StreamNative for Kubernetes. A Kubernetes-native packaging of Pulsar with operators, designed for teams that want to run Pulsar themselves but with a managed control plane experience.

Connectors and ecosystem. StreamNative invests in Pulsar IO connectors, the Function Mesh project (Kubernetes-native Pulsar Functions orchestration), and protocol compatibility layers like KoP (Kafka-on-Pulsar) and AoP (AMQP-on-Pulsar). These are explicit moats: by making Pulsar look like Kafka or RabbitMQ to existing clients, StreamNative reduces the migration cost from competing systems.

The Comparison to Confluent

The two companies are strikingly parallel. Both were founded by the original creators of an open-source streaming platform. Both sell a managed cloud service plus an enterprise distribution. Both invest heavily in protocol-compatible layers and adjacent tooling. Both ship Schema Registry equivalents and Connect-style ecosystems. Both have to monetize software anyone can download for free.

The key differences:

	Confluent	StreamNative
—-	—-	—-
Underlying project	Apache Kafka	Apache Pulsar
Founded	2014	2019
IPO	2021	Private
Category mindshare	Dominant	Niche
Ecosystem network effects	Massive	Modest
Enterprise install base	Global Fortune 500	Selected large adopters (Tencent, ByteDance, Yahoo, etc.)

The structural challenge for StreamNative is that it is playing the same game as Confluent in a category Confluent already won. Even on technical merit — and Pulsar's architecture is, in many specific ways, more elegant than Kafka's — the gravity of the Kafka ecosystem means most new streaming projects default to Kafka. StreamNative's path to growth requires either converting Kafka shops to Pulsar (rare and expensive) or capturing the Pulsar shops that already exist (a smaller pond).

DataStax: The Other Pulsar Commercial Story

StreamNative is not the only commercial vendor of Pulsar. DataStax — the long-standing commercial company behind Apache Cassandra — adopted Pulsar in 2020-2021 as the underlying technology for its Astra Streaming product, which it sells alongside Astra DB (managed Cassandra). DataStax acquired the Pulsar-focused company Kesque in 2021 to accelerate that work.

The rationale: DataStax already had a large enterprise install base for Cassandra, and adding a managed streaming product to that bundle let them compete for "operational data + real-time pipeline" workloads without building a streaming engine from scratch. Pulsar's architecture (separating compute from storage, with first-class geo-replication) fit the Cassandra customer profile well.

The result is that Pulsar has two meaningful commercial vendors — StreamNative and DataStax — which is unusual for an open-source infrastructure project but also reflects the fact that neither has reached Confluent's scale. Two medium vendors split a smaller pie.

The Honest Vendor Take

Second place in streaming is a tough place to be. The honest version of the StreamNative story:

The technology is real. Pulsar is genuinely a well-engineered distributed system, with real architectural advantages over Kafka for certain classes of workload (multi-tenant, geo-replicated, very large scale). StreamNative's engineering team is deep, the contributions to Apache Pulsar are real, and customers who pick StreamNative get a product that works.

The commercial story is hard. The default streaming choice in 2026 is Kafka. Convincing a new customer to pick Pulsar — against the gravity of the Kafka ecosystem, the larger pool of available engineers who know Kafka, and the broader connector library — requires a specific reason, and most customers do not have one. The customers StreamNative wins tend to have explicit multi-tenant or geo-replication needs, or are already running Pulsar from a previous decision.

The exit options are constrained. Confluent went public on the back of a category-dominant position. StreamNative does not have that runway. The realistic outcomes are: continued growth as a niche specialist, an acquisition by a larger infrastructure vendor, or eventual consolidation with DataStax or another Pulsar-adjacent company. None of those are bad outcomes — they are just not the Confluent outcome.

The engineering credibility is the biggest asset. When Tencent or ByteDance need to run Pulsar at extreme scale, the people they call are at StreamNative. That depth of expertise is genuinely defensible and is the company's strongest moat.

For customers, the practical advice is: if you have already decided to run Pulsar, StreamNative is the canonical commercial choice — it is the most actively developed, has the deepest committer involvement, and offers the most full-featured managed product. If you are choosing between Kafka and Pulsar, the streaming-platform decision dominates the vendor decision, and you should make that call before evaluating StreamNative versus Confluent versus anyone else.