GitLab Self-Managed is GitLab deployed and hosted by the customer, on their own servers or private cloud, rather than on GitLab.com. It ships with the same native Issues tracker as GitLab's SaaS product: teams file, label, assign, and prioritize issues, link them to merge requests and milestones, and manage work on boards, all inside the instance that also hosts their source code and CI/CD pipelines.

• Connects via a personal access token (PAT), typically from a dedicated service account, since self-managed GitLab isn't reachable through the OAuth flow used for GitLab.com. If the instance sits behind a firewall, Aikido connects through the Aikido Broker instead.
• Push Aikido findings into GitLab as issues either manually, per finding, from the Aikido feed, or automatically via scheduled bulk creation.
• Autocreation is configurable: severity threshold (Low through Critical), issue type (SCA, SAST, Secrets, Cloud, IaC, Malware, License), a daily ticket cap (25 by default), and scope by group, team, or repository.
• Each GitLab issue created this way is linked back to the source finding under the Aikido Issue Detail's Tasks tab, and Aikido can auto-close it once the underlying vulnerability is resolved.