Apache Pulsar

Distributed publish-subscribe messaging and streaming platform for persistent event workloads.

4 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

    Use the official Helm chart on a customer-operated Kubernetes cluster; standalone Docker is documented for development and evaluation.

  2. Operated by

    Your team

    Customer manages brokers, bookies, metadata, durable volumes, retention, access controls and upgrades.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Apache Pulsar 4.2 deployment on AWS ↗ · Source checked 2026-11-12

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

Install methodUse the official Helm chart on a customer-operated Kubernetes cluster; standalone Docker is documented for development and evaluation.
InfrastructureServers / containers
Customer-operated brokers, BookKeeper storage and required metadata services. 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 Pulsar. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.
LicenseApache License 2.0 for upstream Apache Pulsar.

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.

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

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

Pulsar 5.0 documents OIDC bearer-token authentication for clients, principals and roles used by broker/admin operations. This is not evidence of a maintained browser-console login integration. Select the actual administrative UI and its compatible identity integration before treating user SSO as confirmed.

Apache Pulsar 5.0 core client identity; browser/user-console federation remains unconfirmed · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

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

The Apache-maintained Helm chart includes the Pulsar service components. The deployment guide separates non-production quickstart from production preparation, storage and sustained-load configuration.

Pulsar 4.2.x deployment guide; select a chart matching the deployed application version · Source ↗ · Deployment artifact ↗ (repository default branch (moving; select matching application release)) · Reviewed 2026-11-14

Documented · Editor reviewed.

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

The reviewed upstream Helm values request 256 MiB/0.1 CPU per ZooKeeper pod (three replicas) and 512 MiB/0.2 CPU per BookKeeper pod (four replicas). These active scheduling requests cover only two components, not their actual capacity or the complete broker/proxy/storage/monitoring cluster. The moving chart identifies appVersion 5.0.1; pin and tune a compatible release for workload, replication and HA.

Moving upstream Helm chart component defaults reviewed on this date; not a complete minimum, benchmark or replacement for the separately retained 4.2.x deployment guide · Source ↗ · Chart appVersion metadata ↗ · BookKeeper request template ↗ · ZooKeeper request template ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The upstream v5.0.1 core is Apache-2.0 licensed, with bundled third-party notices and components governed by their own terms. Hosted Pulsar services and vendor support are separate commercial offerings.

Versioned Apache Pulsar core; no managed-service or enterprise-support entitlement inferred · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The publisher-designated GitHub release checked was v5.0.1, published 2026-10-26. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.

Upstream apache/pulsar release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Show all fields (7 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.

Scope & considerations

The cited 4.2 deployment guide belongs to a maintained release line. Match chart and service versions; standalone mode is not equivalent to a resilient production cluster. Connectors and remote sinks have separate boundaries.

Community & maintenance

Apache-governed project with a long public release history; the official release index records 5.0.0 and 5.0.1 plus maintenance of 4.2 in October 2026.

Category fit

Streaming
Distributed messaging and streaming with persistent topics and separately scalable serving and storage components.

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 KafkaDistributed event streaming platform for durable publication, storage and consumption of event streams.
    • Google Cloud
    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 Pulsar 4.2 deployment on AWS ↗ · AWS

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

      The upstream 4.2 guide provisions EC2 instances and networking with Terraform, then installs Pulsar with Ansible in the customer AWS account. Review the selected release, instance types, persistence and network access before using the example.

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

Suggest a correction · Back to directory