Originally reported by DevOps.com. Original announcement date: April 2020.
GitLab Opens Up 18 Features to the Free Core Tier
GitLab announced that it was moving 18 features — previously only available to paying subscribers — into the free, open source Core tier of its DevOps platform. The move affects capabilities spanning the full software development lifecycle, from project planning and code creation through to deployment, configuration, and security.
Scott Williamson, then Executive Vice President of Product Management at GitLab, explained that the company organizes DevOps tooling across four service tiers. The newly liberated features were distributed across seven stages of the GitLab DevOps lifecycle.
Which Features Moved to Core?
The 18 features migrated to the Core (free, open source) tier were organized by DevOps stage:
Plan
- Related Issues — link issues to surface dependencies and relationships between work items.
- Export Issues — export issue lists for reporting and offline analysis.
- Issue Board Focus Mode — a distraction-free view for working with issue boards.
- Service Desk — allow external users to submit support requests directly as GitLab issues via email.
Create
- Web Terminal for Web IDE — run a terminal session directly within the browser-based IDE.
- File Syncing to Web Terminal — sync local file changes to the web terminal environment.
- Design Management — upload, version, and discuss design files alongside code and issues.
Verify
- Code Quality Reports on Merge Requests — surface code quality regressions and improvements directly in merge request diffs.
Package
- Package Manager Support — a unified package registry supporting multiple package manager formats (such as npm, Maven, and others) within a single interface.
Release
- Canary Deployments — route a subset of traffic to a new version before full rollout.
- Incremental Rollout — gradually roll out changes to a percentage of your fleet.
- Feature Flags — enable or disable features at runtime without redeploying code.
- Deploy Boards — visualize the real-time deployment status of pods across Kubernetes environments.
Configure
- Multiple Kubernetes Cluster Support — connect and manage more than one Kubernetes cluster per project or group, simplifying multi-environment deployments.
Defend
- Network Policies for Container Network Security — define and enforce network-level security policies for containerized workloads.
Why GitLab Made the Move
Williamson noted that the majority of GitLab’s customer base historically begins with the open source Core tier before upgrading to a paid plan. Making higher-tier features available for free lowers the barrier to adoption and lets teams experience the platform’s full lifecycle coverage earlier in their evaluation.
The announcement was also made against the backdrop of broader economic uncertainty in early 2020. GitLab acknowledged that organizations under budget pressure often lean more heavily on open source tooling — reducing licensing costs while retaining engineering talent to manage and customize their platforms.
Context: Remote DevOps and Platform Strategy
GitLab has long emphasized its suitability for distributed, remote teams — a design philosophy that predates widespread remote work adoption. The platform’s single-application approach (one codebase covering the entire DevOps lifecycle from planning to monitoring) means teams can collaborate asynchronously across plan, code, build, test, deploy, and monitor stages without stitching together multiple tools.
Williamson highlighted that for teams reconsidering how they allocate infrastructure resources, GitLab’s SaaS offering (GitLab.com) provides an alternative to self-managing the platform — allowing engineering capacity to focus on writing and shipping code rather than operating DevOps infrastructure.
What This Means for Teams Evaluating GitLab
For teams currently on the Core tier, these additions are immediately actionable. Key features worth evaluating for immediate value include:
- Service Desk — useful for teams that handle internal or external support workflows alongside their development process.
- Feature Flags — enables safer deployments and experimentation without coordinating full releases.
- Canary Deployments and Deploy Boards — critical for teams running Kubernetes-based workloads who want progressive delivery without a paid tier.
- Design Management — relevant for product teams that want to keep design assets versioned and linked to code changes.
- Code Quality Reports — a lightweight way to enforce code quality gates within an existing CI pipeline.
Teams already using competing CI/CD platforms or assembling their own toolchains from open source components may find this consolidation of features into a single free platform compelling — particularly if Kubernetes-native deployment workflows are already part of their stack.
For the latest information on GitLab’s tier structure and feature availability, refer to the official GitLab pricing and feature comparison page.