# Oracle OpenGrok

[Oracle OpenGrok](https://github.com/oracle/opengrok) was traditionally the most popular open source code search tool. Originally developed inside Sun Microsystems around 2004, it’s now an Oracle open source project after Oracle acquired Sun.

Sourcegraph is a good replacement for OpenGrok for almost every organization.

- [Migrating from OpenGrok to Sourcegraph](https://docs.sourcegraph.com/admin/migration/opengrok) (Sourcegraph documentation)

## Pros

- Simple interface
- Support for non-Git repositories
- Easy deployment (for Java shops)

## Cons

- Slow and difficult-to-manage indexing process (leading to stale results for users)
- Poor support for searching/browsing multiple commits and branches
- Poor scalability to many repositories and for large repositories
- Inflexible and buggy API (using the new REST API)


<section class="h0Wrapper headingWrapper"><section class="h1Wrapper headingWrapper"><h1 id="oracle-opengrok"><a class="anchor" aria-hidden tabindex="-1" href="#oracle-opengrok"><span class="icon icon-link"></span></a>Oracle OpenGrok</h1>
<p><a href="https://github.com/oracle/opengrok">Oracle OpenGrok</a> was traditionally the most popular open source code search tool. Originally developed inside Sun Microsystems around 2004, it’s now an Oracle open source project after Oracle acquired Sun.</p>
<p>Sourcegraph is a good replacement for OpenGrok for almost every organization.</p>
<ul>
<li><a href="https://docs.sourcegraph.com/admin/migration/opengrok">Migrating from OpenGrok to Sourcegraph</a> (Sourcegraph documentation)</li>
</ul>
<section class="h2Wrapper headingWrapper"><h2 id="pros"><a class="anchor" aria-hidden tabindex="-1" href="#pros"><span class="icon icon-link"></span></a>Pros</h2>
<ul>
<li>Simple interface</li>
<li>Support for non-Git repositories</li>
<li>Easy deployment (for Java shops)</li>
</ul>
</section><section class="h2Wrapper headingWrapper"><h2 id="cons"><a class="anchor" aria-hidden tabindex="-1" href="#cons"><span class="icon icon-link"></span></a>Cons</h2>
<ul>
<li>Slow and difficult-to-manage indexing process (leading to stale results for users)</li>
<li>Poor support for searching/browsing multiple commits and branches</li>
<li>Poor scalability to many repositories and for large repositories</li>
<li>Inflexible and buggy API (using the new REST API)</li>
</ul></section></section></section>