
# Apache Druid

Column-oriented analytics database for interactive queries over streaming and historical event data.

Canonical page: https://launchinyourcloud.com/directory/apache-druid/
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.


## Apache Druid

Column-oriented analytics database for interactive queries over streaming and historical event data.

- Listing: https://launchinyourcloud.com/directory/apache-druid/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Apache Druid.
- Licensing model: open-source
- Installation: Run the official server distribution with bin/start-druid; distributed production deployments require the documented cluster services and storage configuration.
- Architecture: Customer-operated JVM analytics services, metadata store and deep storage
- Operations: Customer manages cluster sizing, ingestion, metadata and deep storage, access controls, backups and upgrades.
- Product website: https://druid.apache.org/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The smallest bundled configurations are evaluation examples. Data ingestion connectors and storage destinations can involve external services; configure their account and network boundaries separately. Apache Druid 39.0.0 requires Java 25 and drops Java 21 support. Its upgrade notes also change SQL INSERT/REPLACE authorization, replace SysMonitor with OshiSysMonitor, add taskStatus to task/run/time metrics, change Netty direct-memory behavior, and move the bundled MariaDB driver to 3.5.10 with jdbc:mariadb: preferred. Test permissions, dashboards, memory limits and metadata-store URLs before rollout.

Apache License 2.0 for upstream Apache Druid. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated JVM analytics services, metadata store and deep storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- data-analytics: Real-time OLAP database for SQL analysis of ingested streaming and batch data; this is an analytics engine rather than a dashboard authoring application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://druid.apache.org/faq/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://druid.apache.org/faq/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://druid.apache.org/faq/ (checked 2026-11-12). 


### Cloud deployment evidence

- Apache Druid cloud deployment FAQ (aws, azure, gcp): https://druid.apache.org/faq/
  The Apache project explicitly identifies AWS, Google Cloud and Azure as deployment environments for Druid. This is a project compatibility statement paired with the installation documentation, not a managed service or certification; configure metadata, deep storage and cluster operations separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Apache project with a maintained upstream release history and a project-curated production adopter directory including Adikteev, AdsWizz and Airbnb.

Reviewed 2026-11-10.

- Current Druid releases: https://github.com/apache/druid/releases

- Named production adopters: https://druid.apache.org/druid-powered/

### Sources

- Official installation and runtime: https://druid.apache.org/docs/latest/operations/single-server/

- Upstream project and capabilities: https://github.com/apache/druid

- Current upstream license: https://github.com/apache/druid/blob/master/LICENSE

- Analytics functionality: https://druid.apache.org/

- Apache Druid 39.0.0 release: https://github.com/apache/druid/releases/tag/druid-39.0.0

- Apache Druid 39.0.0 upgrade notes: https://druid.apache.org/docs/39.0.0/release-info/upgrade-notes

### Licensing sources

- https://github.com/apache/druid/blob/master/LICENSE

### Infrastructure sources

- https://druid.apache.org/docs/latest/operations/single-server/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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. The druid-kerberos extension provides SPNEGO/GSSAPI authentication for Druid HTTP endpoints, with service principals, keytabs, cookies and authorizer mapping. Configure compatible browser/API clients and protect every endpoint; this is Kerberos federation, not native SAML/OIDC. Scope: Upstream HTTP Kerberos/SPNEGO authentication extension. Source: https://druid.apache.org/docs/latest/development/extensions-core/druid-kerberos/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The server distribution includes bin/start-druid, which derives memory settings from host resources. Older single-server reference scripts are deprecated; production cluster storage/services need a separate architecture plan. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://druid.apache.org/docs/latest/operations/single-server/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current 39.0.0 local quickstart requires at least 6 GiB RAM and Java 25. It is an introductory single-machine ingestion/query setup, not a production or HA footprint. Data volume, ingestion tasks, service roles and availability requirements need separate sizing. Scope: Druid 39 local tutorial baseline; production capacity excluded. Source: https://druid.apache.org/docs/latest/tutorials/index.html (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/apache/druid/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Apache Druid druid-39.0.0 was published November 19, 2026. It requires Java 25, changes SQL write authorization and monitoring labels, replaces SysMonitor, changes Netty direct-memory behavior and updates MariaDB Connector/J. Review the complete incompatible-change and upgrade notes. Scope: Upstream Apache Druid release; deployment packages and commercial distributions may differ. Source: https://github.com/apache/druid/releases/tag/druid-39.0.0 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/apache/druid/releases/tag/druid-38.0.0. Supporting source: Version-specific upgrade notes — https://druid.apache.org/docs/39.0.0/release-info/upgrade-notes.






