OpenGrok

OpenGrok is a self-hosted engine for searching and browsing source code and its history. It suits teams that can operate an indexed web application, especially those working across varied version-control systems. Its search and navigation are broad, but deployment and memory needs make it a poor fit for anyone seeking a managed, low-maintenance service.

Overview

OpenGrok builds an index of source trees and presents results through a read-only web interface. That makes it useful for finding code and understanding how it changed, without turning the browser into an editing environment. The project is open source under the CDDL license and costs nothing.

Key features

Search covers full text, definitions, symbols, paths, and revision history. Subtree searches, wildcards, and date-range filters help narrow a query across large repositories. Regex search is not supported, so developers who rely on regular-expression queries should look elsewhere.

The browser combines syntax-highlighted cross-references with file history, revision diffs, and directory history. This is a strong set of tools for tracing code relationships and changes; the interface remains read-only, however, so it is for discovery and review rather than editing.

OpenGrok supports Git, Mercurial, Subversion, CVS, Perforce, ClearCase, Bazaar, Monotone, Razor, RCS, SCCS, Teamware, and AccuRev. That breadth can simplify search across repositories using different systems. Plugins can extend support for programming languages or revision-control systems when a codebase needs something beyond the built-in integrations.

The web application includes a REST API at /api/v1/. Its granular authorization framework allows access to be controlled, while authentication is delegated to the application server or a reverse proxy. API bearer tokens require HTTPS unless the application is explicitly configured to permit insecure token use.

Pricing

OpenGrok is free, with no paid tier in its plan: free for the open-source project under the CDDL license. The plan covers codebase indexing and code navigation. It does not include regex search, so the zero price does not change that functional limitation.

Platforms

OpenGrok supports API, Linux, macOS, self-hosted, web, and Windows environments. Deployment involves creating an index and deploying the web application. The setup guide centers on Unix-like systems, with Windows commands and paths adjusted accordingly. Requirements include Java 21 through 25, Universal Ctags, a servlet container such as Tomcat 10.x, and a recent browser for clients. The indexer usually runs with an 8 GB JVM heap, and the web application needs more memory, so hosting capacity is part of the real cost of using this free software.

Who it's for

OpenGrok is a sensible choice for engineering teams that need searchable, navigable indexes of self-hosted source trees and can maintain the supporting Java application and indexing process. Its multiple repository integrations are particularly useful in organizations with mixed version-control systems. It is less suitable for individuals or teams who want a hosted service, need regex search, or cannot allocate memory and operational effort to indexing and serving the application.

The project is maintained by enthusiasts and volunteers around the world. It directs users to discussions and mailing lists for support, and to GitHub Issues for bug reports and feature requests. The releases page identifies version 1.14.19 as the latest release and says it allows Java 25.

Pros and cons

• Pros: Broad revision-control support makes one search interface practical across repositories using many different systems.
• Pros: History, diffs, directory browsing, and syntax-highlighted cross-references support code investigation beyond simple text matching.
• Pros: A REST API and extensible plugins provide routes to integrate or expand the application.
• Cons: Setup requires indexing and deploying a Java web application, with a typical 8 GB JVM heap for the indexer and still more memory for the web app.
• Cons: Regex search is absent, and the browser is read-only.
• Cons: Authentication depends on the application server or reverse proxy, and API bearer tokens need HTTPS by default.

Alternatives

For a broader comparison, browse the Code Search Tools category. Choose ast-grep instead if you want a free option spanning API, extension, desktop, and web platforms. Code Search is worth considering for its free Community plan, which includes unlimited users, repository-wide find and replace, a CLI and MCP server, and SCIP code intelligence.

Pick sqry for a free, MIT-licensed tool that runs locally on Linux, macOS, or Windows. Shebe is another free local-search option, with API, self-hosted, and Windows support and an Apache-2.0 license. LXR Cross Referencer is a free, self-installed alternative for Linux, self-hosted, and web environments.

Chatterbox TTS is another listed alternative. Code Fundi has a freemium model and a Dev plan priced at $21 a month, with 5,000 Credits/Mo, 10 Private Repo Indexes, multi-codebase search/chat, and priority support. Sourcebot is also an alternative, with a free Basic plan and a free trial.

Verdict

Choose OpenGrok if your team needs code search and history browsing across self-hosted repositories, particularly when those repositories use different revision-control systems. Its strongest case is broad navigation at no software cost; its chief trade-off is the Java deployment, indexing, and memory overhead. Teams seeking managed convenience or regex search should choose another tool.