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/github-enterprise-server-developer-fundamentals/4-github-enterprise-server-developer-experience.yml
Copy file name to clipboardExpand all lines: learn-pr/github/github-enterprise-server-developer-fundamentals/includes/1-github-enterprise-server-introduction.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,15 +17,19 @@ This infrastructure may be on-premises, in a private cloud, or hosted with a sup
17
17
GitHub Enterprise Server provides:
18
18
19
19
- Complete data isolation
20
+
20
21
All repositories, issues, pull requests, and metadata live entirely within your organization's environment.
21
22
22
23
- Self-managed operations
24
+
23
25
Your organization controls installation, upgrades, backups, monitoring, and disaster recovery.
24
26
25
27
- Enterprise-grade security controls
28
+
26
29
Features such as subdomain isolation, outbound web proxies, and network segmentation are built in.
27
30
28
31
- Near feature parity with GitHub Enterprise Cloud
32
+
29
33
Most GitHub features are available, though often delayed due to release cadence.
30
34
31
35
> [!IMPORTANT]
@@ -36,15 +40,19 @@ GitHub Enterprise Server provides:
36
40
Organizations typically choose GHES when they need:
37
41
38
42
- Data residency guarantees
43
+
39
44
Source code and metadata must remain within specific geographic or network boundaries.
40
45
41
46
- Regulatory compliance
47
+
42
48
Industries such as finance, healthcare, defense, and government often require self-hosted systems.
43
49
44
50
- Custom security posture
51
+
45
52
Network-level controls, outbound proxies, and strict access segmentation.
46
53
47
54
- Operational sovereignty
55
+
48
56
Full control over uptime, maintenance windows, and system configuration.
49
57
50
58
Developer takeaway: GHES prioritizes control and predictability over speed of feature delivery.
@@ -54,31 +62,39 @@ Developer takeaway: GHES prioritizes control and predictability over speed of fe
54
62
In a self-managed GitHub Enterprise Server environment, responsibility for operating GitHub shifts from GitHub to the customer.
55
63
56
64
- Platform team ownership
65
+
57
66
Platform teams manage installation, upgrades, security patching, backups, monitoring, and availability of the GHES instance.
58
67
59
68
- Developer dependencies on platform teams
69
+
60
70
Developers rely on internal teams for enabling features, configuring integrations, and resolving infrastructure-related issues.
61
71
62
72
- Infrastructure-driven limitations
73
+
63
74
Some capabilities-such as GitHub-hosted runners or cloud-native services-are unavailable, requiring developers to adapt workflows.
64
75
65
76
- Operational awareness
77
+
66
78
Developers must be aware of system constraints, maintenance windows, and version differences that affect day-to-day work.
67
79
68
80
### How GHES fits into regulated and security-sensitive environments
69
81
70
82
GHES is designed for organizations with strict control, compliance, and security requirements.
71
83
72
84
- Data isolation
85
+
73
86
All code, metadata, and logs remain within the organization's network or approved infrastructure.
74
87
75
88
- Regulatory alignment
89
+
76
90
GHES supports compliance requirements common in regulated industries such as finance, healthcare, government, and defense.
77
91
78
92
- Controlled network access
93
+
79
94
Organizations can enforce outbound proxies, restricted connectivity, and network segmentation.
80
95
81
96
- Auditability and traceability
97
+
82
98
All user activity is recorded locally, supporting internal audits and compliance reporting.
83
99
84
100
Key takeaway: GHES provides a GitHub experience that feels familiar, but it is operated and secured like an enterprise platform-updates, availability, and features are managed by the organization, not delivered continuously by GitHub.
Copy file name to clipboardExpand all lines: learn-pr/github/github-enterprise-server-developer-fundamentals/includes/5-github-connect-hybrid-scenarios.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Many organizations choose GitHub Enterprise Server (GHES) to meet strict data co
10
10
11
11
- What to expect as a developer when GitHub Connect is enabled
12
12
13
-
### What is GitHub connect?
13
+
### What is GitHub Connect?
14
14
15
15
GitHub Connect creates a secure link between GitHub Enterprise Server and GitHub Enterprise Cloud. When enabled by administrators, it allows specific features and data to be shared across both environments.
0 commit comments