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

# The Enterprise Universe

> Overview of GitHub Enterprise deployment models and how to choose among cloud personal accounts, EMUs, data residency, and Enterprise Server based on compliance, identity, and collaboration requirements.

Before you change any configuration, answer the most consequential question a GitHub Enterprise architect faces: which deployment model fits my organization?

This is a high-stakes decision made once—changing it later typically requires a migration project that can take months and cost significant resources. The right way to evaluate options is to map your compliance, identity, and collaboration requirements against each deployment model.

Imagine you are choosing an office space.

## Enterprise Cloud — Personal accounts (a co-working space)

GitHub Enterprise Cloud with personal accounts is like a co-working space. Employees have individual credentials (their own “key card”) and can work from other locations as well. This model emphasizes developer freedom, seamless external collaboration, and public open-source contributions.

![A slide titled "Personal Accounts – A Co-Working Space" showing a simple illustration of a co-working room with desks and people, plus a "Personal Accounts" badge and an icon with the note "Their own personal keycard."](https://mintcdn.com/kodekloud-c4ac6d9a/IdpF6mT8Tun72cng/images/GitHub-Administration-Certification/Foundation-Setup/The-Enterprise-Universe/personal-accounts-coworking-room-keycard.jpg?fit=max\&auto=format\&n=IdpF6mT8Tun72cng\&q=85\&s=f1801d43f32153c40c2dc07f0027e635)

Key characteristics:

* Decentralized identity (personal GitHub accounts).
* Strong support for public open-source work and forking.
* Easier external collaboration and cross-organization access.

## Enterprise Cloud — Enterprise Managed Users (EMUs, a leased floor)

Enterprise Managed Users is like leasing a floor in a corporate building. Your company controls who can enter that floor: badges (accounts) only work for your enterprise. EMUs are centrally provisioned by your identity provider (no self-registration), and policies often restrict public contributions and external forking. Usernames include the enterprise slug—for example, `alice_enterprise`.

![A slide titled "EMU – A Leased Floor" showing a stylized multi-story building with one floor highlighted in purple and labeled "Enterprise Managed Users," plus a green label reading "Your company controls entry."](https://mintcdn.com/kodekloud-c4ac6d9a/IdpF6mT8Tun72cng/images/GitHub-Administration-Certification/Foundation-Setup/The-Enterprise-Universe/emu-purple-floor-company-controls-entry.jpg?fit=max\&auto=format\&n=IdpF6mT8Tun72cng\&q=85\&s=b10c5dafd7e372adbed9b34b831d3deb)

Key characteristics:

* Centralized identity and provisioning via your IdP.
* Enterprise-centric username formats (e.g., `alice_enterprise`).
* Tight policy control over repository visibility and forking.
* Useful where you must restrict contributions or enforce centralized governance.

## Enterprise Cloud with Data Residency

Data residency resembles the leased-floor analogy, but the entire building is physically located where your legal or compliance teams require. For example, storing all GitHub data in Frankfurt to meet GDPR or other regional data locality mandates.

Key characteristics:

* Data stores located in specific geographic regions.
* Designed for compliance with data sovereignty laws and contractual obligations.
* Often paired with EMUs when strict identity and data controls are required.

## GitHub Enterprise Server — Your own building

GitHub Enterprise Server is like purchasing and managing your own building. You control every lock, every light bulb, and every server upgrade. This model gives you maximum control and isolation, but you also assume all operational responsibility.

![A presentation slide titled "Enterprise Server – Your Own Building" showing a house icon containing server racks and an orange "Enterprise Server" label. To the right is a short list of responsibilities: "Every lock," "Every light bulb," and "Every server upgrade."](https://mintcdn.com/kodekloud-c4ac6d9a/IdpF6mT8Tun72cng/images/GitHub-Administration-Certification/Foundation-Setup/The-Enterprise-Universe/enterprise-server-building-locks-lights-upgrades.jpg?fit=max\&auto=format\&n=IdpF6mT8Tun72cng\&q=85\&s=e9148631e70abd7f8dc4b5a1d9f86564)

Key characteristics:

* Complete control over updates, backups, and network isolation.
* Suitable for air-gapped or on-premises-only requirements.
* Operational burden: you own outages, capacity, patching, and security operations.

## Quick comparison

| Deployment Model | Primary control model | External collaboration | Data locality | Typical use cases |
| - | -: | :-: | :-: | - |
| Enterprise Cloud — Personal accounts | Decentralized (individual accounts) | High — supports open-source and cross-org work | Cloud region selected by GitHub | Startups, open-source-focused teams |
| Enterprise Cloud — EMUs | Centralized (IdP-managed) | Restricted by enterprise policy | Cloud region selected by GitHub or combined with data residency | Regulated industries, banks, defense contractors |
| Enterprise Cloud — Data residency | Centralized or decentralized, with region-specific storage | Depends on account type & policy | Data stored in specified region (e.g., Frankfurt) | GDPR, regional compliance requirements |
| Enterprise Server | Fully on-premises | Controlled by your network and policies | You control physical location | Government, air-gapped networks, strict isolation |

## How to choose (decision drivers)

The right choice is driven primarily by legal, compliance, and identity requirements—less so by developer preference. Consider these questions:

* Do regulations require code and metadata to remain in a specific country or region?
* Must user accounts be centrally provisioned and prevented from contributing to public repos?
* Is an air-gapped, on-premises environment required?
* Is external collaboration and public open-source contribution desired?

Examples:

* Defense contractors or investment banks: likely EMUs with possible data residency.
* Tech startups valuing open-source contributions: personal accounts on Enterprise Cloud.
* Government agencies requiring air-gapped infrastructure: GitHub Enterprise Server.

## Exam-focused trigger phrases

Watch for these cues in scenario questions:

* "Code must remain in the EU" → prefer Enterprise Cloud with data residency and EMUs.
* "Users must not contribute to public repositories" or "must be centrally managed" → prefer EMUs.
* "Air-gapped network" or "no cloud access" → choose GitHub Enterprise Server.

## Links and references

* [GitHub Enterprise Cloud overview](https://docs.github.com/en/enterprise-cloud)
* [GitHub Enterprise Server documentation](https://docs.github.com/en/enterprise-server)
* [Identity providers and SAML/SSO integrations](https://docs.github.com/en/authentication)

Map the core requirement (data locality, external collaboration, identity control, air-gapped operations) to the deployment model. Compliance and identity constraints are the most decisive factors.

> [card] [Watch Video](https://learn.kodekloud.com/user/courses/github-administration-certification/module/348b2245-ed3e-4fb7-bf18-37a18b478769/lesson/121ed0e3-5c77-4fe8-bc59-46ca8d4b3c42)


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