Install sonic with Homebrew, apt, dnf, MacPorts, Nix, pacman

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• sonic

Project history

Sonic was created by Valerian Saliou and the official repository says the project was initially announced on the author's journal. GitHub repository metadata records the public repository as created in February 2019, matching the README's early emphasis on using Sonic at Crisp for production search workloads.

The design centers on the Sonic Channel protocol rather than an HTTP API. That made Sonic feel more like Redis-style infrastructure to package and run: a daemon, a TOML-like configuration file, a TCP port, and client libraries for applications that need to push identifiers into an index and query them later.

Adoption history

The official README lists Crisp and Scrumpy as users and describes Crisp using Sonic for search across messages, conversations, contacts, and helpdesk articles. It also documents official packages for Debian-based systems, Cargo installation, Docker images, and non-official Homebrew packaging.

The package-manager metadata in this batch shows Sonic available beyond Homebrew, including Debian, Ubuntu, Fedora, Arch, MacPorts, and Nix. That spread is notable because Sonic is a niche search daemon, not a general-purpose library.

How it is used

Operators run Sonic with a configuration file, commonly the sample `config.cfg` or a path supplied with `-c` or `--config`. Applications interact with it through Sonic Channel to push, pop, flush, query, and suggest identifiers.

Sonic is commonly attractive for small and medium products that want fast full-text-ish lookup without operating a larger search stack. It stores search terms and identifiers, leaving document storage and enrichment to the caller's database.

Why package nerds care

For package-manager users, Sonic is interesting because it turns a search backend into one installable daemon with modest runtime expectations. It is the kind of package that appeals to people who like replacing a large service dependency with a single binary plus a small config file.

Its continued releases through 2026, including split core/client/server release artifacts, also show a Rust infrastructure tool maturing while still keeping a Unix-friendly operational shape.

Timeline

• 2019: Public GitHub repository created and Sonic documented as running in Crisp search products.
• 2024: Sonic v1.4.9 released on GitHub.
• 2026: Sonic v1.7.0 released on GitHub.

Related projects

• Elasticsearch is the heavier search backend explicitly used as Sonic's comparison point.
• Redis is a useful operational comparison because the README describes Sonic Channel as the only interaction protocol and emphasizes simplicity.
• Sonic Channel client libraries connect Sonic to Node.js, PHP, Rust, Python, Ruby, Go, Java, Elixir, and other ecosystems.

Sources

• https://api.github.com/repos/valeriansaliou/sonic
• https://api.github.com/repos/valeriansaliou/sonic/releases
• https://github.com/valeriansaliou/sonic
• https://github.com/valeriansaliou/sonic/blob/master/CONFIGURATION.md
• input.json source_facts.package-manager