Your Dutch GitLab Partner
SUE is a GitLab partner in the Netherlands. We help you choose between GitLab.com, self-managed, and Dedicated, migrate your pipelines and repositories to GitLab, and manage your GitLab environment in the cloud of your choice or in your own data center.
Our GitLab Services
SUE has been providing Infrastructure & Operations services since 1997 and builds GitLab platforms that your developers use every day and that your security team can monitor. You choose where GitLab runs: in your own data center, on AWS, Azure, or Google Cloud, or as GitLab Dedicated.
01
DevOps Assessment & Licensing Advice
We'll assess your current toolchain and pipelines and recommend which GitLab tier (Free, Premium, or Ultimate) and which deployment model best suits your teams and compliance requirements.
02
Implementation & migration
We install self-managed GitLab and migrate repositories, merge requests, and pipelines from Jenkins, GitHub, or Bitbucket, one team at a time.
03
Platform Engineering & DevSecOps
We build reusable CI/CD templates, connect Kubernetes clusters via the GitLab agent and Flux, and enable security scanning and approval policies by default in every pipeline.
04
Managed Services
With Managed GitLab, we handle upgrades, patches, backups, monitoring, and runner management—whether in your private cloud or on AWS, Azure, or GCP.
05
Support
Need GitLab support right now?
Is a pipeline stuck, has an upgrade failed, or are your runners not working? Contact us, and a GitLab-certified SUE engineer will help you troubleshoot the issue.
Request supportGitLab Content Expert
Together with GitLab, we share analyst reports and blog posts about migration, GitLab Duo, and compliance. If there’s a topic you’d like to see covered, please let us know via the contact form.
"With GitLab, we streamline development so you can build, test, and deploy faster— all in one place."
GitLab Use Cases
01
Migrating to GitLab from Jenkins, GitHub, or Bitbucket
Common Migration Challenges
Jenkins servers with hundreds of plugins that no one dares to upgrade anymore, and Jira and Confluence Data Center, which will reach end of life on March 28, 2029. As a result, teams work in disparate tools, and every pipeline is custom-built.
Migrate your pipelines and repositories to GitLab
We’ll start by taking inventory of repositories, pipelines, and plugins, and select a migration path for each team. We’ll convert Jenkinsfiles using the “Convert to GitLab CI/CD Flow” feature (generally available since GitLab 18.8) and a manual review. We’ll migrate repositories and pull requests using GitLab’s importers for Bitbucket Server and GitHub. Jenkins and GitLab will run side by side temporarily, allowing each team to make the switch gradually.
Advantages
One place for code, CI/CD, issues, and security. Fewer plugins to patch and a migration at your own pace.
02
Sovereign GitLab Self-Managed and GitLab Duo on Your Own Infrastructure
Common Challenges to Sovereignty
Financial institutions, healthcare organizations, and software companies with strict customer requirements want to keep source code and AI prompts under their own control, while GitHub is migrating its platform to Azure and GitHub Copilot operates exclusively from the cloud. A public SaaS service often does not align with their risk profile.
Bring GitLab and AI to Your Own Environment
We install self-managed GitLab in your own data center or in a Dutch or EU cloud region. For AI, we integrate the GitLab Duo Agent Platform Self-Hosted with open models such as Mistral and Devstral 2 via vLLM—completely offline, if desired. With Managed GitLab, we then keep the platform up to date.
Advantages
You remain in control of your code and data, and you choose which model to use. Agentic AI for your developers—without any code leaving your environment.
03
DevSecOps and Compliance with NIS2 and the Cyber Resilience Act
Common Compliance Challenges
Since September 11, 2026, manufacturers of products with digital components have been required to report actively exploited vulnerabilities within 24 hours under the Cyber Resilience Act. NIS2 requires demonstrable control over your software supply chain, whereas security scans are currently often run separately from the pipeline.
Build compliance into your GitLab pipelines
We set up GitLab Ultimate with SAST, dependency scanning, container scanning, and secret detection in central CI/CD templates and enforce them using merge request approval policies. For each release, you generate a CycloneDX SBOM from the Dependency List and stream audit events to your SIEM.
Advantages
You can identify vulnerabilities in the merge request before they go into production. Auditors receive evidence from a single system.
The IT challenges
Many software teams use a mix of Jenkins, GitHub Actions, Bitbucket, and standalone security tools, each with its own management and permissions. At the same time, there are fixed deadlines: the CRA reporting requirement has been in effect since September 11, 2026; NIS2 and DORA require demonstrable control over your software supply chain; and Atlassian will discontinue Jira and Confluence Data Center on March 28, 2029. On top of that, you want to use AI assistants without entrusting your source code to a third party.
How GitLab Helps
- One DevSecOps platform: GitLab combines source code management, CI/CD, security scanning, and planning into a single application and, in June 2026, was named a Leader in the Gartner Magic Quadrant for DevSecOps Platforms for the fourth consecutive year.
- Deployment options: You can run GitLab as GitLab.com, as a single-tenant GitLab Dedicated instance in an EU region, or as a self-managed instance in your own data center—including air-gapped environments.
- Agentic AI in the lifecycle: The GitLab Duo Agent Platform (GA since January 2026) offers agents for planning, code review, security analysis and pipeline execution, with self-hosted models for self-managed environments.
Partner with SUE for your GitLab implementation
- Certified engineers: You'll work with GitLab-certified engineers from SUE.
- Kubernetes and the Cloud: We integrate GitLab with your Kubernetes clusters on AWS, Azure, GCP, or in your own data center, leveraging the expertise from our Managed Kubernetes service.
- Migration Step by Step: We’re migrating one team and one pipeline at a time, with a clear schedule and without a “big bang.”
- Managed GitLab: After going live, we’ll handle upgrades, patches, backups, and monitoring so your teams are working on the latest GitLab release.
Frequently asked questions
All frequently asked questionsStart by taking inventory of your Jenkinsfiles, shared libraries, and plugins, and select a few representative pipelines as a pilot. The "Convert to GitLab CI/CD Flow" feature in the GitLab Duo Agent Platform converts Jenkins syntax to GitLab CI/CD YAML and creates a merge request for it. SUE reviews and standardizes that output into reusable templates, so you can then migrate on a team-by-team basis.
Atlassian will discontinue Jira and Confluence Data Center on March 28, 2029; starting March 30, 2026, new customers will no longer be able to purchase Data Center subscriptions. Bitbucket and Bamboo Data Center are not subject to this end date and will remain available through a Bitbucket Hybrid License. If you still want to move to a single platform for code, CI/CD, and issues, GitLab’s Bitbucket Server importer will migrate your repositories, pull requests, and comments.
GitLab.com is a multi-tenant SaaS solution that requires the least amount of management. GitLab Dedicated is a single-tenant SaaS solution where GitLab manages the platform for you on AWS in a region of your choice, with BYOK and a monthly update to the N-1 release. With the self-managed option, you run the platform yourself or have SUE manage it for you, in your own data center or cloud. This is also the option for air-gapped environments.
Yes. With GitLab Duo Agent Platform Self-Hosted, you can run models on your own infrastructure; since GitLab 19.0, this also includes open models such as Mistral Devstral 2 and GLM-5.1 via vLLM. With an offline license, this works entirely without an internet connection.
Yes. With Managed GitLab, SUE handles upgrades, patches, backups, monitoring, and runner management—whether in your own data center or on AWS, Azure, or Google Cloud. GitLab releases a new version every month, and we schedule the upgrades so they don’t disrupt your teams. You retain control over access, data, and configuration.
Choose an experienced GitLab partner
Choose an experienced GitLab partner
* required