Apache Kafka

Distributed event streaming platform for durable publication, storage and consumption of event streams.

3 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Run the official Java distribution or Apache Kafka container image; configure the documented broker/controller topology for production.

  2. Operated by

    Your team

    Customer manages broker capacity, replication, retention, authentication, authorization, monitoring and upgrades.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodRun the official Java distribution or Apache Kafka container image; configure the documented broker/controller topology for production.
InfrastructureServers / containers
Customer-operated Kafka brokers/controllers with persistent replicated topic partitions. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.
Licensing modelOpen Source / Open Core
Apache License 2.0 for upstream Apache Kafka. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.
LicenseApache License 2.0 for upstream Apache Kafka.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

Kafka 4.4 documents production SASL/OAUTHBEARER authentication with an identity provider for broker/client access, while the default unsecured token implementation is development-only. That establishes protocol authentication, not a browser administration-console SSO path; select and verify the actual user-facing interface separately.

Apache Kafka 4.4 core broker/client identity; web-console user SSO remains unconfirmed · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The upstream quickstart identifies the official apache/kafka:4.4.0 JVM image and apache/kafka-native:4.4.0 native image. Its single-container example is a basic environment, not a replicated production cluster or managed Kafka service.

Apache Kafka upstream 4.4.0 quickstart · Source ↗ · Deployment artifact ↗ (4.4.0 JVM image; production topology requires separate planning) · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The Kafka 4.4 operations guide publishes a reference machine with dual quad-core Xeons and 24 GB RAM, and estimates buffering memory from write throughput multiplied by 30 seconds. This is a hardware/reference formula, not a modern cloud minimum or an HA design; separately size brokers, KRaft controllers, replication, retention, disks and recovery capacity.

Published Kafka 4.4 hardware example and buffering heuristic; not a validated 100-user/1-TB HA footprint · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The upstream 4.4.0 core is Apache-2.0 licensed. This does not confer a managed Kafka subscription, commercial support entitlement or rights to separately licensed vendor add-ons; infrastructure and operations costs are separate.

Apache Kafka upstream software, not a managed-service or commercial distribution quote · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

The single-node quickstart is an evaluation starting point. Commercial Kafka distributions, hosted services and independently licensed connectors are outside this upstream listing.

Community & maintenance

Established Apache project with an actively updated distribution/quickstart and a project-maintained Powered By directory of named organizations.

Category fit

Streaming
Distributed event log with topics, producers, consumers and stream processing integrations; applications and connectors determine downstream processing.

Compare within Streaming

  • Aiven for Apache Kafka BYOCManaged Apache Kafka brokers in the customer's cloud account, operated by Aiven.
    • AWS
    • Azure
    • Google Cloud
    Vendor-operated BYOC · Commercial Only
  • Apache PulsarDistributed publish-subscribe messaging and streaming platform for persistent event workloads.
    • AWS
    Customer-operated · Open Source / Open Core
  • Cloudera on CloudCloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.
    • AWS
    • Azure
    • Google Cloud
    Shared operations · vendor control plane · Commercial Only
  • Confluent Platform Self-ManagedSelf-managed event streaming platform deployed to customer-operated Kubernetes with Confluent for Kubernetes.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Redpanda BYOCManaged Kafka-compatible streaming in your cloud account.
    • AWS
    • Azure
    • Google Cloud
    Vendor-operated BYOC · Commercial Only

These products address related workflows; read their category-fit notes before comparing scope. See all of Streaming →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Apache Kafka deployment on GKE using Strimzi ↗ · Google Cloud

      Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      Google documents creating customer GKE infrastructure and deploying Apache Kafka through the Strimzi operator. This is upstream Kafka operated in the customer project, not Confluent Cloud. The published tutorial includes version-specific ZooKeeper/KRaft assumptions; verify current Kafka and Strimzi compatibility and production security.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory