GitHub Enterprise Cloud (with data residency)
Last updated: October 29, 2026
Span connects to GitHub Enterprise Cloud with data residency through the GitHub Enterprise integration. That is GitHub's cloud tenant on your own ghe.com subdomain (for example, https://acme.ghe.com), not github.com.
Why it matters
Data residency tenants live on their own host, so the standard GitHub card cannot reach them. This setup creates a GitHub App on your tenant so Span can read pull requests, reviews, commits, and repository activity there, the same data it reads from github.com.
How it works
Span creates a public GitHub App inside one organization on your tenant (the app-owner organization). Because the app is public on the tenant, you can install it on any organization there.
The app is read-only. Span never writes to GitHub.
Each organization you install the app on is a separate connection. Span syncs each one about every 2 hours.
If your teams use github.com (including a standard GitHub Enterprise Cloud plan on github.com), connect the GitHub integration instead. This article is only for Cloud with data residency.
Setup
Before you begin, you need:
The Manage Integrations permission in Span. Owners, Admins, and the Integration Admins group have it by default.
Permission to create a GitHub App on the tenant (typically an owner of the app-owner organization).
Your enterprise hostname, for example
acme.ghe.com. Hostname only, nohttps://.The name of the GitHub organization that should own the app.
Popups allowed for Span. GitHub App creation opens in a new tab.
Step 1: Open GitHub Enterprise in Span
Go to Settings → Integrations.
Click Set Up on the GitHub Enterprise card.
Step 2: Create the GitHub App
Under GitHub App Creation (status Not created until this succeeds):
Set Deployment to Cloud (with data residency).
Enter the Hostname, for example
acme.ghe.com.Enter the App Owner Organization, the organization on that tenant where the app will be created, for example
engineering-org(name only, not a path).Click Create GitHub App.
GitHub opens so you can confirm the app, then redirects back to Span. The badge changes to Created.
Step 3: Connect organizations
Connect stays disabled until the app exists ("Complete the setup above before connecting.").
Click Connect.
Install the app on each GitHub organization Span should read, and choose all or selected repositories.
Things to know
Server or Cloud (with data residency)? Server is self-hosted on your own infrastructure (for example
github.company.com). Cloud (with data residency) is hosted by GitHub on yourghe.comsubdomain. Pick the option that matches how you sign in to GitHub.The hostname must be a ghe.com subdomain. If you choose Cloud (with data residency) and enter a host that is not under
ghe.com, Span rejects it and tells you to choose Server. The reverse also applies.One app, many organizations. You create the app once. After that, use Connect another to install it on more organizations on the same tenant.
Revert and bug metrics. Span detects reverts on github.com and Azure DevOps only, so PR Revert Rate reads 0 for data residency tenants. Est. Bug PR Density runs when all of an organization's Git connections are github.com or GitLab, so it doesn't run with a GitHub Enterprise connection.
Data refreshes about every 2 hours. New activity and newly granted repositories show after the next sync.
Troubleshooting
The Create GitHub App tab did not open: allow popups for Span and try again.
Connect is disabled: finish GitHub App Creation first. Connect unlocks when the app status is Created.
The hostname is rejected: remove
https://and any path, and check that you picked the right Deployment.The connection shows Reconnect required: Span could not authenticate to the tenant twice in a row. Open the integration and choose Reconnect.
Related articles
Ways to connect GitHub to Span
How to create an Integrations Admin in Span
Need help?
Contact your Span account team or reach out to support@span.app.