Originally reported by SD Times. Original GitLab announcement attributed to co-founder and CEO Sid Sijbrandij.
GitLab Opens Up 18 Features Across the DevOps Lifecycle
GitLab announced that 18 features previously restricted to paid tiers are moving to its open-source Community Edition (CE). The move spans the full DevOps lifecycle — from planning and code creation through to deployment, security, and package management.
“This marks a major milestone in our efforts to empower the community to collaborate more robustly and to take our single tool for the DevOps lifecycle to the next level,” wrote Sid Sijbrandij, co-founder and CEO of GitLab, in a company blog post at the time of the announcement.
The migration of code to the open-source portion of the GitLab codebase was tracked through individual issues linked from the official GitLab blog post.
The Full List of 18 Open-Sourced Features
The newly open-sourced features cover seven lifecycle stages: planning, creating, verifying, packaging, releasing, configuring, and defending. Here is the complete list:
Planning & Issue Management
- Related issues — Connect related GitLab issues together to track dependencies and cross-linked work.
- Export issues as CSV — Export issues from a GitLab project as a CSV file, delivered as an email attachment to your default notification address.
- Issue board focus mode — A distraction-free view for working within GitLab issue boards.
- Service desk — Allow external users to submit support tickets directly into GitLab issues via email, without needing a GitLab account.
Creating & Web IDE Enhancements
- Web Terminal for Web IDE — Integrates a terminal directly into the GitLab Web IDE, making it faster and easier to contribute changes to projects without leaving the browser.
- File syncing to the web terminal — Enables users to sync files from the Web IDE to a preconfigured terminal environment for in-browser code testing.
- Design Management — Allows design assets to be uploaded directly to GitLab issues, keeping designs, discussions, and implementation work in one place as a single source of truth.
Verifying
- Code quality — Automated code quality analysis integrated into merge requests, surfacing regressions before code is merged.
Packaging
- Conan (C/C++) repository — A built-in package registry for C and C++ projects using the Conan package manager.
- Maven (Java) repository — A built-in Maven repository for Java projects.
- NPM (Node.js) registry — A private NPM registry hosted within GitLab for Node.js packages.
- NuGet (.NET) repository — A built-in NuGet feed for .NET projects.
Releasing & Deploying
- Canary deployments — Route a subset of traffic to a new version of an application to test in production before a full rollout.
- Incremental rollout — Gradually deploy new versions of an application to a percentage of Kubernetes pods.
- Feature flags — Control the rollout of new features in production without requiring a new deployment.
- Deploy boards — Visualize the current state of a Kubernetes environment directly within GitLab CI/CD pipelines.
Configuring & Securing
- Support for multiple Kubernetes clusters — Connect more than one Kubernetes cluster to a single GitLab project or group, enabling environment-specific cluster configurations.
- Network policies for container network security — Define and enforce network policies to control traffic between containers and protect running workloads.
Why This Matters for DevOps Teams
For teams running self-managed GitLab CE instances, this release significantly closes the gap between the free and paid tiers. Capabilities that previously required an Enterprise Edition licence — such as feature flags, canary deployments, multi-cluster Kubernetes support, and built-in package registries — became available to all open-source users.
The package registry additions are particularly valuable for organisations managing internal dependencies across multiple languages. Having Conan, Maven, NPM, and NuGet registries within the same platform that hosts source code and CI/CD pipelines reduces the need for separate Artifactory or Nexus installations for smaller teams.
Design Management addresses a common workflow gap: design assets are frequently stored in Figma, Zeplin, or shared drives, disconnected from the issues that track their implementation. Moving them into GitLab issues creates a tighter feedback loop between designers and engineers.
“From design management to package managers, managing multiple Kubernetes clusters to connecting related issues, we’re making it easier than ever for an individual contributor to have everything they need to plan, build, deploy, and secure their application with GitLab,” Sijbrandij wrote.
Context: GitLab’s Open Core Model
GitLab operates on an open-core model, maintaining a Community Edition (CE) under an MIT licence and an Enterprise Edition (EE) with additional paid features. Periodically, the company moves features from EE down to CE as those features mature or as community demand grows. This announcement represented one of the larger single batches of such migrations.
Teams evaluating GitLab CE versus GitHub, Gitea, or other self-hosted options should review the current GitLab CE feature list directly on the GitLab website, as the feature set continues to evolve with each release.