You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/github/manage-github-actions-enterprise/includes/github-enterprise-models.md
+3-8Lines changed: 3 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,10 +3,9 @@ In this unit, you'll explore the different GitHub Enterprise deployment models
3
3
## How users are managed
4
4
GitHub Enterprise Cloud (GHEC) is a cloud-based solution tailored for organizations that need the flexibility and scalability of GitHub's infrastructure while maintaining enterprise-grade security and compliance. It offers features such as centralized user management, data residency options, and integration with identity providers like SAML and SCIM for single sign-on and user provisioning.
5
5
6
-
GHEC is ideal for globally distributed teams, as it ensures high availability, automated backups, and seamless access to GitHub’s robust collaboration tools. It supports regulatory compliance (e.g., GDPR) and provides detailed audit logs for governance. With GHEC, organizations can leverage GitHub’s advanced capabilities without managing on-premises infrastructure.
7
-
8
-
### Standard User Model
6
+
GHEC is ideal for globally distributed teams, as it ensures high availability, automated backups, and seamless access to GitHub’s robust collaboration tools. It supports regulatory compliance and provides detailed audit logs for governance. With GHEC, organizations can leverage GitHub’s advanced capabilities without managing on-premises infrastructure.
9
7
8
+
### 1. Standard User Model
10
9
This is the traditional user model on GitHub, where users manage their own account.
11
10
12
11
**Characteristics of standard user model**:
@@ -18,7 +17,6 @@ This is the traditional user model on GitHub, where users manage their own accou
18
17
19
18
20
19
### The Enterprise Managed User (EMU) model
21
-
22
20
This is the model designed for organizations requiring centralized user account management, offering better control and compliance features.
23
21
24
22
**In EMU model**:
@@ -30,8 +28,7 @@ This is the model designed for organizations requiring centralized user account
30
28
31
29
32
30
33
-
### GitHub Enterprise Cloud (GHEC) with **Data Residency**
34
-
31
+
### GitHub Enterprise Cloud (GHEC) with **Data Residency**
35
32
GitHub Enterprise Cloud (GHEC) with **Data Residency** is an important feature of GHEC for organizations that must comply with data protection regulations by ensuring specific data is stored in particular geographical regions.
36
33
37
34
**It allows users to**:
@@ -52,8 +49,6 @@ GitHub Enterprise Cloud (GHEC) with **Data Residency** is an important feature o
52
49
- Certain types of backup data may be replicated outside the region but remain encrypted.
53
50
54
51
## 2. GitHub Enterprise Server (GHES)
55
-
56
-
57
52
GitHub Enterprise Server (GHES) is a self-hosted version of GitHub designed for organizations that require complete control over their GitHub instance. It is ideal for companies that want to host their repositories and associated data on-premises or in a private cloud environment for compliance, security, or performance reasons.
0 commit comments