Getting Started with Gitlab
Getting Started with WX-ONE GitLab as a Service
Get your managed GitLab instance productive in a few steps—from provisioning and importing your repositories to CI/CD runners and single sign-on.
Steps for WX1 gitlab
Step 1: Order your instance and choose an edition
Pick the service edition that matches your availability needs: StartUp with a 99% business-hours SLA for testing and small teams, Professional with a 99.9% SLA and a redundant setup, or Enterprise with a 99.9% SLA around the clock, including security monitoring and hardening.
Once ordered, our team provisions your dedicated GitLab instance in a GDPR-compliant, ISO 27001:2022 certified WX-ONE data center in Germany. You receive a ready-to-use environment including backups, monitoring, and the GitLab license tier you need (Open Source, Premium, or Ultimate).
Step 2: Add users, groups, and single sign-on
Structure your organization with groups and subgroups, and assign permissions through role-based access control—from Guest all the way to Owner.
Connect your existing identity provider via single sign-on. Common methods such as SAML, OpenID Connect, and LDAP are supported, so your teams log in with their existing corporate accounts. Optionally enforce two-factor authentication for an extra layer of security.
Step 3: Import your repositories
Bring your existing source code across without losing history. GitLab imports repositories directly from other Git platforms or from any Git remote via URL.
- Move entire groups or individual projects, including branches and tags
- Migrate issues, merge requests, and wikis where the source supports it
- Cleanly re-map access rights afterwards through group roles
Our support team assists with larger migrations and verifies that the imported data is complete.
Step 4: Set up CI/CD runners and launch a pipeline
Add a .gitlab-ci.yml to the root of your project to define your first pipeline. Then register one or more GitLab Runners to execute your build, test, and deploy jobs.
- Connect runners using your instance's registration token
- Store container images in the built-in Container Registry
- Wire security scans such as SAST and DAST directly into the pipeline
Once your first pipeline turns green, your DevSecOps workflow is live—while we handle operations, updates, and scaling for you.


