> ## Documentation Index
> Fetch the complete documentation index at: https://docs.weaveos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub Enterprise Cloud (GHE.com)

> Connect a GitHub Enterprise Cloud with data residency organization on GHE.com using a private GitHub App

GitHub Enterprise Cloud with data residency is hosted by GitHub, but each enterprise gets its own address on GHE.com, such as `https://octocorp.ghe.com`. It is separate from github.com, so the standard [GitHub connection](/code-platforms/github) can't reach it. It isn't [GitHub Enterprise Server](/code-platforms/github-enterprise-server) either; that product runs on infrastructure your company operates.

| If your organization's address is… | Use |
| - | - |
| `https://github.com/ORG` | [GitHub](/code-platforms/github) |
| `https://SUBDOMAIN.ghe.com/ORG` | GitHub Enterprise Cloud (GHE.com), described here |
| Any other domain, such as `https://github.example.com/ORG` | [GitHub Enterprise Server](/code-platforms/github-enterprise-server) |

<Note>
  GHE.com connections are enabled for individual Weave organizations. Contact Weave to request access.
</Note>

## Connect an organization

1. In Weave's GitHub connection settings, select **GitHub Enterprise Cloud (GHE.com)**.
2. Enter your organization URL, such as `https://octocorp.ghe.com/engineering`.
3. On GitHub, approve creation of the private Weave App in that organization.
4. On GitHub's installation page, choose which repositories the App can read and click **Install**.
5. GitHub redirects you back to Weave, which verifies the connection and starts repository discovery automatically.

You need permission to manage Weave connections and to create and install Apps in the GitHub organization. Weave sign-in is unchanged; no GHE.com user sign-in is needed. Requests that need approval from a GitHub enterprise owner stay pending until approved.

## How it works

Each organization gets its own private Weave App, created in that organization. Weave stores the App's private key and webhook secret encrypted for that connection only. Weave sends REST and GraphQL requests to your enterprise's API host, `https://api.SUBDOMAIN.ghe.com`, and clones repositories from `https://SUBDOMAIN.ghe.com`. Requests from a connection can't reach any other host.

The App requests the same read-only permissions and webhook events as the [GitHub Enterprise Server App](/code-platforms/github-enterprise-server#imported-data), and Weave imports the same repository data.

Cloud Copilot billing and verified-domain email enrichment remain github.com features and aren't available through a GHE.com connection.

## Network access

GitHub hosts GHE.com, so you don't need to open firewall ports. If your enterprise restricts access with an IP allow list, add [Weave's outbound IP addresses](/data-sources/reference#ip-addresses) for App, API, and Git access. GitHub must also be able to deliver webhooks to Weave.

## Resume and maintain a connection

Saved GHE.com connections have the same controls as Enterprise Server connections: continue a pending installation, refresh, replace the App, or disconnect. See [Resume and maintain a connection](/code-platforms/github-enterprise-server#resume-and-maintain-a-connection).

If you started setup from the Enterprise Server option with a GHE.com address, Weave may already have saved the App. Open the GHE.com connection page and choose **Continue installation** on that organization. You don't need to create another App.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.