Skip to main content
GitHub logoGitHub

Make your GitHub code and activity searchable in Glean

Indexes repositories, code, commits, issues, and pull requests across GitHub Cloud, Enterprise Server, and Server. Always scoped to each user's permissions.

GitHub CloudEnterprise ServerServerPermission-awareCode searchPer-user OAuth

Choose your deployment

Glean has a connector for each GitHub hosting model. Pick the one that matches how your organization runs GitHub.

Compare deployments

All three connectors index the same GitHub content (repositories, code, commits, issues, and pull requests) and enforce permissions at query time. They differ in where GitHub is hosted, how Glean authenticates, and a few capabilities.

GitHub CloudEnterprise ServerServer
Best forGitHub.com, including GitHub Enterprise CloudSelf-hosted GitHub Enterprise ServerOn-prem GitHub Server the crawler can reach
AuthenticationGitHub App + per-user OAuthGitHub App + admin personal access tokenGitHub App created on your instance
Per-user OAuth for private reposRequiredNot usedNot used
Multiple instancesNoSupported on one Glean deploymentNo
NetworkGlean-hosted; nothing to exposeInstance must be reachable by the crawlerInstance must be reachable by the crawler
Code SearchOn by defaultOn by defaultOn by default
GitHub PagesLegacy gh-pages sites, by repo listLegacy gh-pages sites, by repo listLegacy gh-pages sites, by repo list

Not sure which you run? Most GitHub.com customers use GitHub Cloud. Choose Enterprise Server or Server only if GitHub is self-hosted in your own environment.

Explore by deployment

Security

Support