# GitLab messaging framework: a completed example

Rainbrand filled in its messaging framework template for GitLab on November 16, 2026, using only GitLab's public website, press releases, brand guidelines and handbook. GitLab's internal framework may say more or differ. Text in quotation marks is GitLab's wording; the rest is our summary of it. Anything GitLab doesn't publish is marked **Not published**, where an internal framework would have an answer.

| | |
| --- | --- |
| Owner | GitLab's handbook files its messaging pages under Product and Solution Marketing. This example: the Rainbrand blog. |
| Last reviewed | November 16, 2026 |
| Version | Example 1 |
| Related | Voice: design.gitlab.com, Brand voice (last updated November 2, 2026). Visual guidelines: design.gitlab.com. Trademark guidelines: GitLab handbook. |

## 1. Positioning

_Who the brand is for, what it is, and why someone would choose it over the alternative. Say who it is not for._

For engineering organizations scaling AI agents across software delivery that won't trade speed for control, GitLab is the intelligent orchestration platform for DevSecOps, where teams and their AI agents plan, build, secure and ship software in one place. Unlike a separate tool for each stage, where context is lost between systems, GitLab's planning, source control, CI/CD and security share one data model, and the same policies and approvals apply to changes made by people and by agents.

Sources: the homepage ("the intelligent orchestration platform for teams that won't compromise on speed or control as they scale agentic software engineering"; "Policies, approvals, and scanning apply to human and agent changes alike"), the company page ("the intelligent orchestration platform where teams and their AI agents ship secure software faster") and Why GitLab ("Unlike fragmented toolchains where context is lost across disconnected systems").

Not for: **Not published.**

Based on: GitLab's handbook messaging page lists the customer problems its messaging starts from: a different tool for each team or person, many integrations and configurations, no common metrics, slow handoffs, security reviews that block releases, and build, QA, security and operations teams working in silos. Its customer stories describe the alternative in customers' own terms: Lockheed Martin's lists ClearCase, Jenkins, Dimensions, Redmine and Bitbucket, with each program running its own toolchain. The interviews, sales calls and win and loss reviews behind these choices are **Not published**.

## 2. Value proposition

_The same promise at three lengths, so nobody has to shorten it themselves._

- Under 10 words: "Speed you can trust, all the way to production." (homepage headline). The same page also uses "Ship faster. Stay in control."
- One sentence: "GitLab is the intelligent orchestration platform for teams that won't compromise on speed or control as they scale agentic software engineering." (homepage)
- About 50 words: the press release boilerplate in section 8.

Earlier wording: the handbook messaging page, last modified August 27, 2026, gives the value proposition as "GitLab is The DevOps platform" and longer versions of that sentence. The website, company page and press releases use the newer category name, "intelligent orchestration platform", so this example uses that. See section 10.

## 3. Audiences

_One row per audience you write for. What they are trying to do, what they use today, and what they need to hear first._

| Audience | Trying to | Uses today | Needs to hear | Best proof |
| --- | --- | --- | --- | --- |
| Engineering executives: the handbook's Erin, Application Development Executive, and Kennedy, Infrastructure Engineering Director | Ship faster as teams add AI agents, without losing control of what reaches production | A separate tool for planning, source control, CI and security, joined by custom integrations | One platform where people and agents work under the same gates | Lockheed Martin story; Fortune 100 figure, with its footnote |
| Security and compliance leads | Apply the same policies to every change and show auditors the evidence | Scanners and approvals that sit beside the pipeline and run late | "Scanning, policies, and approvals run inside the pipeline, not beside it"; "Every agent action shows up in the audit trail" | The scanners listed on Why GitLab; deployment options; the training policy for customer code |
| Development team leads and DevOps engineers: the handbook's Delaney and Devon | Get feedback on each commit and stop switching between tools | Several tools, logins and handoffs | Code, merge requests, pipelines and security findings in one place | Lockheed Martin build times |

Sources: the handbook's DevOps Platform message house has separate one-sentence value propositions for business and technology leaders and for engineers, and one-line pitches for each persona in small, mid-sized and enterprise companies. The audience rows above keep those personas and update what they need to hear to the current website.

## 4. Message pillars

_Two to four themes that support the value proposition. Each has one message and the proof for it._

| Pillar | Message | Proof | Use for |
| --- | --- | --- | --- |
| AI orchestration | "Define how teams and AI agents work together": teams orchestrate and agents execute, inside the guardrails the team sets | GitLab Duo Agent Platform; GitLab 19.5 lets teams "Connect any MCP-compatible agent to GitLab" | Engineering executives; launches |
| One platform, one source of context | "Planning, source control, and CI/CD in one platform", sharing one data plane, so people and agents work from the same source | Lockheed Martin: "80x faster CI pipeline builds" and thousands of Jenkins servers retired; GitLab Orbit, a context graph for the software lifecycle, generally available since October 29, 2026 | Engineering executives; developers |
| Security built in | Scanning, policies and approvals run inside the pipeline, for human and agent changes alike, and every agent action is in the audit trail | Why GitLab lists SAST, DAST, dependency scanning, secret detection, container scanning and fuzz testing, and three deployment options | Security and compliance leads; regulated industries |

## 5. Proof library

_Every fact, number, customer result or quote the copy may use, with its source and the date it was last checked. Copy may make only claims listed here._

| Claim | Evidence | Source | Checked | Approved for |
| --- | --- | --- | --- | --- |
| "More than 70 million registered users" | GitLab's own count | About GitLab boilerplate, press release of October 29, 2026 | November 16, 2026 | Press and boilerplate, with its date. The company page gives "Over 50 million" estimated registered users "as of June 2026"; the October figure is newer, so copy uses it. |
| "approximately 50% of the Fortune 100" trust GitLab | "Claim based on GitLab data"; the footnote defines the Fortune 100 as the top 20% of the 2025 Fortune 500 list | Same boilerplate | November 16, 2026 | Only with the footnote |
| Lockheed Martin: "80x faster CI pipeline builds", "1,000s of Jenkins servers retired", "90% less time spent on system maintenance" | Customer story | about.gitlab.com/customers/lockheed-martin/ (the page shows no date) | November 16, 2026 | Engineering executives; aerospace and defense. Name Lockheed Martin with each number. |
| One Department of Defense program cut build times from 12 hours to 4 hours and ran 16 builds a night instead of four | Same customer story | Same | November 16, 2026 | Developers |
| Customer code is "unused for training or fine tuning of our own models", and "Code suggestions do not use customer code" | GitLab's stated policy | Why GitLab | November 16, 2026 | Security and privacy audiences |
| Deploys "on-premises, multi-tenant SaaS, or GitLab Dedicated, our fully managed single-tenant SaaS solution" | Product fact | Why GitLab | November 16, 2026 | All |
| GitLab Orbit is generally available: it "connects code, merge requests, work items, pipelines, and vulnerabilities in a single, continuously updated view for AI agents and engineers" | Launch announcement | Press release of October 29, 2026 | November 16, 2026 | Launch and product copy |
| 177 consecutive monthly releases | Company page, figures "as of June 2026" | about.gitlab.com/company/ | November 16, 2026 | Only with its date; the number grows every month |
| "Planning, source control, and CI/CD in one platform"; "Projects, releases, and code share one data plane" | Product description | Homepage | November 16, 2026 | All; the one platform pillar |
| "Scanning, policies, and approvals run inside the pipeline, not beside it"; "Policies, approvals, and scanning apply to human and agent changes alike" | Product description | Homepage | November 16, 2026 | All; the security pillar |
| "Every agent action shows up in the audit trail" | Product description | Homepage | November 16, 2026 | Security and compliance leads; the security pillar |
| GitLab 19.5: "Connect any MCP-compatible agent to GitLab" | Release summary | Homepage, What's new | November 16, 2026 | The AI orchestration pillar |

## 6. Claim boundaries

_What the brand never says, what it says only with proof beside it, and what it can’t say yet._

- Never: "first" or "only". The handbook: "They are extremely difficult to prove with evidence so they lack credibility", and partners often ask GitLab to change that wording in joint marketing, such as press releases.
- Only with proof attached: the Fortune 100 figure, with its footnote; any speed or savings number, with the named customer story it comes from; the registered-user count, with its date and source.
- Not yet: **Not published.** An internal framework would list unannounced features and claims still waiting for evidence.

## 7. Words to use and avoid

_Product names, category terms and phrases, with the reason for each._

| Use | Instead of | Why |
| --- | --- | --- |
| "single application", "built from the ground up", "built in" | "integrated" | Handbook: a competitor whose suite is made of separate apps can claim "integrated" too |
| The platform and what it does across stages | Git and Git-only concepts | Handbook: "Git" is already in the company's name |
| "intelligent orchestration platform for DevSecOps" | "The DevOps platform" | The website, company page and press releases use the newer category name |
| "product" and "platform" | Choosing one | Handbook: GitLab is a single application you buy and use, and a platform for further use cases through its API |

Note for the owner: the Why GitLab page uses the heading "Integrated AI and multi-agent workflows across the SDLC". Say whether the rule on "integrated" covers feature headings like this one.

## 8. Approved descriptions

_Text people paste as written._

- Tagline: **Not published** as an official tagline. The homepage headline on November 16, 2026: "Speed you can trust, all the way to production."
- Boilerplate (the "About" paragraph for press releases), from the press release of October 29, 2026, used with its footnote: "GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 70 million registered users and approximately 50% of the Fortune 100* trust GitLab to ship better, more secure software faster."
- Short bio: **Not published.** The closest is the company page's first line: "We're the company behind GitLab, the intelligent orchestration platform where teams and their AI agents ship secure software faster."
- Email introduction: the handbook's standard email introduction uses the earlier category name, "The DevOps platform". **Update before reuse**, with the category name from the boilerplate.

## 9. Adapting by channel and audience

_What may change (headlines, length, examples, order of pillars) and what may not (positioning, claims, names, approved descriptions)._

- May change: headlines. The handbook: "Headlines can be more experimental, and sometimes use different words than official messaging. This is acceptable, as long as they are truthful and authentic." The homepage's industry sections also lead with a different result for each industry.
- Must stay the same: the category name, the boilerplate (as written, with its footnote) and every claim in section 5, with its source.

## 10. Ownership and changes

_Who owns the framework, what triggers a review (a launch, a pricing change, new proof, a claim that stops being true), and what changed._

Review triggers: **Not published.**

| Date | Change | Why |
| --- | --- | --- |
| August 27, 2026 | Handbook messaging page last modified, in a marketing restructure | Its value proposition uses "The DevOps platform" |
| October 29, 2026 | Press release boilerplate: "intelligent orchestration platform for DevSecOps", "More than 70 million registered users" | Latest press release on November 16, 2026 |
| November 16, 2026 | This example: assembled from the sources below; the handbook's value proposition and email introduction marked as earlier wording; two dated user counts noted | The website and press releases use the newer category name |
| November 16, 2026, after the first Brief | Added the homepage product descriptions behind the three pillars to section 5; chose the October 29 user count as current | Tracing the first channel copy showed pillar lines that section 5 didn't list yet |

## 11. Testing

_How each message was tested, with whom, what they understood and what changed. Test with people from the audiences in section 3, not with colleagues._

**Not published** by GitLab, and not done for this example: nobody from GitLab's audiences has read these messages for us. The article this file comes from describes how to run the tests.

---

## Sources (all read November 16, 2026)

- Homepage: about.gitlab.com
- Why GitLab: about.gitlab.com/why-gitlab/
- Company page: about.gitlab.com/company/
- Press release, "GitLab Orbit, Now Generally Available, Makes AI Agents More Accurate and Less Expensive to Run", October 29, 2026: about.gitlab.com/press/releases/2026-10-29-gitlab-announces-orbit-general-availability/
- Lockheed Martin customer story: about.gitlab.com/customers/lockheed-martin/
- Handbook, Product Marketing Messaging: handbook.gitlab.com/handbook/marketing/product-and-technical-marketing/product-and-solution-marketing/messaging/
- Handbook, DevOps Platform Message House: handbook.gitlab.com/handbook/marketing/product-and-technical-marketing/product-and-solution-marketing/usecase-gtm/devops-platform/message-house/
- Brand voice: design.gitlab.com/brand-messaging/brand-voice/

_From rainbrand.com/blog/brand-messaging-framework/. Quoted text comes from GitLab's public website, press releases, brand guidelines and handbook. GitLab is a trademark of GitLab Inc._
