GitLab
about.gitlab.com · Dev tools · watching since Aug 17, 2026 · RSS
Current state
As of Aug 22, 2026GitLab offers Free, Premium ($29/user/month billed annually), and Ultimate (custom pricing) plans across GitLab.com, Self Managed, and Dedicated deployment models. AI features are accessed via GitLab Credits, sold at $1/credit, with Premium and Ultimate including 12 and 24 credits/user/month respectively as a limited-time promotion. Additional add-ons include Compute Minutes ($10/1,000 minutes), Storage ($5/month per 10GiB, billed annually), and Enterprise Agile Planning ($15/user/month, Ultimate only).
| Plan | Price | Includes |
|---|---|---|
| Free | $0 per user / month | 5 users per top-level group · 400 compute minutes per month · 10 GiB adjustable storage · Static Application Security Testing · No credit card required |
| Premium | $29 per user / month | Billed annually · Unlimited licensed users · 10,000 compute minutes per month · $12 included GitLab Credits per user/month · Advanced CI/CD, SLA Management, Priority Support |
| Ultimate | — | Custom pricing, contact sales · Unlimited guest users · 50,000 compute minutes per month · $24 included GitLab Credits per user/month · Application Security Testing, Compliance and Governance |
| GitLab Dedicated | — | Single-tenant SaaS fully managed by GitLab · Data residency in region of choice · Full data and source code isolation · Bring your own key encryption · Includes everything from Ultimate |
| GitLab Dedicated for Government | — | FedRAMP compliant infrastructure · GovRAMP authorized · Deployed on AWS GovCloud · 50,000 compute minutes per month · Unlimited guest users |
Free tier Free plan: $0 per user/month, 5 users per top-level group, 400 compute minutes/month, 10 GiB adjustable storage, no credit card required.
Changes
This is the Competitor pricing pack running on a real vendor.
Current state
As of Aug 17, 2026This GitLab page lists REST API deprecations to be replaced in a future v5 REST API, though no v5 development is currently active. GitLab follows semantic versioning for the REST API and recommends migrating to new fields/endpoints noted for each deprecated item.
Deprecations
- No date
geo_nodes API endpoints
→ geo_sites
- No date
merged_by field in merge request API
→ merge_user field
- No date
merge_status field in merge request API
→ detailed_merge_status field
- No date
null value for private_profile attribute in user API
- No date
single merge request changes API endpoint
→ list merge request diffs endpoint
- No date
managed licenses API endpoint
→ License Approval policy feature
- No date
approvers and approver_group fields in merge request approval API
→ endpoint to list all approval rules for a merge request
- No date
active identifier for runners (REST/GraphQL API)
→ paused property
- No date
runner status returning paused or active
→ paused boolean attribute
- No date
ip_address field for Runners API
- No date
default_branch_protection API field
→ default_branch_protection_defaults field
- No date
require_password_to_approve API field
→ require_reauthentication_to_approve field
- No date
pull mirroring configuration with the Projects API endpoint
→ projects/:id/mirror/pull endpoint
- No date
restrict_user_defined_variables parameter in Projects API
→ ci_pipeline_variables_minimum_override_role
- No date
namespace parameter in project import and export API
→ namespace_id and namespace_path parameters
Latest entries
- Non-numeric IDs on integer path parameters return 400 bad requestbreaking
- Namespace parameter in project import API endpoints deprecated in GitLab 18.7deprecation
- Restrict_user_defined_variables parameter in Projects API deprecated in GitLab 17.7deprecation
- Pull mirroring configuration with the Projects API endpoint deprecated in GitLab 17.6deprecation
- Runner will not return ip_address starting GitLab 17.0breaking
- Default_branch_protection API field deprecated in GitLab 17.0deprecation
- Require_password_to_approve API field deprecated in GitLab 16.9deprecation
- Runner usage of active replaced by paused in GitLab 16.0breaking
- Runner status will not return paused in a future v5 REST APIbreaking
- Geo_nodes API endpoints deprecated in favor of geo_sitesbreaking
- Merged_by API field deprecated in favor of merge_user fieldbreaking
- Merge_status API field deprecated in favor of detailed_merge_status fieldbreaking
Changes
No qualifying changes since Aug 17, 2026. The page itself hasn't changed either. Last checked 1 d ago.
This is the Product and API pack running on a real vendor.
Current state
As of Aug 17, 2026GitLab's subprocessor list includes GitLab Affiliates providing 'Support Services' across 13 countries, 17 Third Party Sub-processors (e.g., Google LLC, Amazon Web Services Inc., Zendesk Inc., Anthropic PBC, OpenAI LLC, ClickHouse Inc.) for services like Cloud Hosting, AI-Powered Product Features, and Customer Support, and numerous Professional Services Sub-processors that apply only under a Professional Services Agreement. No specific transfer mechanisms (e.g., SCCs) or a 'last updated' date are stated on the page. Users can sign up to be notified of changes to the list.
- Regions
- Netherlands, United Kingdom, Ireland, Germany, France, Australia, Canada, Japan, South Korea, Singapore, Spain, India, United States, European Union
Changes
No qualifying changes since Aug 17, 2026. The page itself hasn't changed either. Last checked 1 d ago.
This is the Vendor and legal pack running on a real vendor.
Watch GitLab — or anything else — your way.
Your own prompt, cadence and channels. One alert with the before/after proof when your sentence comes true.