Getting Started with Software
Getting Started with WX-ONE Software
Four steps take you from choosing a plan to running your first production CI/CD pipeline on your managed GitLab environment.
Steps for WX1 software
Step 1: Choose and Order Your Plan
Compare the three service tiers and pick the one that fits your team.
- Startup – 99% availability, support on business days from 8:00 AM to 5:00 PM, ideal for small teams and MVP projects.
- Professional – 99.9% availability, support on business days from 8:00 AM to 5:00 PM, for growing engineering organizations.
- Enterprise – 99.9% availability with round-the-clock 24/7 support for mission-critical workloads.
Billing is transparent and monthly. Once you order, we provision your managed GitLab instance in our data centers in Germany.
Step 2: Take Over Your Environment and Set Up Access
As soon as your instance is live, you receive your administrator credentials.
- Sign in to the web interface and define your first administrator group.
- Configure single sign-on or your preferred authentication provider.
- Enforce two-factor authentication as a mandatory requirement for all members.
We handle platform operations, patching, and security hardening for you, so you can focus on your projects.
Step 3: Create Projects, Groups, and Teams
Structure your work through groups and repositories.
- Create groups for departments or products, with individual project repositories underneath.
- Invite team members and assign role-based permissions from guest to maintainer.
- Import existing repositories via git push or the built-in importer.
This cleanly mirrors your organizational structure in the platform and keeps access control fully in view at all times.
Step 4: Configure and Roll Out CI/CD Pipelines
Automate testing, security scanning, and deployments directly from your repositories.
- Add a pipeline definition to your repository to trigger builds on every commit.
- Register runners to execute your jobs.
- Add automated test and security stages plus approvals for production deployments.
With every change, your code runs through reproducible, auditable pipelines for faster and safer releases.


