GitHub Enterprise Cloud with Data Residency (GHE.com)
Canonical version: GitHub Enterprise Cloud with Data Residency (GHE.com).
GHE.com is the version of GitHub Enterprise Cloud with data residency: a managed cloud GitHub where a company chooses the region its code and data are stored in. Each enterprise gets a dedicated subdomain (e.g. octocorp.ghe.com) with its own namespace, fully isolated from the open-source community on github.com. It exists for organizations with compliance requirements (GDPR-style data localization) that previously had only one real option: self-hosting GitHub Enterprise Server.
Regions
EU (including Azure regions in Norway and Switzerland), Australia, United States, and Japan, with more planned.
How it differs from github.com
- Enterprise Managed Users required: all accounts are provisioned and lifecycle-managed by the company's identity provider (SAML/OIDC + SCIM); users can only access enterprise resources and are invisible to the wider GitHub community
- No public repositories: innersource collaboration happens through internal repositories instead
- Enterprise-specific endpoints: API calls go to
https://api.<company>.ghe.com, not api.github.com - GitHub Copilot: Business or Enterprise subscriptions only (no Copilot Individual), and some Copilot features lag github.com availability
- Centralized governance: billing, administration, and audit run through the enterprise account; billable via Azure subscription or directly, with usage-based options
Versus GitHub Enterprise Server
The pitch over self-hosting: latest features (including Copilot) without waiting for server releases, no maintenance windows, no ops burden, while still meeting residency requirements. GitHub built it as a multi-tenant evolution of its own cloud rather than a packaged server product.
Governance context
GHE.com is the natural home for the enterprise AI-governance stack: GitHub Copilot Managed Settings (enforced client configuration), GitHub Copilot MCP Registry (curated MCP server allowlists), and GitHub Copilot Sandboxing policies all administered from the enterprise account, with data staying in-region.
References
- Overview: https://docs.github.com/en/enterprise-cloud@latest/admin/data-residency/about-github-enterprise-cloud-with-data-residency
- Data storage: https://docs.github.com/en/enterprise-cloud@latest/admin/data-residency/about-storage-of-your-data-with-data-residency
- Feature overview: https://docs.github.com/en/enterprise-cloud@latest/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency
- Getting started: https://docs.github.com/en/enterprise-cloud@latest/admin/data-residency/getting-started-with-data-residency-for-github-enterprise-cloud
- Engineering blog: https://github.blog/engineering/engineering-principles/github-enterprise-cloud-with-data-residency/
Related
- GitHub
- GitHub Copilot
- GitHub Copilot Managed Settings
- GitHub Copilot MCP Registry
- GitHub Copilot Sandboxing
About Sébastien
Ready to get to the next level?
Found this valuable? Share it with someone who needs it.