diff --git a/code-review/people.mdx b/code-review/people.mdx
index 9e9d771..7b7d204 100644
--- a/code-review/people.mdx
+++ b/code-review/people.mdx
@@ -8,7 +8,7 @@ A developer needs a Code Review seat for Hacktron to review their pull requests
 
 ## Requirements
 
-- An active free trial or paid Hacktronsubscription
+- An active free trial or paid Hacktron subscription
 - A connected [Git provider integration](/platform/repositories)
 
 ## Auto-assign seats on PR
diff --git a/platform/repositories/gitlab.mdx b/platform/repositories/gitlab.mdx
index 8a969d1..3ec4507 100644
--- a/platform/repositories/gitlab.mdx
+++ b/platform/repositories/gitlab.mdx
@@ -1,6 +1,6 @@
 ---
 title: "GitLab"
-description: "Configure repository access for GitLab.com."
+description: "Configure repository access for GitLab.com and self-hosted GitLab."
 ---
 
 ## Prerequisites
@@ -72,3 +72,36 @@ This is required to create a service account for Hacktron to use.
 </Steps>
 
 That's it! Hacktron will now run security reviews for every pull request in the selected repositories.
+
+## Self-hosted GitLab / GitLab Enterprise
+
+Hacktron supports self-hosted GitLab and GitLab Enterprise through the same
+Personal Access Token flow described above. The only difference is one extra
+step when you connect.
+
+Follow the same **Configure access** steps to create a service account
+(**Settings** → **Service Accounts**), grant it Maintainer access, and generate
+a token from the service account's **Manage access tokens** with the `api`,
+`read_api`, and `read_user` scopes.
+
+<Note>
+  On self-managed GitLab, service accounts require GitLab EE, and by default
+  only an instance administrator can create them (administrators can also
+  allow top-level group Owners to create them). Alternatively, a personal
+  access token from any user with Maintainer access and the same scopes works
+  identically.
+</Note>
+
+When you open the **Connect GitLab** modal in Hacktron, select **Self-hosted /
+GitLab Enterprise** and enter your instance's base URL (e.g.
+`https://gitlab.example.com`) before entering the token.
+
+<Note>
+  Self-hosted prerequisites:
+  - Your GitLab instance must be reachable from Hacktron over HTTPS with a
+    valid TLS certificate.
+  - GitLab installed under a URL subpath (e.g. `https://example.com/gitlab`)
+    is not supported — the base URL must be the instance origin.
+  - The token must carry the `api`, `read_api`, and `read_user` scopes on
+    your self-hosted instance.
+</Note>