install

Additional install commands

macOS

Homebrewverified · 100%

brew install druid

local Homebrew formula metadata

Linux

Nixverified · 92%

nix profile install nixpkgs#druid

nixpkgs package indexes · pkgs/by-name/dr/druid/package.nix · source: api.github.com

overview

Package summary

High-performance, column-oriented, distributed data store

Project links

Commands and aliases

druid-broker.sh
druid-coordinator.sh
druid-historical.sh
druid-jconsole.sh
druid-middleManager.sh
druid-node.sh
druid-overlord.sh
druid-router.sh

history

Project history and usage

Apache Druid is a high-performance real-time analytics database aimed at fast ingestion, low-latency OLAP queries, operational dashboards, and high-concurrency analytical applications. In package-manager terms, the Homebrew formula is less a tiny CLI utility and more a local entry point into a distributed data system with multiple node-role scripts.

Project history

Druid entered the Apache Incubator on February 28, 2018. During incubation, source control moved to ASF Git/GitHub, incubating releases were cut in 2018 and 2019, and the project graduated as an Apache top-level project on December 18, 2019.

The current Apache Druid repository and website present Druid as a real-time analytics database with native ingestion, SQL/native query support, a web console, APIs, and deployment paths for local, Docker, and Kubernetes environments.

Adoption history

Druid adoption is tied to workloads that need fast ingest plus interactive analytical queries, especially dashboards, operational analytics, and user-facing data applications. Its Apache governance, public mailing lists, Slack/community pages, official Docker image, and separate Kubernetes operator are signals of an ecosystem beyond a single package.

How it is used

The Homebrew package exposes scripts for Druid process roles such as broker, coordinator, historical, middleManager, overlord, router, and node. Users typically start with the quickstart or Docker/Kubernetes deployment paths, then configure runtime properties under the documented `conf/druid` layout.

Why package nerds care

Druid is significant to package maintainers because it stretches the definition of a package: installing it gives local executables, but the software is really a cluster with role-specific daemons, config trees, Java runtime requirements, web UI, APIs, and external integrations. It is a reminder that data infrastructure packages often package orchestration entry points as much as binaries.

Timeline

2018-02-28: Druid enters the Apache Incubator.
2018-07-06: Druid source control moves to ASF Git/GitHub.
2018-12-12: Druid 0.13.0-incubating is released.
2019-04-09: Druid 0.14.0-incubating is released.
2019-12-18: Druid graduates as an Apache top-level project.
Docs era: Apache Druid publishes docs, quickstarts, Docker guidance, and a separate Kubernetes operator.

Related projects

Apache Druid Operator is maintained separately for Kubernetes deployments.
The Druid website source is maintained separately from the main code repository.
Druid commonly integrates with streaming and batch ingestion systems and exposes HTTP and JDBC query APIs.

Sources

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for druid. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 1 platform targets.
Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: conf/druid/_common/common.runtime.propertiesconf/druid/_common/log4j2.xmlconf/druid/broker/runtime.propertiesconf/druid/coordinator/runtime.propertiesconf/druid/historical/runtime.propertiesconf/druid/middleManager/runtime.propertiesconf/druid/overlord/runtime.properties

executables

Installed executables

Command	Kind	Exposure
`druid-broker.sh`	cli	global executable
`druid-coordinator.sh`	cli	global executable
`druid-historical.sh`	cli	global executable
`druid-jconsole.sh`	cli	global executable
`druid-middleManager.sh`	cli	global executable
`druid-node.sh`	cli	global executable
`druid-overlord.sh`	cli	global executable
`druid-router.sh`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version37.0.0

manager updated2026-06-22

local dataok

upstreamnot checked

latest detectednot detected

https://druid.apache.org/

infoRelease/tag comparison is only available for GitHub repositories.https://druid.apache.org/none confidence

install metadata

Package metadata

Package key	brew:druid
Version	37.0.0
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/druid
Homepage	https://druid.apache.org/
Repository	https://github.com/apache/druid
Upstream docs	https://druid.apache.org/docs/latest
License	Apache-2.0
Source archive	https://www.apache.org/dyn/closer.lua?path=druid/37.0.0/apache-druid-37.0.0-bin.tar.gz
Last updated	2026-06-22T14:03:12-07:00
Pulse	updated
Dependencies	openjdk@21
Bottle	available (on all)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	druid
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

druid

nix profile install nixpkgs#druid

normalized package name match
Matched by: Druid

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/dr/druid/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/druid.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install druid with Homebrew, Nix