Choosing the wrong deployment model can force a large migration. Treat this decision as strategic and involve compliance, security, and operations stakeholders early to avoid unexpected costs and downtime.





- Compliance and legal constraints usually determine the correct model more than developer preferences.
- Examples:
- Defense contractors or investment banks: likely Enterprise Managed Users (EMUs), possibly combined with data residency to control identities and data location.
- Tech startups relying on external open-source contributions: typically personal accounts on GitHub Enterprise Cloud.
- Government agencies or organizations with air-gapped networks: typically GitHub Enterprise Server.
-
Enterprise Managed Users (EMUs)
- Provisioned and managed through your identity provider (SCIM/IdP); no self-registration for EMUs.
- Scoped to the enterprise; administrative policies can restrict EMUs from interacting with external public repositories (for example, limiting forks or outside contributions).
- Use a username namespace and naming conventions that distinguish them from personal accounts.
-
GitHub Enterprise Server
- Full operational control: updates, backups, network isolation, and access control are your responsibility.
- Requires infrastructure operations, planning for upgrades, disaster recovery, and availability SLAs.
Exam and architecture tips
- Watch for trigger phrases in scenarios:
- “Code must remain in the EU” → Enterprise Cloud with data residency.
- “Users must not be allowed to contribute to public repositories” or “centralized identity” → EMUs.
- “Air-gapped”, “no cloud”, or “full operational control” → Enterprise Server.
- Map scenario constraints (data residency, identity management, network isolation) to the three main models. That mapping helps you choose quickly and justify the decision.
- GitHub Enterprise Cloud overview
- Enterprise Managed Users (EMUs)
- Data residency for GitHub Enterprise Cloud
- GitHub Enterprise Server documentation
Map constraints to deployment models: data residency → Enterprise Cloud (data residency); identity control → EMUs; network isolation/air-gap → Enterprise Server. This mapping is the fastest way to pick the correct deployment for architecture decisions and exam questions.