Livegrep

Paid LinuxSelf-hostedWeb

What Livegrep is

Livegrep is an open-source tool for interactive regular expression search across source repositories, including repositories at roughly gigabyte scale. It combines a codesearch indexing and search backend with a web interface that connects over TCP. Searches use Google's RE2 syntax, with terms such as `path:`, `-path:`, `repo:`, `-repo:` and `max_matches:` for narrowing results. The backend can build an in-memory index or save a standalone index file for reuse, even when the index is too large for RAM. Once an index is built, searches use it without further access to the original Git repositories. The index is usually three to five times the size of indexed text; Livegrep memory-maps it and recommends fast SSDs when it does not fit in RAM. A helper driver can update and index selected GitHub repositories, and the interface can display source files when configured with local source paths. Deployment runs both the backend and web interface. Livegrep is written and run by Nelson Elhage, builds with Bazel, requires a relatively recent C++ compiler, and has a Go frontend.

Who it suits

Livegrep suits developers and teams that want interactive regex searches across source repositories and can run its indexing backend and web interface. Its index and build requirements are relevant when planning a self-hosted deployment.

What it does well

Open-source repository search tool
Supports Google's RE2 regular expression syntax
Indexes can be saved and reused
Can update selected GitHub repositories
Docker deployment is documented

What to know first

Requires running both backend and web interface
Index typically uses three to five times source-text size
Build requires Bazel and a recent C++ compiler

Verdict

Livegrep provides a self-hosted search interface backed by reusable repository indexes. Plan for its index storage and build requirements, especially when the index will not fit in RAM.

Facts from Livegrep's own pages

Architecture: The backend index and search process is written in C++ and the web frontend is implemented in Go. · livegrep.com, 10 Oct 2026
Build requirements: The project builds with Bazel and requires a relatively recent C++ compiler; the initial build downloads around 100 MB of dependencies. · github.com, 10 Oct 2026
Deployment: The project documents Docker images and example commands for running its indexer, backend, and web frontend. · github.com, 10 Oct 2026
Docker: Livegrep's CI builds Docker images on every merge to main, and the repository documents running its indexer, backend, and frontend in containers. · github.com, 4 Oct 2026
File browsing: Livegrep can display source files directly in its interface when configured with local source paths. · github.com, 10 Oct 2026
GitHub integration: A helper called livegrep-github-reindex can automatically update and index selected GitHub repositories. · github.com, 10 Oct 2026
Index files: The backend can save and reuse standalone index files, including indexes too large to fit in RAM. · github.com, 4 Oct 2026
Indexing: Codesearch can build an in-memory index or save an index file that can be reused for later runs. · github.com, 10 Oct 2026
Intended users: The project describes itself as a tool for interactively searching source code, including large repositories. · github.com, 4 Oct 2026
Local deployment: By default, the frontend connects to a local codesearch instance on port 9999 and serves HTTP on port 8910. · github.com, 4 Oct 2026
Maker: Livegrep is written and run by Nelson Elhage. · livegrep.com, 10 Oct 2026
Open source: Livegrep is open source and is written and run by Nelson Elhage. · livegrep.com, 4 Oct 2026
Purpose: Livegrep is an open-source tool for interactive regex search of source repositories around gigabyte scale. · github.com, 10 Oct 2026
Regex engine: Livegrep uses RE2 and inherits its supported syntax. · github.com, 10 Oct 2026
Repository access: After an index is built, Livegrep works from that index without further access to the original Git repositories. · github.com, 10 Oct 2026
Repository browser: Livegrep can display source files directly in its interface when configured with local source paths. · github.com, 4 Oct 2026
Resource requirements: An index is usually 3–5 times the size of indexed text; memory-mapping allows indexes larger than available RAM, while faster SSDs are recommended for performance. · github.com, 10 Oct 2026
Search syntax: The web search supports regular expressions and special terms including path:, repo:, and max_matches:. · livegrep.com, 10 Oct 2026
Self-hosting: To run Livegrep, users invoke both the codesearch backend and the web interface. · github.com, 10 Oct 2026
Support: The about page lists [email protected] as the feedback contact. · livegrep.com, 4 Oct 2026

Where Livegrep stands on Freedom251

Code Search Tools#40 of 42