# Install groonga with Homebrew Fulltext search engine and column store. Version 16.0.8 via Homebrew; verified 2026-07-14. ## Install ```sh sudo av install brew:groonga ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install groonga ``` Evidence: provider-native install command ## Package facts - **Package key:** brew:groonga - **Package manager:** Homebrew - **Version:** 16.0.8 - **Source summary:** Fulltext search engine and column store - **Homepage:** - **Repository:** - **Last updated:** 2026-07-14T06:50:51Z - **Generated:** 2026-08-03T00:40:33+00:00 ## Executables - groonga (alias) - groonga-suggest-create-dataset (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 16.0.8 ## Project history and usage Groonga is an open source full-text search engine and column-oriented DBMS packaged for command-line and server use. In package-manager terms it sits in an unusual but useful space: it is both a standalone search/database executable and the C library foundation for language bindings and storage-engine integrations. The project is especially significant for Japanese and multilingual search because its design combines inverted indexes, instant updates, n-gram and word tokenizers, read-lock-free reads, geo search, and column-store aggregation in one embeddable engine. ### Project history Groonga grew out of the Senna search-engine lineage. The Groonga news archive records a 'Senna -> groonga' transition on 2009-01-14, followed by 0.x releases in 2010 and the Groonga 1.0.0 release on 2010-08-29. The 2.0.0 release announcement in 2012 framed the major-version bump as a signal that Groonga had become practical enough for wider use after steady feature additions and bug fixes. From that point the project kept a long-running monthly-ish release culture, visible in the official news archive across the 2.x through later numbered series. The core documentation describes Groonga as both a fast full-text search engine based on inverted indexes and a column-oriented DBMS. It exposes basic functionality as a C library, provides a server command, and is used by related projects as a library, a server, or a storage engine. ### Adoption history Groonga adoption spread through integrations rather than only through the standalone executable. The official related-projects page lists Mroonga for MySQL, PGroonga for PostgreSQL, Rroonga for Ruby, Nroonga for Node.js, Perl/PHP/Haskell/GObject bindings, client libraries, server utilities, and command-line helpers. The official users page documents production-style uses such as PatentField using Groonga and Mroonga for full-text search, drilldown search, near search, snippets, and column-store features over large patent data, plus smaller web and command-line tools using Rroonga, Mroonga, and other bindings. For package ecosystems, Groonga matters because the same engine appears as a direct package, a dependency of database extensions, and a dependency of language bindings. Installing the formula can support standalone experiments, local indexing tools, or native dependencies for higher-level search stacks. ### How it is used The Homebrew package installs the `groonga` command and related tooling. Users can create and query Groonga databases directly, run the built-in server, or use the C library and protocol endpoints through bindings and clients. Groonga is commonly chosen when an application needs immediate index updates, concurrent reads while updating, multilingual tokenization choices, drilldown/aggregation, or geo search without handing all data to a separate general-purpose search cluster. The project has no general user credential file in the official package-level curation. Configuration is more database/server specific than a single dotfile convention, so this batch leaves config and credentials locations null. ### Why package nerds care Groonga is package-nerd interesting because it is a native C search engine with a broad integration surface: command-line executable, embeddable library, database storage-engine base, PostgreSQL extension base, and language-binding target. Its release cadence and source-package archive make it visible in Unix packaging culture: distributors can package the core engine once, then layer Mroonga, PGroonga, Rroonga, and other related packages on top. It also represents a non-English-first search problem space in package indexes. Tokenizers, MeCab integration, n-gram behavior, and Japanese/Chinese-friendly search are not add-ons; they are central to why the package exists. ### Timeline - 2009: Official news records the transition from Senna to Groonga. - 2010: Groonga 1.0.0 was released on 2010-08-29. - 2012: Groonga 2.0.0 was released, with the announcement emphasizing maturity after steady 1.x development. - 2014: Droonga 1.0.0 was released as a distributed Groonga-related data processing engine. - 2015: PGroonga 1.0.0 was released for PostgreSQL full-text search backed by Groonga. - 2020s: The official news archive shows continued major-series releases and ongoing PGroonga activity. ### Related projects - Mroonga is the MySQL/MariaDB storage-engine integration built on Groonga. - PGroonga is the PostgreSQL extension that uses Groonga as an index for fast multilingual full-text search. - Rroonga, Nroonga, p5-Groonga, Ploonga, Proonga, Haroonga, and Groonga-GObject expose Groonga to language runtimes. - Groonga-client, GQTP clients, and command-line utilities such as grnwrap sit around the standalone server and CLI workflow. ### Sources - - - - - - - - ## Security Notes No matching local secret-handling manifest was found for groonga. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Combined YAML source View the package source record on GitHub. [combined/groonga.yml](https://github.com/automic-vault/db/blob/main/combined/groonga.yml) ## Sources - Nucleus package database - Geiger risk classifier - curated package history - pkgdb category and tag curation