Skip to content
Back
PRICING BRIEFINGDaily · Oct 16, 2026
GGitLab
GitLab
PACKAGING CHANGE

GitLab brings Secrets Manager to Self-Managed, Dedicated still pending

GitLab's Secrets Manager, a centralized service for storing, controlling access to and rotating credentials, was marked "New" and available for Premium and Ultimate plans.

GitLab’s pricing page · Change Detected

WHY IT MATTERS

Self-Managed customers, often in regulated or air-gapped environments, now get native credential management without waiting on GitLab.com feature parity to trickle down — one less reason to run a third-party secrets vault alongside GitLab. But Dedicated accounts, typically GitLab's highest-compliance customers, are the ones most likely to need this and are the ones still waiting. Watch whether Dedicated gets Secrets Manager within GitLab's usual ~52-day change cadence, or whether it lags further behind.

BY THE NUMBERS

  • GitLab has made 10 real pricing changes since tracking began Apr 11, 2025
  • 28 days since the previous change (Sep 18, 2026 credits rename)
  • Faster than GitLab's typical ~52-day gap between changes
  • Feature changes make up 9 of GitLab's 24 tracked events

THEIR RATIONALE

GitLab is rolling Secrets Manager out deployment tier by deployment tier rather than shipping it everywhere at once — GitLab.com first, Self-Managed next, Dedicated still to come. That staged approach matches the company's recent cadence: it moved just 28 days after renaming Flex per-use credits to "on-demand" and dropping overage discounts, faster than its typical 52-day gap between changes, and follows a year of incremental platform additions like adding Claude Code and Codex to Duo Agent Platform in March.

TRACK RECORD10 changes since Apr 11, 20258 in the last 12 monthsa change every ~52 daysprevious change Sep 18, 2026 (28 days ago)

THE SIGNAL

This is a capability-parity move more than a packaging one: GitLab isn't changing what Secrets Manager costs or who can buy it, it's closing the gap between what GitLab.com customers get and what self-hosted customers get. Feature-level changes like this are GitLab's single most common type of pricing-page move — 9 of its 24 tracked events — and a routine category across the whole index, accounting for about 11.7% of the 1,720 pricing changes tracked in the last six months. The more telling fact is what's still missing: Dedicated, the tier aimed at GitLab's largest and most regulated customers, doesn't have it yet.

FEATURE CHANGES173 companies in the last 6 months11.7% of 1,720 tracked changes5× on GitLab's pagePerplexity most often (6)

IN CONTEXT

Secrets Manager first appeared on GitLab's pricing page as a 'New' card limited to GitLab.com; this update extends it to Self-Managed and leaves Dedicated as the remaining gap. GitLab has made 10 real pricing-page changes since tracking began in April 2025, and this one landed just 28 days after it renamed Flex per-use credits to on-demand and dropped overage discounts — faster than its typical 52-day cadence. The company has spent 2026 shipping access in stages, from unifying Flex Commitment billing in June to adding Claude Code and Codex to Duo Agent Platform in March. Feature changes are GitLab's most common move (9 of 24 tracked events) and a routine category index-wide — about 11.7% of 1,720 changes tracked in six months. The open question is when Dedicated catches up.

WHAT PEOPLE ARE SAYING

@multilayertwitter

GitLab 19.5で、GitLab Secrets Managerが一般提供になった(米国時間10/15)。対象はhttps://about.gitlab.com/ Dedicatedにも近く対応するとのこと。 OpenBaoをベースに作られていて、ビルドで使う認証情報も実行時に使う認証情報も、コードと同じ権限と監査ログの仕組みで管理できる。 .gitlab-ci.ymlのsecrets:キーワードで必要なシークレットを宣言したジョブにだけ、値が渡される。保護ブランチで、なおかつproduction/*の環境に向けたジョブにだけ渡す、といった条件も組み合わせられる。 値は一時ファイルに書き込まれて、ジョブにはそのパスだけが渡る。ログではマスクされ、ジョブが終わると破棄される。読み取りのたびにパイプラインとジョブのIDが監査イベントに記録される。 今までCI/CD変数に入れていた署名鍵などを必要なジョブだけに絞れるので、依存パッケージが乗っ取られたときでも、漏れる範囲をそのジョブが読めたシークレットまでに抑えられる。別にVaultを立てて権限を二重に管理する手間も減る。 #GitLab #DevSecOps #CI/CD #セキュリティ

View original