
# Confluent Platform Self-Managed

Self-managed event streaming platform deployed to customer-operated Kubernetes with Confluent for Kubernetes.

Canonical page: https://launchinyourcloud.com/directory/confluent-platform-self-managed/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Confluent Platform Self-Managed

Self-managed event streaming platform deployed to customer-operated Kubernetes with Confluent for Kubernetes.

- Listing: https://launchinyourcloud.com/directory/confluent-platform-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: A commercial Confluent subscription is required for Confluent Platform components deployed with CFK; component licenses otherwise vary.
- Licensing model: commercial-only
- Installation: Install the Confluent for Kubernetes operator with Helm, then deploy Confluent Platform components through Kubernetes custom resources.
- Architecture: CFK operator managing persistent Kafka, KRaft, Schema Registry, Connect, ksqlDB and other selected Confluent Platform services in a customer Kubernetes cluster
- Operations: Customer manages Kubernetes clusters, node pools, persistent storage, load balancers, DNS and routing, identity and RBAC, secrets, backups, scaling and upgrades; CFK reconciles the declared Confluent application resources.
- Product website: https://www.confluent.io/product/confluent-platform/
- Source review: 2026-11-19; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers self-managed Confluent Platform deployed with Confluent for Kubernetes, not Confluent Cloud. Current CFK guidance explicitly addresses Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. Provider examples do not certify every Kubernetes, Confluent Platform or topology combination; use the current supported-environments matrix and validate cross-cluster networking, storage, security, version compatibility and subscription terms. Confluent's November 2026 security releases address multiple broker, Kafka Connect, ZooKeeper, TLS trust, JWT, file-read, and denial-of-service issues. Upgrade to the latest patched release for the deployed branch: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3, or 8.4.1. Until patched, deployments using a separate Kafka Connect administrative listener should remove admin.listeners; the ZooKeeper fix applies to the affected 7.x lines identified by Confluent. CONFSA-2026-37 covers CVE-2026-114938 in Confluent Platform 7.6.x–8.4.x and Control Center 2.0.x–2.7.x when package/archive installs use affected customer JDKs, plus specified Docker-image ranges. Fixed-runtime releases were still being prepared at review time. Apply -XX:-UseBASE64Intrinsics to every affected Java process, restart and verify the flag until the applicable fixed image or runtime is available.

This entry specifically covers deployment through Confluent for Kubernetes. Confluent states that deploying with CFK requires a subscription and applies licensing requirements to every Confluent Platform component in that cluster. Some components can use Apache 2.0 or Confluent Community licenses outside this CFK path, but that does not make the selected CFK deployment an open-source offering.

CFK deploys long-running stateful brokers, controllers and supporting services on customer Kubernetes worker nodes with persistent storage. Using a managed Kubernetes control plane does not make the Confluent Platform application runtime serverless.


### Category fit

- streaming: Runs Apache Kafka brokers together with schema, connector and stream-processing services for customer-operated event streaming.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.confluent.io/operator/current/co-multi-region.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.confluent.io/operator/current/co-multi-region.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.confluent.io/operator/current/co-multi-region.html (checked 2026-11-16). 


### Cloud deployment evidence

- Confluent for Kubernetes guidance for EKS, AKS and GKE (aws, azure, gcp): https://docs.confluent.io/operator/current/co-multi-region.html
  The current CFK multi-region guide explicitly identifies Google Kubernetes Engine, Amazon Elastic Kubernetes Service and Azure Kubernetes Service for provider-specific configuration and validation. The CFK overview defines the product as managing self-managed Confluent Platform in the customer's own Kubernetes environment. This evidence does not include the separately operated Confluent Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Confluent for Kubernetes overview: https://docs.confluent.io/operator/current/overview.html

- Deploy Confluent for Kubernetes: https://docs.confluent.io/operator/current/co-deploy-operator.html

- Supported environments and versions: https://docs.confluent.io/operator/current/co-supported-environments.html

- CFK multi-region deployment guidance: https://docs.confluent.io/operator/current/co-multi-region.html

- Confluent Platform licensing: https://docs.confluent.io/platform/current/installation/license.html

- Confluent November 2026 security advisories and patched releases: https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes

- Confluent compromised CA trust advisory: https://support.confluent.io/hc/en-us/articles/55611336006292-CONFSA-2026-33-CVE-2026-114820-CVE-2026-114406-Confluent-Platform-Compromised-eMudhra-Certificate-Authority-Roots-and-intermediates

- Confluent Kafka Connect administrative-listener advisory: https://support.confluent.io/hc/en-us/articles/55610452168340-CONFSA-2026-27-CVE-2026-115644-Confluent-Platform-Missing-Access-Control-Unauthenticated-Access-to-Kafka-Connect-Logging-API

- CONFSA-2026-37 Java4Shell advisory: https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell

### Licensing sources

- https://docs.confluent.io/platform/current/installation/license.html

### Infrastructure sources

- https://docs.confluent.io/operator/current/overview.html

- https://docs.confluent.io/operator/current/co-supported-environments.html

- https://docs.confluent.io/operator/current/co-deploy-operator.html


### Buyer diligence


Research coverage: 8/12 fields (67%); 6 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Control Center supports OIDC SSO and automated configuration through CFK. The guide says IdP refresh-token rotation must be disabled for this integration. This is self-managed Control Center authentication, distinct from Confluent Cloud SAML. Scope: Confluent Platform Control Center OIDC; requires the relevant licensed components. Source: https://docs.confluent.io/platform/current/security/authentication/sso-for-c3/overview.html (reviewed 2026-11-16).

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. The Platform guide says Confluent’s annual SOC 2 report is available on request. It does not supply the current report period or customer-environment scope; its separate FIPS configuration guidance must not be treated as a whole-deployment attestation. Scope: Vendor security-controls report availability and deployment configuration; actual attestation scope unresolved. Source: https://docs.confluent.io/platform/current/security/compliance/overview.html (reviewed 2026-11-16).

- Security controls: Documented. CFK telemetry is disabled by default; enabling Health+ sends service metadata to Confluent. The built-in JMX Prometheus exporter lacks authentication/encryption and cannot be disabled through CFK, so restrict access at the network boundary and configure other security surfaces separately. Current review: CONFSA-2026-37 covers CVE-2026-114938 in package/archive installs using affected customer JDKs and in the advisory's Platform, Control Center, CMF, Flink, operator, Gateway and CFK init-container image ranges. Fixed-runtime releases were still in preparation. Apply -XX:-UseBASE64Intrinsics, restart and verify every affected Java process until a fixed vendor image or JDK is deployed. Scope: Confluent Platform 7.6.x–8.4.x, Control Center 2.0.x–2.7.x and the exact Docker-image ranges in CONFSA-2026-37. Source: https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://docs.confluent.io/operator/current/co-monitor-cp.html.

- Air-gapped operation: Sources checked — unresolved. CFK documents copying the required tagged Platform/operator/init-container images into a private registry and configuring pulls from it. This establishes private image delivery, but the reviewed guide does not establish end-to-end offline licensing, dependencies or updates for the selected stack. Scope: CFK private-registry installation mechanics; full disconnected operation remains unresolved. Source: https://docs.confluent.io/operator/current/co-custom-registry.html (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. The CFK guide installs confluent-for-kubernetes from Confluent’s Helm repository, then manages Platform components through custom resources. The repository index moves; select a CFK/chart release compatible with the Platform components and Kubernetes version. Scope: Confluent for Kubernetes deployment; commercial subscription applies. Source: https://docs.confluent.io/operator/current/co-deploy-operator.html (reviewed 2026-11-16). Deployment artifact: https://packages.confluent.io/helm/index.yaml. Artifact reference: moving Helm repository index; select compatible chart version.

- Minimum footprint / sizing: Documented. The current CFK guide starts with three Kafka brokers and three KRaft controllers. Each broker’s minimum is 4 CPUs, 16 GB RAM and 1 TB disk; the production column is larger. Controllers and other components add resources. Scope: CFK minimum cluster planning; not aggregate production sizing or pre-8.0 ZooKeeper guidance. Source: https://docs.confluent.io/operator/current/co-plan-sizing.html (reviewed 2026-11-16).

- License pricing: Documented. This entry specifically covers deployment through Confluent for Kubernetes. Confluent states that deploying with CFK requires a subscription and applies licensing requirements to every Confluent Platform component in that cluster. Some components can use Apache 2.0 or Confluent Community licenses outside this CFK path, but that does not make the selected CFK deployment an open-source offering. Scope: Confluent Platform Self-Managed: software license terms; infrastructure and operating costs are separate. Source: https://docs.confluent.io/platform/current/installation/license.html (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed compatibility matrix dates CFK 3.4.x to 2026-10-28, with standard support through 2028-10-28. It supports Platform 7.6.x–8.4.x and lists separate Control Center and Kubernetes ranges. The operator, init container and Platform have distinct versions; do not use a Platform patch number as the chart/operator version. Scope: CFK 3.4 release-line/support and component compatibility; not a claim about the newest Platform patch. Source: https://docs.confluent.io/operator/current/co-supported-environments.html (reviewed 2026-11-16).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Confluent Platform November security patches (security-advisory): Vendor advisories cover broker/Connect, CA trust, JWT, ZooKeeper and denial-of-service issues; component conditions vary. Scope: Confluent Platform fixes: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3 or 8.4.1, as applicable to each advisory. CFK/operator versions are separate. Conditions: Kafka Connect admin.listeners creates a separate affected administrative surface. ZooKeeper fixes apply only to the vendor-identified 7.x lines; do not transfer these claims to Confluent Cloud. Action: Use each advisory to choose the patched branch and compatible CFK/components. Until patched, remove the separate Connect admin.listeners setting. Source: https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes; reviewed 2026-11-17. Supporting source: Compromised CA trust remediation — https://support.confluent.io/hc/en-us/articles/55611336006292-CONFSA-2026-33-CVE-2026-114820-CVE-2026-114406-Confluent-Platform-Compromised-eMudhra-Certificate-Authority-Roots-and-intermediates. Supporting source: Connect administrative listener mitigation — https://support.confluent.io/hc/en-us/articles/55610452168340-CONFSA-2026-27-CVE-2026-115644-Confluent-Platform-Missing-Access-Control-Unauthenticated-Access-to-Kafka-Connect-Logging-API.

- Confluent CONFSA-2026-37 Java4Shell guidance (security-advisory): CONFSA-2026-37 covers CVE-2026-114938 in customer-JDK installs and multiple Confluent Docker-image ranges. Scope: Confluent Platform 7.6.x–8.4.x, Control Center 2.0.x–2.7.x and the exact additional image ranges in the advisory. Conditions: Package/archive installs inherit the customer JDK; Docker applicability depends on the image and tag. Action: Apply -XX:-UseBASE64Intrinsics, restart and verify every affected Java process until a fixed vendor image or JDK is deployed. Source: https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell; reviewed 2026-11-19.



