GitLab vs Bitbucket
free-tier · subscription-per-seat · usage-based · enterprise-custom
·free-tier · subscription-per-seat · usage-based · enterprise-custom
GitLab wins · 40–18 (13 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to GitLabA probe confirms GitLab hosts a live llms.txt at docs.gitlab.com/llms.txt (HTTP 200) with structured documentation content, directly satisfying the story of pointing an agent at agent-oriented docs. This is reinforced by agent-oriented documentation like the Orbit skill for AI coding agents and MCP tool exposure. Missing for 10: independent/community corroboration that agents actually consume this llms.txt successfully in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.gitlab.com/llms.txt # GitLab Documentation Learn how to use and administer GitLab, the most scalabl…”
- [claimed-docs] “The GitLab Orbit skill gives AI coding agents structured guidance for querying the GitLab Orbit graph.”
- [claimed-docs] “GitLab Orbit exposes two MCP tools that let any MCP-compatible AI agent discover and invoke GitLab Orbit commands against your graph.”
Bitbucketnone0/10Direct probes for llms.txt, markdown docs, and OpenAPI specs all returned 404s, and no evidence shows Bitbucket/Atlassian publishing agent-oriented docs like llms.txt.
- [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to GitLabGitLab CI/CD is inherently headless automation infrastructure, with REST API for programmatic control, personal access tokens for auth, and Duo Agent Platform explicitly designed to run agents/flows within CI/CD pipelines (via 'Custom flows', 'Sessions' tracking execution) and third-party CLI agents like Kilo integrating directly into CI/CD pipelines. Missing for 10: independent hands-on validation of headless agent runs in CI, and more detail on non-interactive/unattended flow execution specifics.
- [claimed-docs] “Get started with GitLab CI/CD Build and test your application.”
- [claimed-docs] “Automate your workflows and build integrations with the GitLab REST API”
- [claimed-docs] “Custom flows are workflows you create to automate your team’s specific processes.”
- [claimed-docs] “Sessions show the status and execution data for the agents and flows you’ve run.”
- [claimed-docs] “Delegate routine tasks, from code refactoring and security scans to research, to specialized AI agents.”
- [claimed-docs] “Kilo is the open-source agentic engineering platform for GitLab. Powerful CLI and IDE agents autonomously plan, code, and verify tasks. Inte…”
- [claimed-docs] “Personal access tokens”
Bitbucket ships a native CI/CD system (Pipelines) that runs headlessly with hosted or private runners and 'no infrastructure needed,' and explicitly supports triggering AI-powered automated workflows (cleanup, docs, release notes, flaky-test fixes) from the pipeline. This directly satisfies running the product headlessly/in CI for automation. missing for 10: independent/hands-on corroboration of Pipelines reliability and any CLI-level headless invocation outside the pipeline UI.
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
- [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnGitLabnone0/10The evidence shows GitLab exposing its own functionality as an MCP server (e.g., GitLab Orbit's MCP tools, the official 'mcp_server' doc) and governance policies for tools invoked by connecting clients, but nothing documents the reverse capability—letting a user plug external third-party MCP servers into GitLab's Duo Agent Platform so its own agents/flows can call those tools. Missing for 10: documentation of adding/registering external MCP servers as tool sources for GitLab Duo agents, any UI/config for MCP server URLs within Agent Platform, and independent confirmation that GitLab agents can invoke tools from arbitrary MCP servers.
- [claimed-docs] “GitLab Orbit exposes two MCP tools that let any MCP-compatible AI agent discover and invoke GitLab Orbit commands against your graph.”
- [claimed-docs] “Configure Allow, Ask, and Deny policies for agent tools, enforced at execution time for all connecting clients.”
- [probe] “official MCP server documented at https://docs.gitlab.com/user/gitlab_duo/model_context_protocol/mcp_server/”
- [claimed-docs] “Custom agents are agents you create and configure for your team’s specific needs.”
- [claimed-docs] “Custom flows are workflows you create to automate your team’s specific processes.”
Bitbucketnone0/10The only MCP-related evidence found is Atlassian's own MCP server (bitbucket-probe-4), meaning Bitbucket exposes tools via MCP rather than allowing users to plug external MCP servers into Bitbucket so it can use their tools. No evidence shows Bitbucket/Rovo acting as an MCP client that can consume third-party MCP servers.
- [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”
- [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
ai-native userConnect an agent via an official MCP server
weight 3 · round to GitLabGitLab documents an official MCP server (gitlab-probe-2) and separately exposes MCP tools via GitLab Orbit for AI agent discovery/invocation (gitlab-docs-42), showing first-party MCP server support for connecting external agents. Missing for 10: independent/hands-on verification of the MCP server's reliability and breadth of tool coverage beyond vendor docs.
- [probe] “official MCP server documented at https://docs.gitlab.com/user/gitlab_duo/model_context_protocol/mcp_server/”
- [claimed-docs] “GitLab Orbit exposes two MCP tools that let any MCP-compatible AI agent discover and invoke GitLab Orbit commands against your graph.”
- [claimed-docs] “The GitLab Orbit skill gives AI coding agents structured guidance for querying the GitLab Orbit graph.”
There is direct evidence of an official Atlassian MCP server repository (atlassian-mcp-server), which covers Bitbucket as part of the Atlassian suite, enabling agents to connect via MCP. However, the evidence pack lacks detailed documentation on Bitbucket-specific MCP setup, tool scope, or independent hands-on confirmation. Missing for 10: first-party Bitbucket docs describing MCP server usage, independent verification of the server's functionality with Bitbucket specifically.
- [probe] “official MCP server documented at https://github.com/atlassian/atlassian-mcp-server”
ai-native userUse an official CLI
weight 2 · round to GitLabGitLab documents an official CLI (glab) at docs.gitlab.com/editor_extensions/gitlab_cli, distinct from the general REST API tooling, confirming a first-party CLI exists for interacting with GitLab. Missing for 10: no independent/hands-on corroboration of CLI usability or AI-native workflow specifics, and no detail on CLI feature completeness relative to agentic use cases.
- [probe] “official CLI documented at https://docs.gitlab.com/editor_extensions/gitlab_cli/”
- [claimed-docs] “Interact programmatically with GitLab.”
- [claimed-docs] “Automate your workflows and build integrations with the GitLab REST API”
Docs mention Rovo being accessible 'in your terminal or in your IDE,' implying some CLI-based AI access, but there's no dedicated documentation of an official Bitbucket CLI tool, its command set, or installation/usage details. missing for 10: dedicated official CLI product docs, command reference, installation instructions, independent corroboration of CLI usage.
- [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
ai-native userDrive the product through a documented public API
weight 3 · round to GitLabGitLab documents a comprehensive REST API with OpenAPI 3.0 spec, interactive docs/testing tool, versioning/deprecation policy, and clear auth via PAT/OAuth2/SSH keys, explicitly positioned for automating workflows and integrations. This is a well-established, mature public API surface that AI agents and third-party tools (e.g., Make's integration module) already use programmatically. Missing for 10: no independent hands-on developer report specifically praising/critiquing the API's ergonomics for AI-agent use cases.
- [claimed-docs] “Interact programmatically with GitLab.”
- [claimed-docs] “Automate your workflows and build integrations with the GitLab REST API”
- [claimed-docs] “You can browse and test every endpoint interactively in the [REST API documentation]”
- [claimed-docs] “Use the interactive request tool to send live requests to GitLab.”
- [claimed-docs] “GitLab supports authentication with HTTP Bearer or OAuth 2.0 credentials.”
- [claimed-docs] “Docs, "OpenAPI": "GitLab documents its REST API using the OpenAPI 3.0 specification (formerly called Swagger)... The OpenAPI spec is autogen…”
- [claimed-docs] “Docs, "REST API deprecations": "You should regularly review the following deprecations and make the recommended changes"; "GitLab will not m…”
- [claimed-docs] “Personal access tokens”
- [claimed-docs] “Make allows you to connect GitLab to more than 700 ready-made applications or to any API to integrate your DevSecOps processes and optimize …”
Bitbucketnone0/10The evidence pack contains no documentation or reference to a public Bitbucket REST/GraphQL API; the only related probes (llms.txt, docs.md, OpenAPI spec) all returned 404s, and no other citation mentions an API for programmatic control. While a documented API is a plausible axis for an SCM/CI platform, this pack provides no confirming evidence.
- [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to GitLabGitLab supports scoped Personal Access Tokens and OAuth 2.0 credentials for programmatic API access (gitlab-docs-5, gitlab-docs-22, gitlab-docs-17, gitlab-docs-32), and its AI Agent Platform governance docs explicitly describe configuring Allow/Ask/Deny policies for agent tools enforced at execution time plus session/audit monitoring (gitlab-docs-44, gitlab-docs-45), which together support least-privilege credentialing for agents. However, there is no dedicated agent-specific token type or explicit scope list tailored to agent use-cases, and no independent/hands-on corroboration of this workflow. Missing for 10: a first-party doc showing agent-specific token scopes/creation flow, and independent verification that agent credential scoping works as described.
- [claimed-docs] “Personal access tokens”
- [claimed-docs] “For `http`, enter your [personal access token](/user/profile/personal_access_tokens/).”
- [claimed-docs] “[Personal access tokens](/user/profile/personal_access_tokens/)”
- [claimed-docs] “GitLab supports authentication with HTTP Bearer or OAuth 2.0 credentials.”
- [claimed-docs] “Configure Allow, Ask, and Deny policies for agent tools, enforced at execution time for all connecting clients.”
- [claimed-docs] “Monitor AI agent sessions, audit logs, and developer exposure across a group.”
Bitbucketnone0/10Evidence shows only general workspace/repo/branch permission controls (bitbucket-docs-9) but nothing about issuing scoped or least-privilege API credentials/tokens specifically for an AI agent, such as app passwords or API token scopes tied to agent use cases.
- [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
ai-native userBuild against official SDKs
weight 2 · round to GitLabGitLab documents a way to 'Interact programmatically with GitLab' (API access) which implies SDK-style build capability, but the evidence pack never names specific official SDKs (e.g., Python/JS/Go client libraries) or documents their agentic/AI-native use cases explicitly. missing for 10: named official SDK packages/languages, documentation of AI-agent-specific SDK usage, independent developer corroboration of building against these SDKs.
- [claimed-docs] “Interact programmatically with GitLab.”
Bitbucketnone0/10The evidence pack contains no mention of official SDKs for building against Bitbucket/Atlassian APIs, and the probes explicitly show 404s for openapi/API-schema and machine-readable docs endpoints, indicating no discoverable SDK or API spec was found. Only an MCP server is documented, which addresses a different story, not SDK access.
- [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnGitLabnone0/10The evidence pack covers REST API, personal access tokens, SSH keys, MCP server, and CLI, but contains no mention of webhooks or event subscription mechanisms anywhere. Since webhook subscription is a plausible and common capability for a platform like GitLab, this is a 'none' rather than 'na', but there is simply no supporting evidence.
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to GitLabGitLab documents GitLab Duo Chat and Agent Platform features that surface AI-generated insights and suggestions directly from the product's own data — Chat has access to issues, merge requests, commits, and CI/CD pipelines and maintains context (gitlab-docs-48), can answer natural-language queries like finding relevant MRs (gitlab-docs-39), and delegates tasks like code refactoring, security scans, and research to specialized AI agents (gitlab-docs-47). Security findings and agent-driven remediation also surface directly in merge requests/IDEs (gitlab-docs-1, gitlab-docs-29). Missing for 10: independent/hands-on evidence of insight quality or accuracy, and more detail on proactive (vs. query-driven) insight generation.
- [claimed-docs] “Agents turn issues into merge requests, remediate vulnerabilities, and review code while your team stays in control.”
- [claimed-docs] “you can ask “Find the merge request about authentication” and Chat searches for relevant merge req”
- [claimed-docs] “Delegate routine tasks, from code refactoring and security scans to research, to specialized AI agents.”
- [claimed-docs] “Chat has access to your project, including issues, merge requests, commits, and CI/CD pipelines, and Chat maintains context across conversat…”
- [claimed-docs] “Discover agents and flows created by the GitLab team and community members.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform. Security findings appear directly in merge requests and I…”
Bitbucket docs claim AI code review that reviews changes and suggests fixes, plus Rovo-powered AI workflows and model access, indicating AI-generated insights/suggestions from repository data. However, these are vendor claims with no independent/hands-on corroboration, and community evidence is silent on AI features entirely. Missing for 10: independent verification of AI review quality, concrete examples of AI-generated insights in practice, and detail on how deeply Rovo integrates with actual code/data.
- [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
- [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
- [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to GitLabGitLab Duo Agent Platform explicitly supports background automation: custom flows/agents run tasks (code refactoring, security scans, research) autonomously in CI/CD pipelines, with sessions tracking execution, governance policies (Allow/Ask/Deny), and human-in-loop approval options — all first-party documented. Missing for 10: independent/hands-on evidence of these autonomous flows actually running unattended in production and more detail on triggering/scheduling mechanisms.
- [claimed-docs] “Discover agents and flows created by the GitLab team and community members.”
- [claimed-docs] “Custom agents are agents you create and configure for your team’s specific needs.”
- [claimed-docs] “Custom flows are workflows you create to automate your team’s specific processes.”
- [claimed-docs] “Sessions show the status and execution data for the agents and flows you’ve run.”
- [claimed-docs] “Human in the loop approvals for chat-based GitLab Duo Agent Platform sessions”
- [claimed-docs] “Configure Allow, Ask, and Deny policies for agent tools, enforced at execution time for all connecting clients.”
- [claimed-docs] “Monitor AI agent sessions, audit logs, and developer exposure across a group.”
- [claimed-docs] “Delegate routine tasks, from code refactoring and security scans to research, to specialized AI agents.”
- [claimed-docs] “Customize workflows for development, testing, security, and deployment. Teams orchestrate from above the lifecycle while agents execute with…”
Bitbucket documents AI-triggered pipeline automations (cleanup, docs updates, release notes, flaky test fixes) that run 'all from your pipeline,' suggesting background autonomous execution, but there is no detail on scheduling, triggers, or true autonomy without human initiation, and no independent/hands-on corroboration. Missing for 10: concrete documentation of trigger conditions/scheduling for autonomous runs, evidence of unattended multi-step agentic execution, and third-party confirmation the feature works as described.
- [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to GitLabGitLab Duo Agent Platform provides a built-in AI assistant/agent system where users can delegate tasks (code refactoring, security scans, research) to specialized agents and flows, with sessions tracking execution, human-in-the-loop approvals, and governance controls, plus Duo Chat for conversational delegation with project context. Missing for 10: independent hands-on user reports validating real-world reliability/effectiveness of the agent delegation beyond first-party docs.
- [claimed-docs] “Delegate routine tasks, from code refactoring and security scans to research, to specialized AI agents.”
- [claimed-docs] “Discover agents and flows created by the GitLab team and community members.”
- [claimed-docs] “Custom agents are agents you create and configure for your team’s specific needs.”
- [claimed-docs] “Custom flows are workflows you create to automate your team’s specific processes.”
- [claimed-docs] “Sessions show the status and execution data for the agents and flows you’ve run.”
- [claimed-docs] “You can customize the Agent Platform to match your workflow, coding standards, or project requirements.”
- [claimed-docs] “you can ask “Find the merge request about authentication” and Chat searches for relevant merge req”
- [claimed-docs] “Human in the loop approvals for chat-based GitLab Duo Agent Platform sessions”
- [claimed-docs] “Configure Allow, Ask, and Deny policies for agent tools, enforced at execution time for all connecting clients.”
- [claimed-docs] “Monitor AI agent sessions, audit logs, and developer exposure across a group.”
- [claimed-docs] “Chat has access to your project, including issues, merge requests, commits, and CI/CD pipelines, and Chat maintains context across conversat…”
- [claimed-docs] “Customize workflows for development, testing, security, and deployment. Teams orchestrate from above the lifecycle while agents execute with…”
Bitbucket docs mention built-in AI capabilities: an AI code reviewer that reviews changes and suggests fixes, AI-powered pipeline workflows to automate tasks (feature flag cleanup, docs updates, release notes, flaky test fixes), and access to Rovo AI assistant in terminal/IDE. These support delegating tasks to a built-in AI assistant, but the story's depth (e.g., detailed task delegation UX, chat-based commands) isn't well documented and there is no independent/hands-on corroboration of these AI features actually working. Missing for 10: independent verification of AI assistant behavior, deeper documentation of delegation workflow, and community evidence confirming real-world use.
- [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
- [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
- [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
ai-native userOperate the product with natural-language commands
weight 2 · round to GitLabGitLab Duo Chat and the Agent Platform let users issue natural-language requests (e.g. 'Find the merge request about authentication') that trigger context-aware search, agent delegation, and even automated MR/issue creation, backed by first-party docs on Chat context, custom agents/flows, and governance controls. Missing for 10: independent/hands-on validation of natural-language command accuracy and broader coverage showing NL control extends to all major platform actions rather than mainly chat/search and agent triggering.
- [claimed-docs] “you can ask “Find the merge request about authentication” and Chat searches for relevant merge req”
- [claimed-docs] “Delegate routine tasks, from code refactoring and security scans to research, to specialized AI agents.”
- [claimed-docs] “Chat has access to your project, including issues, merge requests, commits, and CI/CD pipelines, and Chat maintains context across conversat…”
- [claimed-docs] “Agents turn issues into merge requests, remediate vulnerabilities, and review code while your team stays in control.”
- [claimed-docs] “Custom agents are agents you create and configure for your team’s specific needs.”
- [claimed-docs] “Custom flows are workflows you create to automate your team’s specific processes.”
- [claimed-docs] “Human in the loop approvals for chat-based GitLab Duo Agent Platform sessions”
Bitbucketnone0/10Evidence shows AI code review, AI-triggered pipeline workflows, and Rovo access in terminal/IDE, but nothing indicates Bitbucket itself can be operated via natural-language commands (e.g., chat-based repo management, NL-driven PR/merge actions). Missing for 10: any documentation of natural-language command interface, conversational control of Bitbucket actions, or hands-on evidence of NL-driven operation.
- [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
- [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
- [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to GitLabGitLab documents an interactive OpenAPI-based REST API reference where users can browse and test every endpoint live, seeing the curl command, request URL, and server response, with authentication via personal access tokens or OAuth — directly matching the story of an interactive, runnable API reference. Missing for 10: independent/hands-on corroboration beyond GitLab's own docs, and no explicit AI-native framing (e.g., LLM-consumable examples) tied specifically to this reference tool.
- [claimed-docs] “You can browse and test every endpoint interactively in the [REST API documentation]”
- [claimed-docs] “Use the interactive request tool to send live requests to GitLab.”
- [claimed-docs] “GitLab supports authentication with HTTP Bearer or OAuth 2.0 credentials.”
- [claimed-docs] “For `http`, enter your [personal access token](/user/profile/personal_access_tokens/).”
- [claimed-docs] “The tool displays the `curl` command, the full request URL, and the server response.”
- [claimed-docs] “Docs, "OpenAPI": "GitLab documents its REST API using the OpenAPI 3.0 specification (formerly called Swagger)... The OpenAPI spec is autogen…”
- [claimed-docs] “You can browse and test every endpoint interactively in the REST API documentation.”
Bitbucketnone0/10No evidence of an interactive API reference or runnable examples; probes for OpenAPI/docs-md/llms.txt all returned 404s, indicating no such interactive reference is exposed.
- [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to GitLabGitLab documents its REST API using OpenAPI 3.0, autogenerated from API code, with the raw spec file available in the monorepo (openapi_v2.yaml), plus an interactive documentation viewer for browsing/testing endpoints. This directly satisfies the machine-readable API spec download story. Missing for 10: no independent/community confirmation of the spec's completeness or ease of direct download outside vendor docs.
- [claimed-docs] “Docs, "OpenAPI": "GitLab documents its REST API using the OpenAPI 3.0 specification (formerly called Swagger)... The OpenAPI spec is autogen…”
- [claimed-docs] “You can browse and test every endpoint interactively in the [REST API documentation]”
- [claimed-docs] “Use the interactive request tool to send live requests to GitLab.”
- [claimed-docs] “You can browse and test every endpoint interactively in the REST API documentation.”
Bitbucketnone0/10Probes explicitly show no OpenAPI/swagger spec found at Bitbucket's/Atlassian's support domain, and no docs evidence mentions a downloadable machine-readable API spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnGitLabnone0/10While GitLab offers CI/CD build-and-test capabilities and an AI agent governance framework (Allow/Ask/Deny policies, session monitoring, human-in-the-loop approvals), the evidence pack contains no mention of a dedicated sandbox/staging environment isolated from production data for AI agents or AI-native testing workflows. Missing for 10: explicit sandbox/staging environment documentation, evidence of production-data isolation for agent test runs, and any hands-on confirmation that AI agent testing doesn't touch production data.
- [claimed-docs] “Configure Allow, Ask, and Deny policies for agent tools, enforced at execution time for all connecting clients.”
- [claimed-docs] “Monitor AI agent sessions, audit logs, and developer exposure across a group.”
- [claimed-docs] “Human in the loop approvals for chat-based GitLab Duo Agent Platform sessions”
- [claimed-docs] “Get started with GitLab CI/CD Build and test your application.”
Bitbucketnone0/10No evidence describes a sandbox/staging environment or test-data isolation feature for AI-native testing in Bitbucket; evidence covers CI/CD, code review, permissions, and unrelated community complaints. Missing for 10: any mention of sandbox environments, ephemeral test environments, or production-data isolation for AI workflows.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to GitLabGitLab documents its REST API with OpenAPI 3.0 spec autogenerated from code, explicit versioning (v4) with semantic versioning, and a dedicated deprecations page instructing users to review and adapt to upcoming changes ahead of removal. This directly matches the story of versioned APIs with a documented deprecation policy. Missing for 10: no independent/community corroboration of how deprecation policy plays out in practice, and no explicit long-term support timeline details beyond the semantic versioning statement.
- [claimed-docs] “Docs, "OpenAPI": "GitLab documents its REST API using the OpenAPI 3.0 specification (formerly called Swagger)... The OpenAPI spec is autogen…”
- [claimed-docs] “Docs, "REST API deprecations": "You should regularly review the following deprecations and make the recommended changes"; "GitLab will not m…”
- [claimed-docs] “Automate your workflows and build integrations with the GitLab REST API”
- [claimed-docs] “You can browse and test every endpoint interactively in the [REST API documentation]”
Bitbucketnone0/10No evidence of a versioned API or documented deprecation policy; probes for OpenAPI/docs endpoints returned 404s and no mention of API versioning or deprecation exists in the evidence pack.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to GitLabGitLab's REST API and CLI expose programmatic access that lets automation manage 'CI/CD processes across multiple projects' and control access 'across your organization,' enabling scripted bulk actions, and the Duo Agent Platform can delegate routine tasks to agents across a codebase. However, there is no explicit documentation of a dedicated bulk-operations endpoint/UI (e.g., bulk-close issues, bulk-update MRs) or evidence of an agent performing large batch operations in one call. Missing for 10: explicit bulk-action API/UI documentation, hands-on evidence of bulk operations at scale, and confirmation that Duo agents can act on many items simultaneously rather than one at a time.
- [claimed-docs] “Automate your workflows and build integrations with the GitLab REST API”
- [claimed-docs] “Manage CI/CD processes across multiple projects with precision.”
- [claimed-docs] “Control user access programmatically to maintain consistent permissions across your organization.”
- [claimed-docs] “Delegate routine tasks, from code refactoring and security scans to research, to specialized AI agents.”
- [claimed-docs] “Custom flows are workflows you create to automate your team’s specific processes.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to GitLabGitLab's CI/CD pipelines are inherently event-driven (triggered by push, merge request, schedule events), and the Duo Agent Platform lets users define 'custom flows' and 'custom agents' that automate team-specific processes, with policies (Allow/Ask/Deny) governing when agent tools execute — a clear rules-on-events automation model beyond simple chat. Missing for 10: explicit documentation of rule/condition syntax (e.g., CI 'rules:' keyword, webhook trigger configuration) and independent/hands-on evidence confirming these AI Agent Platform flows work reliably in practice.
- [claimed-docs] “Custom flows are workflows you create to automate your team’s specific processes.”
- [claimed-docs] “You can customize the Agent Platform to match your workflow, coding standards, or project requirements.”
- [claimed-docs] “Delegate routine tasks, from code refactoring and security scans to research, to specialized AI agents.”
- [claimed-docs] “Configure Allow, Ask, and Deny policies for agent tools, enforced at execution time for all connecting clients.”
- [claimed-docs] “Discover agents and flows created by the GitLab team and community members.”
- [claimed-docs] “Build and test your application.”
Bitbucket supports event-driven automation via Pipelines (triggered on push/PR/tag events), merge checks/branch policies, and Jira issue auto-updates on commit events, which cover core event→action rule triggering. However there's no dedicated declarative 'rules engine' (like Jira Automation) for defining custom conditional triggers beyond CI/CD pipeline YAML and merge-check policies. Missing for 10: a first-class no-code rules/automation builder for arbitrary event-condition-action logic, and independent hands-on validation of rule reliability.
- [claimed-docs] “when you include your issue key in commits, your Jira issue statuses update automatically”
- [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
- [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnGitLabnone0/10The evidence pack covers CI/CD, agent flows, and API automation broadly, but nothing explicitly documents recurring/scheduled job triggers (e.g., pipeline schedules, cron-based automation, or recurring agent flow runs) for AI-native users.
Bitbucketnone0/10The evidence describes CI/CD pipelines, AI-triggered workflows, and merge automation, but no citation mentions scheduling recurring jobs or cron-like automation. Missing for 10: any mention of scheduled/recurring pipeline triggers, cron syntax, or automated recurring task execution.
- [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
ai-native userVersion, review, and roll back my automations
weight 1 · round to GitLabGitLab's Duo Agent Platform lets users create custom agents/flows, review execution via session logs, and enforce human-in-the-loop approvals and governance policies (audit logs, allow/ask/deny), which supports review and monitoring of automations. However, there is no explicit documentation of versioning agent/flow definitions or rolling back a previously run automation/flow to an earlier state — this is only implied by GitLab's general git-based/CI-as-code model, not stated for the Agent Platform specifically. Missing for 10: explicit version-history UI for agents/flows, a documented rollback/revert mechanism for automations, and independent evidence of this workflow in practice.
- [claimed-docs] “Custom agents are agents you create and configure for your team’s specific needs.”
- [claimed-docs] “Custom flows are workflows you create to automate your team’s specific processes.”
- [claimed-docs] “Sessions show the status and execution data for the agents and flows you’ve run.”
- [claimed-docs] “You can customize the Agent Platform to match your workflow, coding standards, or project requirements.”
- [claimed-docs] “Human in the loop approvals for chat-based GitLab Duo Agent Platform sessions”
- [claimed-docs] “Configure Allow, Ask, and Deny policies for agent tools, enforced at execution time for all connecting clients.”
- [claimed-docs] “Monitor AI agent sessions, audit logs, and developer exposure across a group.”
Bitbucket Pipelines configs live in the same git repo, so pull-request review (docs-7, docs-11) and change-management enforcement (docs-6) apply to pipeline/automation changes, and AI-powered pipeline workflows are documented (docs-4, docs-8, docs-10). However, no evidence explicitly confirms automation-specific versioning history, dedicated review flows for automation scripts, or a rollback mechanism for automations. Missing for 10: explicit documentation of automation version history/diffing, dedicated review workflow for automation changes, and an explicit rollback/undo feature for pipeline or Rovo-triggered automations.
- [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
- [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
- [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
Ci cd — continuous integration and delivery — pipelines, runners, cachingCi cd
Continuous integration and delivery — pipelines, runners, caching
Deployment
developerAutomate application deployments as part of my CI/CD pipeline
weight 2 · round to GitLabGitLab CI/CD natively supports build/test/deploy pipelines, with docs on getting started with CI/CD, deployment integrations (Pulumi push-to-deploy, env0 Terraform GitOps, Kubernetes agent for cloud-native deployment/monitoring), and multi-project pipeline orchestration via API. This is core, well-documented GitLab functionality with both first-party docs and ecosystem/partner integrations reinforcing deployment automation. Missing for 10: independent hands-on validation specifically of deployment pipeline reliability (community evidence only covers CI runner/performance issues broadly, not deployment automation itself).
- [claimed-docs] “Get started with GitLab CI/CD Build and test your application.”
- [claimed-docs] “Manage CI/CD processes across multiple projects with precision.”
- [claimed-docs] “Manage your infrastructure-as-code by using env0 with native support for GitLab. Automate your GitOps workflow to run Terraform Plan on Merg…”
- [claimed-docs] “The Pulumi integration with GitLab CI makes it easy to create and manage infrastructure stacks based on commits to specific Git branches so …”
- [claimed-docs] “You can connect your Kubernetes cluster with GitLab to deploy, manage, and monitor your cloud-native solutions.”
- [claimed-docs] “Customize workflows for development, testing, security, and deployment.”
Bitbucket Pipelines is documented as a built-in CI/CD tool for automated workflows, with deployment environments, permissions, and centralized visibility across pipeline/deployment status, supporting deployment automation as part of CI/CD. Missing for 10: hands-on/independent evidence of deployment pipeline execution, detailed deployment-specific docs (e.g., deployment triggers, rollback), and no community corroboration of deployment automation specifically.
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
- [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
- [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
devops-leadMap incidents to deployments and require change approval before releases
weight 1 · round to BitbucketGitLabnone0/10The evidence pack contains no mention of incident management, incident-to-deployment mapping, or release/change approval gates (e.g., protected environments, deployment approval rules). Only generic compliance-control and audit-evidence claims (gitlab-docs-20) appear, which do not address linking incidents to deployments or requiring approvals before releases.
Bitbucket docs explicitly state that incidents can be mapped to deployments and automated change approval processes enabled via integration with Jira Service Management, directly matching the story, and this is reinforced by merge checks/CI-CD policy enforcement features. Missing for 10: independent/hands-on verification of the incident-deployment mapping workflow beyond vendor docs.
- [claimed-docs] “Enable automated change approval processes and resolve incidents faster by mapping incidents to deployments with Bitbucket and Jira Service …”
- [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
- [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
Dev environments
developerLaunch a ready-to-code cloud-based development environment in seconds
weight 2 · round drawnGitLabnone0/10The evidence pack contains no mention of GitLab Workspaces, a Web IDE, or any other cloud-based, ready-to-code development environment feature — only CI/CD, API, security scanning, and Duo Agent Platform content, none of which addresses instant cloud dev environments. Since a DevOps platform could plausibly ship such a feature, the axis applies but is unevidenced.
Pipeline authoring
developerReuse community-built CI/CD actions or plugins in my pipelines
weight 2 · round to GitLabEvidence shows numerous third-party/partner tools that plug directly into GitLab CI/CD pipelines (Semgrep, Aqua Trivy as default scanner, DigiCert code signing, env0 Terraform, Pulumy push-to-deploy) and a community 'AI Catalog' of agents/flows built by GitLab and community members, indicating reusable pipeline integrations exist. However there's no explicit mention of GitLab's dedicated CI/CD component/action marketplace (e.g., a 'CI/CD Catalog' of reusable YAML components analogous to GitHub Actions Marketplace), so the story is only partly evidenced. Missing for 10: explicit documentation of a reusable CI/CD components/actions catalog, examples of importing a community pipeline template, and independent developer confirmation of reuse workflow.
- [claimed-docs] “Aqua Trivy is the fastest way for DevSecOps and security teams to shift left and get started with vulnerability and infrastructure as code (…”
- [claimed-docs] “DigiCert® Software Trust Manager automates code signing in GitLab CI/CD pipelines, cryptographically signing artifacts before release. Signi…”
- [claimed-docs] “Manage your infrastructure-as-code by using env0 with native support for GitLab. Automate your GitOps workflow to run Terraform Plan on Merg…”
- [claimed-docs] “The Pulumi integration with GitLab CI makes it easy to create and manage infrastructure stacks based on commits to specific Git branches so …”
- [claimed-docs] “Semgrep is a fast, open-source, static analysis tool that finds bugs and enforces code standards at editor, commit, and CI time. Precise rul…”
- [claimed-docs] “Discover agents and flows created by the GitLab team and community members.”
developerDefine CI/CD pipelines as code using a YAML syntax
weight 3 · round to BitbucketEvidence only vaguely references CI/CD capability (e.g., 'Build and test your application', 'Manage CI/CD processes across multiple projects with precision') but never explicitly confirms YAML-based pipeline definition (e.g., .gitlab-ci.yml syntax) or documents its structure. missing for 10: explicit mention of .gitlab-ci.yml YAML pipeline definition, pipeline syntax examples, and independent corroboration of YAML-as-code CI/CD authoring.
- [claimed-docs] “Build and test your application.”
- [claimed-docs] “Manage CI/CD processes across multiple projects with precision.”
- [claimed-docs] “Customize workflows for development, testing, security, and deployment.”
- [claimed-docs] “Customize workflows for development, testing, security, and deployment. Teams orchestrate from above the lifecycle while agents execute with…”
Bitbucket Pipelines is documented as the built-in CI/CD tool supporting hosted/private runners and centralized pipeline visibility, which aligns with a pipelines-as-code model, but the evidence never explicitly states the YAML file syntax (e.g., bitbucket-pipelines.yml) developers use to define pipelines. Missing for 10: explicit mention of YAML config file/syntax, example pipeline definitions, and independent hands-on confirmation of the YAML authoring experience.
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
- [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
Runners
devops-leadRun CI/CD jobs on runners hosted by the platform without managing infrastructure
weight 3 · round to BitbucketThe pack only offers a generic docs link ('Build and test your application', gitlab-docs-8) pointing to GitLab CI/CD documentation, with no specific mention of GitLab.com's SaaS-hosted shared runners or the ability to run jobs without managing infrastructure. Community evidence even highlights CI reliability problems ('CI workers did not run' gitlab-comm-1), which weakens confidence rather than confirming hosted-runner ease. Missing for 10: explicit documentation of GitLab.com shared/hosted runners, runner autoscaling, and infra-free operation, plus independent confirmation it works reliably.
- [claimed-docs] “Build and test your application.”
- [community] “GitLab's recent performance has been abysmal... we've had entire days where the team was unable to deploy because the CI workers did not run…”
Docs explicitly state Bitbucket Pipelines provides hosted runners so teams can run CI/CD workflows 'no infrastructure needed', with centralized visibility across pipelines, and also offers private runners as an alternative. Missing for 10: independent/hands-on corroboration of hosted-runner reliability or scale, and no detail on hosted runner resource limits/pricing.
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
devops-leadGet centralized visibility into CI/CD workflow runs across the organization
weight 2 · round to BitbucketEvidence shows GitLab enables cross-project CI/CD management via API (gitlab-docs-13), compliance controls and audit evidence collected 'in every pipeline' (gitlab-docs-20), and Duo Chat that has access to CI/CD pipeline context (gitlab-docs-48), suggesting some organization-wide CI/CD oversight capability. However, there is no explicit evidence of a dedicated centralized CI/CD dashboard, pipeline analytics view, or org/group-level pipeline status reporting UI. Missing for 10: a documented CI/CD dashboard or analytics view aggregating pipeline runs across projects/groups, independent/hands-on confirmation of such visibility, and detail on how audit-ready pipeline evidence is surfaced centrally.
- [claimed-docs] “Manage CI/CD processes across multiple projects with precision.”
- [claimed-docs] “Apply controls for compliance and collect audit-ready evidence automatically in every pipeline.”
- [claimed-docs] “Chat has access to your project, including issues, merge requests, commits, and CI/CD pipelines, and Chat maintains context across conversat…”
- [claimed-docs] “SAST, DAST, and compliance in every pipeline.”
Docs claim centralized visibility into pipeline status, testing policies, and deployment environments across the org via Bitbucket Pipelines (hosted/private runners), with policy enforcement across teams and repos. However, this is vendor-only marketing copy with no independent/hands-on corroboration of an actual cross-org dashboard or reporting UI, and no detail on how granular or org-wide the visibility truly is. Missing for 10: independent verification of the centralized dashboard's usability/completeness, detail on cross-project rollups, and community evidence confirming it works at scale.
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
- [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
devops-leadRun CI/CD jobs on my own self-hosted or private runners
weight 2 · round to BitbucketGitLabnone0/10The evidence pack discusses GitLab CI/CD generally (build/test, multi-project CI/CD management) and self-hosting the GitLab instance itself (Linux package, Docker images, Helm chart), but never mentions GitLab Runners, runner registration, or private/self-hosted runner configuration — the specific capability the story asks about is unevidenced here.
- [claimed-docs] “Build and test your application.”
- [claimed-docs] “Manage CI/CD processes across multiple projects with precision.”
- [claimed-docs] “The Linux package includes services and tools to install GitLab without laborious configuration.”
- [claimed-docs] “If you're using cluster management, we recommend the Helm chart or the Operator for installing cloud-native GitLab.”
- [claimed-docs] “GitLab maintains a set of official Docker images based on the Linux package.”
- [claimed-docs] “If the Linux package isn't available for your distribution, you can self-compile GitLab.”
Bitbucket docs explicitly state you can run CI/CD workflows using 'hosted or private runners—or both,' with centralized visibility, directly matching the self-hosted/private runner story, and also supports connecting to on-prem CI/CD tools like Bamboo or Jenkins. Missing for 10: independent/hands-on corroboration of private runner setup or reliability, and detail on runner configuration/scaling.
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
Ecosystem integrations — the surrounding ecosystem — integrations, marketplaces, community packagesEcosystem integrations
The surrounding ecosystem — integrations, marketplaces, community packages
Chat notifications
developerSync repository notifications and activity with chat tools
weight 1 · round drawnGitLabnone0/10No evidence pack items mention Slack, Microsoft Teams, chat notifications, or integrations that sync repository activity to chat tools; evidence focuses on CI/CD, security scanning, REST API, and MCP/CLI docs.
Bitbucketnone0/10No evidence pack item mentions Slack/Teams/chat notification integrations or activity syncing with chat tools; all docs focus on Jira, CI/CD, security scanning, and AI features. Missing for 10: any mention of Slack/Teams integration, chat notification setup, or activity feed syncing to chat tools.
External ci cd integration
devops-leadConnect the platform to external CI/CD tools instead of using its native pipelines
weight 1 · round to BitbucketGitLabnone0/10The evidence pack shows extensive integrations (webhooks, API, third-party security scanners, IaC tools) and a robust REST API for building custom automation, but nothing documents official support for swapping GitLab's native CI/CD engine for an external CI/CD tool (e.g., Jenkins, CircleCI, TravisCI) as a replacement runner/orchestrator. One community note even states third-party CI services like TravisCI generally don't integrate with GitLab, reinforcing the gap. missing for 10: any documentation of connecting/using an external CI/CD orchestrator instead of GitLab's native pipelines, official integration guides for competing CI tools, evidence of webhook-triggered external pipeline execution replacing GitLab CI.
- [community] “I love Gitlab but sadly, quite a lot of services that offer free accounts for open source projects (TravisCI comes to mind), generally don't…”
- [claimed-docs] “Automate your workflows and build integrations with the GitLab REST API”
- [claimed-docs] “Make allows you to connect GitLab to more than 700 ready-made applications or to any API to integrate your DevSecOps processes and optimize …”
Bitbucket docs explicitly state you can use built-in Pipelines 'or connect Bitbucket Cloud to on-prem CI/CD tools like Bamboo or Jenkins,' directly confirming external CI/CD integration as an alternative to native pipelines. Missing for 10: independent/hands-on corroboration of setting up Jenkins/Bamboo integration and broader detail on other third-party CI/CD tool support beyond Bamboo/Jenkins.
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
Marketplace extensions
developerExtend my stack with third-party apps, actions, and AI models from a marketplace
weight 2 · round to GitLabGitLab documents an extensive technology-partners marketplace (AI coding agents like Cursor, Kilo, OpenCode, Greptile; security tools like Semgrep, Trivy; automation via Make with 700+ apps; docs, PM, and chat integrations) plus a dedicated AI Catalog/Agent Platform for discovering and configuring third-party agents/flows and AI models, with governance controls for allow/deny policies. missing for 10: independent/hands-on validation of marketplace install experience and breadth/quality curation beyond vendor listing pages.
- [claimed-docs] “Cursor is the best way to code with AI used by millions of developers and over 50,000 enterprises. You can use any frontier model, with a po…”
- [claimed-docs] “Greptile is building the unified validation layer for code, starting with an AI-powered code review agent that analyzes PRs with full codeba…”
- [claimed-docs] “Kilo is the open-source agentic engineering platform for GitLab. Powerful CLI and IDE agents autonomously plan, code, and verify tasks. Inte…”
- [claimed-docs] “Make allows you to connect GitLab to more than 700 ready-made applications or to any API to integrate your DevSecOps processes and optimize …”
- [claimed-docs] “Aqua Trivy is the fastest way for DevSecOps and security teams to shift left and get started with vulnerability and infrastructure as code (…”
- [claimed-docs] “Semgrep is a fast, open-source, static analysis tool that finds bugs and enforces code standards at editor, commit, and CI time. Precise rul…”
- [claimed-docs] “Discover agents and flows created by the GitLab team and community members.”
- [claimed-docs] “Custom agents are agents you create and configure for your team’s specific needs.”
- [claimed-docs] “Configure Allow, Ask, and Deny policies for agent tools, enforced at execution time for all connecting clients.”
Evidence shows some third-party/AI extensibility — Snyk security scanning integration, ability to connect to on-prem CI/CD tools, and Rovo AI model access in terminal/IDE — but there's no explicit mention of an app marketplace, listing of third-party apps, or an ecosystem of installable actions comparable to a dedicated marketplace story. Missing for 10: explicit marketplace/app directory documentation, breadth of third-party app listings, and independent corroboration of marketplace usage.
- [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
- [claimed-docs] “Access the latest models with Rovo — in your terminal or in your IDE.”
- [claimed-docs] “Use our built-in CI/CD tool, Bitbucket Pipelines, to create powerful, automated workflows. Or connect Bitbucket Cloud to on-prem CI/CD tools…”
- [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
Security tool integrations
devops-leadInstall third-party security scanning integrations directly from a security tab
weight 1 · round to BitbucketGitLabnone0/10Evidence shows GitLab consolidates its own built-in scanners (SAST, SCA, Secret Detection, DAST) into one platform rather than offering a marketplace/security tab for installing third-party scanning integrations. No mention of a security tab UI for adding third-party scanners exists in the evidence pack.
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform.”
- [claimed-docs] “Security findings appear directly in merge requests and IDEs.”
Docs explicitly confirm running automated security scans via out-of-the-box Snyk integration installed directly from the Security tab, plus support for connecting other providers, matching the story closely. Missing for 10: independent/hands-on corroboration of the Security tab install flow and breadth of third-party scanner ecosystem beyond Snyk.
- [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
Governance — stories about governance in this arenaGovernance
Stories about governance in this arena
Licensing cost management
devops-leadMake a single annual commitment and flexibly allocate spend across seat-based and usage-based licensing
weight 1 · round to GitLabgitlab-docs-4 directly claims a single annual commitment with flexible allocation across seat-based and usage-based licensing, matching the story closely, but this is a single first-party marketing line with no independent corroboration, pricing documentation, or hands-on confirmation of how allocation actually works. Missing for 10: detailed pricing/licensing docs explaining mechanics, third-party or customer confirmation, and any evidence of how re-allocation is executed in practice.
- [claimed-docs] “make one annual commitment and steer their spend across seat-based licenses and usage-based credits without re-procurement”
Onboarding
developerAccess built-in resources to learn the Git version control system
weight 1 · round to GitLabGitLab docs include a dedicated 'Work with the Git version control system' resource plus related guides (personal access tokens, SSH keys) that teach developers Git fundamentals within the built-in documentation platform. This directly matches the story of accessing built-in resources to learn Git. Missing for 10: independent/community corroboration that developers actually use these docs to learn Git, and more depth on tutorial-style learning content beyond reference docs.
- [claimed-docs] “Work with the Git version control system.”
- [claimed-docs] “Personal access tokens”
- [claimed-docs] “SSH keys”
Policy enforcement
devops-leadRequire automated change approval workflows before code reaches production
weight 1 · round to BitbucketGitLab's docs gesture at compliance controls, audit-ready evidence, and customizable workflows for deployment, and even mention 'human in the loop approvals' for Duo Agent Platform sessions, but the evidence pack never explicitly documents core mechanisms like required merge-request approvers, protected branches, or approval gates blocking production deploys. Missing for 10: explicit documentation of merge request approval rules/required approvers, protected branch/environment gating before production, and independent confirmation these controls are enforced in practice.
- [claimed-docs] “Apply controls for compliance and collect audit-ready evidence automatically in every pipeline.”
- [claimed-docs] “SAST, DAST, and compliance in every pipeline.”
- [claimed-docs] “Customize workflows for development, testing, security, and deployment.”
- [claimed-docs] “Customize workflows for development, testing, security, and deployment. Teams orchestrate from above the lifecycle while agents execute with…”
- [claimed-docs] “Human in the loop approvals for chat-based GitLab Duo Agent Platform sessions”
Bitbucket docs explicitly describe merge checks, branch permissions, CI/CD policy enforcement, and an explicit 'automated change approval process' integration with Jira Service Management mapping incidents to deployments, directly matching the governance story. Missing for 10: independent/hands-on verification of approval gating in practice and more detail on multi-stage production approval workflows beyond marketing copy.
- [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
- [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
- [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
- [claimed-docs] “Enable automated change approval processes and resolve incidents faster by mapping incidents to deployments with Bitbucket and Jira Service …”
devops-leadEnforce coding standards and CI/CD policies across all teams and repositories
weight 2 · round to GitLabGitLab provides explicit governance tooling: compliance controls with automatic audit-ready evidence per pipeline (gitlab-docs-20), consolidated SAST/DAST/SCA/Secret Detection across the platform enforced in CI/CD and MRs (gitlab-docs-2, gitlab-docs-29, gitlab-docs-50), APIs to manage CI/CD and permissions consistently across projects/orgs (gitlab-docs-13, gitlab-docs-14), and AI-agent-specific governance (Allow/Ask/Deny policies, audit logs, session monitoring) that extends policy enforcement to new AI workflows (gitlab-docs-44, gitlab-docs-45). This directly matches a devops-lead's need to standardize CI/CD and coding policy across teams/repos at scale. Missing for 10: independent/hands-on validation of policy enforcement at scale (e.g., third-party case study or audit report) and more detail on cross-project policy templates/compliance frameworks beyond marketing copy.
- [claimed-docs] “Apply controls for compliance and collect audit-ready evidence automatically in every pipeline.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform. Security findings appear directly in merge requests and I…”
- [claimed-docs] “SAST, DAST, and compliance in every pipeline.”
- [claimed-docs] “Manage CI/CD processes across multiple projects with precision.”
- [claimed-docs] “Control user access programmatically to maintain consistent permissions across your organization.”
- [claimed-docs] “Configure Allow, Ask, and Deny policies for agent tools, enforced at execution time for all connecting clients.”
- [claimed-docs] “Monitor AI agent sessions, audit logs, and developer exposure across a group.”
First-party docs directly claim enforcement of coding standards, CI/CD policies, merge checks, and granular permissions across teams/repos (bitbucket-docs-6, -7, -8, -9), which is exactly the story asked for. However, independent community evidence shows a real gap: an admin reported no way to prevent team members from making repositories public in Bitbucket Enterprise Cloud, undercutting the 'control at scale' claim (bitbucket-comm-19). Missing for 10: independent corroboration that merge-check/CI policy enforcement actually works at scale, and resolution of the reported permission-control gap.
- [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
- [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
- [claimed-docs] “Run CI/CD workflows across your organization using hosted or private runners—or both, with centralized visibility across pipeline status, te…”
- [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
- [community] “It appears that in bitbucket enterprise cloud, there is no way for an administrator to prevent members of my team from making repositories p…”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to GitLabGitLab documents a comprehensive REST API (with OpenAPI spec, interactive docs, versioning/deprecation policy) covering CI/CD, permissions, projects, and more, explicitly positioned for programmatic automation of workflows — plus an official CLI and MCP server extending API-driven access. However, there's no explicit vendor claim or evidence of full UI/API parity (e.g., some newer Agent Platform/UI-only settings, admin toggles) — missing for 10: an explicit parity statement or audit confirming every UI action has an API equivalent, and independent/community verification of this specific claim.
- [claimed-docs] “Automate your workflows and build integrations with the GitLab REST API”
- [claimed-docs] “You can browse and test every endpoint interactively in the [REST API documentation]”
- [claimed-docs] “Use the interactive request tool to send live requests to GitLab.”
- [claimed-docs] “GitLab supports authentication with HTTP Bearer or OAuth 2.0 credentials.”
- [claimed-docs] “Docs, "OpenAPI": "GitLab documents its REST API using the OpenAPI 3.0 specification (formerly called Swagger)... The OpenAPI spec is autogen…”
- [claimed-docs] “Docs, "REST API deprecations": "You should regularly review the following deprecations and make the recommended changes"; "GitLab will not m…”
- [claimed-docs] “Manage CI/CD processes across multiple projects with precision.”
- [claimed-docs] “Control user access programmatically to maintain consistent permissions across your organization.”
- [probe] “official MCP server documented at https://docs.gitlab.com/user/gitlab_duo/model_context_protocol/mcp_server/”
- [probe] “official CLI documented at https://docs.gitlab.com/editor_extensions/gitlab_cli/”
Bitbucketnone0/10No evidence describes Bitbucket's REST API coverage or parity with UI features; probes show missing OpenAPI/docs endpoints, and no documentation claims full API-UI parity.
- [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to GitLabGitLab's Git-based architecture (gitlab-docs-7) and REST API (gitlab-docs-12,15) let users programmatically extract issues, MRs, and code, and self-hosting options (Docker/Helm/Linux package, gitlab-docs-9,21,25) mean users aren't locked into GitLab.com. However, the evidence never cites GitLab's dedicated project/group export-import feature or documentation guaranteeing full data export in open formats, and community notes only describe importing data into GitLab, not exporting out. Missing for 10: explicit documentation of a full project/group data export feature, confirmation of open/portable export formats, and independent verification that a complete migration-out is straightforward.
- [claimed-docs] “Work with the Git version control system.”
- [claimed-docs] “Automate your workflows and build integrations with the GitLab REST API”
- [claimed-docs] “You can browse and test every endpoint interactively in the [REST API documentation]”
- [claimed-docs] “The Linux package includes services and tools to install GitLab without laborious configuration.”
- [claimed-docs] “If you're using cluster management, we recommend the Helm chart or the Operator for installing cloud-native GitLab.”
- [community] “Migrating repos are straightforward... GitHub importer can import: repository description, Git repository data, issues, pull requests, wiki …”
Bitbucketnone0/10No evidence of any data export/portability feature or open-format export capability for Bitbucket repos/issues; probes even show missing docs/API endpoints. Since git repos are inherently portable, this axis is fair for a code-hosting product, but nothing in the evidence pack confirms an explicit export-and-leave capability.
- [probe] “PROBE llms.txt: HTTP 404 at https://support.atlassian.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://support.atlassian.com/bitbucket-cloud.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.atlassian.com/openapi.json, https://support.atlassian.com/swagger.json, https://supp…”
ai-native userSelf-host the core product
weight 3 · round to GitLabGitLab's core product is explicitly documented as self-hostable via multiple official methods: Linux package (gitlab-docs-9), Docker images (gitlab-docs-25), Helm chart/Operator for Kubernetes (gitlab-docs-21), self-compilation (gitlab-docs-26), and scaling reference architectures (gitlab-docs-11). Community evidence corroborates real-world self-hosted usage (gitlab-comm-2 mentions a private self-hosted instance at work). Missing for 10: independent verification that newer AI/Duo Agent Platform features have full parity when self-managed vs. SaaS.
- [claimed-docs] “The Linux package includes services and tools to install GitLab without laborious configuration.”
- [claimed-docs] “If you're using cluster management, we recommend the Helm chart or the Operator for installing cloud-native GitLab.”
- [claimed-docs] “GitLab maintains a set of official Docker images based on the Linux package.”
- [claimed-docs] “If the Linux package isn't available for your distribution, you can self-compile GitLab.”
- [claimed-docs] “Scale your GitLab installation by using the recommended configurations.”
- [community] “I love GitLab, and I use a private instance at work, but I won't use it to store my public projects for one sole reason: you can't hide your…”
Evidence indicates Bitbucket Data Center/Server exists as a self-hosted deployment option (docs mention migrating code from 'Bitbucket Server or Data Center' to Cloud and trialing Cloud 'for the same user count as your Bitbucket Data Center license'), confirming self-hosting is possible, but no documentation describes setup, feature parity, or AI-native workflows for the self-hosted version. Missing for 10: dedicated self-host installation docs, feature parity details for Data Center, and any independent/hands-on confirmation of self-hosting the core product.
- [claimed-docs] “Our free app moves your code and users from Bitbucket Server or Data Center to Cloud.”
- [claimed-docs] “Sign up for a free Bitbucket Cloud Premium trial for the same user count and duration as your Bitbucket Data Center license.”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round to GitLabEvidence shows GitLab can be self-managed (Linux package, Docker images, Helm chart, self-compile) which implicitly lets an organization control where its instance and data physically reside, and mentions compliance/audit controls, but there is no explicit documentation of a GitLab.com SaaS region/residency selection feature or dedicated data-residency guarantee. missing for 10: explicit SaaS region-selection or data-residency policy documentation, evidence of enterprise data-residency add-on, independent confirmation of residency guarantees.
- [claimed-docs] “The Linux package includes services and tools to install GitLab without laborious configuration.”
- [claimed-docs] “If you're using cluster management, we recommend the Helm chart or the Operator for installing cloud-native GitLab.”
- [claimed-docs] “GitLab maintains a set of official Docker images based on the Linux package.”
- [claimed-docs] “If the Linux package isn't available for your distribution, you can self-compile GitLab.”
- [claimed-docs] “Apply controls for compliance and collect audit-ready evidence automatically in every pipeline.”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnGitLabnone0/10No evidence pack item addresses opting out of AI model training on user data, data usage policies for Duo/AI features, or any privacy controls specific to training-data exclusion; the AI governance items ([gitlab-docs-44], [gitlab-docs-45]) cover tool permissions and monitoring, not training data usage.
ai-native userControl data retention and deletion
weight 2 · round drawnGitLabnone0/10The evidence pack mentions AI governance features like Allow/Ask/Deny policies and audit logging (gitlab-docs-44, gitlab-docs-45) but contains no documentation of data retention periods, opt-out/deletion controls, or data handling policies specific to AI/Duo features or chat/session data. No evidence shows a user can configure or delete stored AI interaction data.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnGitLabnone0/10No evidence pack item discusses telemetry collection, usage tracking, or an opt-out/opt-in mechanism for GitLab or its AI/Duo features; ai-governance docs mention audit logs and policies but not telemetry opt-out. Missing for 10: any documentation of telemetry data collection scope, opt-out settings, or usage tracking controls.
Project planning — stories about project planning in this arenaProject planning
Stories about project planning in this arena
External pm sync
developerManage external issue tracker items directly within the code hosting UI
weight 1 · round to BitbucketGitLabnone0/10The evidence pack contains no mention of external issue tracker integrations (e.g., Jira, Bugzilla) or the ability to view/manage such items inside GitLab's UI; only unrelated topics like importing GitHub issues, APIs, and CI/CD are covered.
Bitbucket docs claim a built-in Jira UI for managing Jira issues directly within Bitbucket, plus opening Jira tickets from the PR screen and automatic status updates via commit issue keys, directly supporting external issue tracker management in the code hosting UI. Missing for 10: independent/hands-on corroboration of this specific Jira UI feature and detail on its scope/limitations.
- [claimed-docs] “Reduce context-switching by managing your Jira issues in Bitbucket with the built-in Jira UI”
- [claimed-docs] “when you include your issue key in commits, your Jira issue statuses update automatically”
- [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
developerAutomatically update linked issue tracker statuses by referencing issue keys in my commits
weight 2 · round to BitbucketGitLabnone0/10The evidence pack contains no documentation of commit-message keyword parsing (e.g., 'Closes #123') that automatically transitions or closes linked issues; only generic platform and API descriptions are present, none referencing this specific capability.
Bitbucket docs directly state that including a Jira issue key in commits automatically updates the linked Jira issue's status, and Bitbucket's Jira integration also allows opening/viewing tickets from PR screens. missing for 10: independent/hands-on corroboration of the auto-transition behavior and details on configuration (e.g., required smart commit syntax or workflow mapping).
- [claimed-docs] “when you include your issue key in commits, your Jira issue statuses update automatically”
- [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
Issue tracking
developerTrack requirements, features, and bugs using issues with milestones, time tracking, and dependencies
weight 3 · round to BitbucketGitLabnone0/10The evidence pack contains no documentation describing GitLab's issue tracking, milestones, time tracking, or issue dependency features; the only tangential mention is that milestones are importable data from GitHub (a migration detail, not a feature description). Missing for 10: any docs or community evidence on issue creation, milestone planning, time tracking, or linking blocking/dependent issues.
- [community] “Migrating repos are straightforward... GitHub importer can import: repository description, Git repository data, issues, pull requests, wiki …”
Bitbucket docs mention Jira issue integration (auto status updates on commit, built-in Jira UI in Bitbucket, opening Jira tickets from PRs) which covers basic issue tracking, but this relies entirely on a separate Jira product rather than native Bitbucket issue features, and there is no mention of milestones, time tracking, or dependency tracking anywhere in the evidence. missing for 10: native milestone support, time tracking, dependency linking, and evidence these work without requiring a separate Jira subscription.
- [claimed-docs] “when you include your issue key in commits, your Jira issue statuses update automatically”
- [claimed-docs] “Reduce context-switching by managing your Jira issues in Bitbucket with the built-in Jira UI”
- [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
developerManage projects and assign tasks from my mobile device
weight 1 · round drawnGitLabnone0/10No evidence pack item mentions a mobile app, mobile-optimized UI, or mobile-specific workflow for managing projects or assigning tasks; all cited capabilities (API, CLI, Duo Agent Platform, integrations) are desktop/web/CI-oriented. Missing for 10: any mention of a native or mobile-web GitLab app, mobile task assignment, or mobile project management workflow.
developerOrganize work from high-level roadmaps to everyday tasks using project boards
weight 2 · round drawnGitLabnone0/10The evidence pack contains no concrete documentation of GitLab's project boards, epics, or roadmap features; only a single generic marketing mention of 'planning' appears in a broader lifecycle tagline (gitlab-docs-19), with no detail on issue boards, milestones, or roadmap views. This is insufficient to demonstrate the story's capability.
- [claimed-docs] “From planning to source control to CI/CD, everything you need to build and ship software faster in one platform.”
Repos collaboration — working on repos together — pull requests, reviews, permissionsRepos collaboration
Working on repos together — pull requests, reviews, permissions
Code review
ai-native userHave an AI reviewer analyze code changes and suggest fixes during review
weight 2 · round to GitLabGitLab's Duo Agent Platform explicitly supports AI agents that review code and suggest fixes ('review code while your team stays in control', findings surfaced directly in merge requests) and this is extended by third-party AI code review agents like Greptile and CodeAnt AI integrated into MR workflows. Governance controls (allow/ask/deny, human-in-the-loop approvals) further support this being a real, controllable capability rather than just marketing copy. missing for 10: independent hands-on validation of AI-suggested fixes quality/accuracy in real MR reviews, and more detail on native (non-partner) Duo code review suggestion mechanics.
- [claimed-docs] “Agents turn issues into merge requests, remediate vulnerabilities, and review code while your team stays in control.”
- [claimed-docs] “Security findings appear directly in merge requests and IDEs.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform. Security findings appear directly in merge requests and I…”
- [claimed-docs] “Delegate routine tasks, from code refactoring and security scans to research, to specialized AI agents.”
- [claimed-docs] “Human in the loop approvals for chat-based GitLab Duo Agent Platform sessions”
- [claimed-docs] “Greptile is building the unified validation layer for code, starting with an AI-powered code review agent that analyzes PRs with full codeba…”
- [claimed-docs] “CodeAnt AI brings AI-native code reviews, security scanning (SAST/SCA), and code quality enforcement to GitLab merge requests.”
Bitbucket's own docs explicitly claim an AI code reviewer that reviews changes and suggests fixes (bitbucket-docs-3), directly matching the story, and code review features are documented alongside it (bitbucket-docs-11). However, there is no independent/hands-on evidence corroborating this AI reviewer's real-world behavior or quality, and no detail on how suggestions are surfaced during PR review. missing for 10: independent/hands-on verification of the AI reviewer's accuracy and workflow, detailed documentation of the suggestion/fix mechanism.
- [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
- [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
ai-native userAssign the initial code review of a pull request to an AI reviewer for faster turnaround
weight 2 · round to GitLabGitLab documents AI agents that review code and integrate into merge requests (e.g., 'Agents ... review code while your team stays in control', security findings in MRs, Duo Agent Platform delegating tasks to specialized agents) plus third-party marketplace agents like Greptile and CodeAnt AI explicitly for AI-powered PR/MR review. However, there is no direct documentation showing a first-party workflow to explicitly 'assign' an MR's initial review to an AI reviewer as a reviewer role (vs. automated scanning/chat), so the exact story is only partially evidenced. missing for 10: explicit first-party doc on designating/assigning an AI agent as the primary/initial MR reviewer, and independent hands-on confirmation of turnaround-speed benefit.
- [claimed-docs] “Agents turn issues into merge requests, remediate vulnerabilities, and review code while your team stays in control.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform. Security findings appear directly in merge requests and I…”
- [claimed-docs] “Delegate routine tasks, from code refactoring and security scans to research, to specialized AI agents.”
- [claimed-docs] “Greptile is building the unified validation layer for code, starting with an AI-powered code review agent that analyzes PRs with full codeba…”
- [claimed-docs] “CodeAnt AI brings AI-native code reviews, security scanning (SAST/SCA), and code quality enforcement to GitLab merge requests.”
Bitbucket docs claim an AI code reviewer that reviews all code changes and suggests fixes to speed merges, which addresses the core idea of AI-driven review turnaround, but there is no evidence describing an explicit 'assign as reviewer on a PR' workflow, configurability, or independent/hands-on confirmation of this feature working. missing for 10: evidence of assigning AI as a designated PR reviewer, setup/configuration details, and independent corroboration of real-world use.
- [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
- [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
developerReview code changes online and respond to inline review comments
weight 3 · round to BitbucketThe evidence repeatedly references merge requests as the code-review surface (e.g., security findings appearing directly in merge requests, agents reviewing code, Chat searching for merge requests) which implies GitLab's core online MR review workflow exists, but no citation explicitly documents inline comment threads or replying to review comments. missing for 10: explicit documentation of inline diff comments, comment threading/resolution, and reply workflows within merge requests.
- [claimed-docs] “Agents turn issues into merge requests, remediate vulnerabilities, and review code while your team stays in control.”
- [claimed-docs] “Security findings appear directly in merge requests and IDEs.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform. Security findings appear directly in merge requests and I…”
- [claimed-docs] “you can ask “Find the merge request about authentication” and Chat searches for relevant merge req”
- [claimed-docs] “Greptile is building the unified validation layer for code, starting with an AI-powered code review agent that analyzes PRs with full codeba…”
Bitbucket's docs claim comprehensive PR code review features including reviewing diffs and commenting from the PR screen (bitbucket-docs-11), which implies inline review comments are supported, but no evidence explicitly confirms responding/threading on inline comments, and community feedback focuses on unrelated UI/browsing complaints rather than confirming this specific workflow. missing for 10: explicit documentation or hands-on evidence of inline comment threads/replies, independent corroboration of the review-comment workflow.
- [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
developerReview large diffs and view third-party code quality reports directly in the review screen
weight 2 · round to BitbucketGitLab docs confirm that security/scanner findings (SAST, SCA, Secret Detection, DAST) appear directly in merge requests, which supports third-party report visibility in the review screen (gitlab-docs-2, gitlab-docs-3). However, there is no evidence specifically addressing large-diff review capabilities (e.g., diff collapsing, file-by-file navigation for large changesets) nor explicit mention of a dedicated 'code quality' report widget distinct from security scanners. Missing for 10: evidence of large-diff handling UX, explicit code-quality (non-security) report integration, and independent/hands-on confirmation.
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform.”
- [claimed-docs] “Security findings appear directly in merge requests and IDEs.”
Bitbucket docs explicitly state the product lets developers 'Review large diffs with ease, view third-party code reports, and open Jira tickets right from the PR screen,' directly matching the story. Missing for 10: independent/hands-on corroboration of this specific feature (community evidence discusses other UI aspects but not this capability).
- [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
devops-leadEnforce standardized, customizable merge checks before code can be merged
weight 2 · round to BitbucketEvidence shows GitLab embeds compliance controls, audit evidence, and security scan results (SAST/DAST/SCA) directly into merge requests, and lets teams customize workflows across the lifecycle — suggesting standardized, customizable gates before merge. However, the pack never explicitly documents core merge-check mechanics like approval rules, required reviewers, or branch protection settings, only their compliance/security-adjacent framing. Missing for 10: explicit merge request approval rules/required approvers documentation, branch protection/push rules details, and independent verification that these checks are enforced as blocking gates.
- [claimed-docs] “Apply controls for compliance and collect audit-ready evidence automatically in every pipeline.”
- [claimed-docs] “Customize workflows for development, testing, security, and deployment.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform.”
- [claimed-docs] “Security findings appear directly in merge requests and IDEs.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform. Security findings appear directly in merge requests and I…”
- [claimed-docs] “SAST, DAST, and compliance in every pipeline.”
Bitbucket docs explicitly state support for 'standardized, customizable merge checks' to enforce code quality, compliance, and CI/CD policies across teams and repos, backed by branch-level permission controls. Missing for 10: independent/hands-on corroboration of merge-check configuration in practice and detail on granularity of check types beyond marketing copy.
- [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
- [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
- [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
Package registry
open-source-maintainerPublish and consume software packages in multiple package formats from the same platform
weight 2 · round drawnGitLabnone0/10The evidence pack contains no mention of GitLab's Package Registry or support for multiple package formats (npm, Maven, PyPI, Docker, etc.) that would let a maintainer publish and consume packages across formats from one platform; all citations focus on CI/CD, security scanning, AI agents, and integrations. missing for 10: any documentation of the Package Registry, supported package formats, publish/consume workflows, or package-registry API endpoints.
Bitbucketnone0/10No evidence in the pack mentions a package registry or multi-format package management capability (e.g., npm, Maven, Docker, PyPI) in Bitbucket; docs only reference container image/tag permissions in passing without describing a package publishing feature. Missing for 10: any documentation of a package registry, supported package formats, or publish/consume workflows.
Repo management
devops-leadControl granular access permissions at the workspace, project, repository, and branch level
weight 2 · round to BitbucketEvidence only vaguely references permission control ('Control user access programmatically to maintain consistent permissions across your organization') and generic auth mechanisms (PATs, SSH keys, OAuth), but the pack contains no documentation of protected branches, CODEOWNERS, project/group role hierarchies, or workspace-level access scoping that would substantiate granular multi-level control. Missing for 10: explicit docs on protected branch rules, group/project role-based permissions, and workspace-level access scoping with independent corroboration.
- [claimed-docs] “Control user access programmatically to maintain consistent permissions across your organization.”
- [claimed-docs] “Personal access tokens”
- [claimed-docs] “SSH keys”
First-party docs explicitly state control over permissions at workspace, project, repo, and granular branch/environment/package levels (bitbucket-docs-9), directly matching the story, and is reinforced by broader policy/compliance enforcement claims (bitbucket-docs-6, bitbucket-docs-7). Missing for 10: independent hands-on corroboration of granular branch-level permission enforcement, and one community note (bitbucket-comm-19) suggests admins lack full control over repo visibility, indicating some gaps in enterprise-wide permission enforcement.
- [claimed-docs] “Control permissions at the workspace, project, or repo level, and define granular branch‑level, environment‑level, and package permissions —…”
- [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
- [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
- [community] “It appears that in bitbucket enterprise cloud, there is no way for an administrator to prevent members of my team from making repositories p…”
developerSearch across repositories to find code, files, and commits
weight 2 · round to GitLabEvidence only shows GitLab Duo Chat can search for relevant merge requests and has access to a project's issues, commits, and CI/CD data (gitlab-docs-39, gitlab-docs-48), which touches on finding commits/MRs conversationally but does not document GitLab's broader code/file search or cross-repository search capability. Missing for 10: explicit documentation of full-text code search, file search, and search scoped across multiple repositories/projects (e.g., an 'Advanced Search' feature), plus independent corroboration of search quality.
- [claimed-docs] “you can ask “Find the merge request about authentication” and Chat searches for relevant merge req”
- [claimed-docs] “Chat has access to your project, including issues, merge requests, commits, and CI/CD pipelines, and Chat maintains context across conversat…”
Bitbucketnone0/10No vendor documentation in the evidence pack describes a code/commit search feature, and community reports explicitly state Bitbucket lacks a search feature ('there isn't even a search feature, let alone browse capability' and 'no search feature by language'), so there is no evidence the story is delivered.
- [community] “So how do I browse projects hosted on BitBucket? No search feature by language, no Explore feature like GitHub - can't test drive before sig…”
- [community] “I love bitbucket but I would like to be able to create clusters of related projects by language/tool. Right now there isn't even a search fe…”
developerCreate and manage Git repositories and browse their commit history
weight 3 · round to GitLabGitLab is a core Git repository hosting platform with documented support for creating/managing repos, SSH/PAT authentication, and Git version control workflows (gitlab-docs-7, 31, 5, 6, 32), plus community evidence confirming real-world repo migration and usage (gitlab-comm-3). Commit history browsing is implicit in its core Git platform functionality and referenced via merge requests/commits in Chat context (gitlab-docs-48). Missing for 10: no explicit dedicated documentation snippet describing the commit-history browsing UI itself, relying on inference from broader platform docs.
- [claimed-docs] “Work with the Git version control system.”
- [claimed-docs] “Get started with Git Work with the Git version control system.”
- [claimed-docs] “Personal access tokens”
- [claimed-docs] “SSH keys”
- [claimed-docs] “[Personal access tokens](/user/profile/personal_access_tokens/)”
- [claimed-docs] “Chat has access to your project, including issues, merge requests, commits, and CI/CD pipelines, and Chat maintains context across conversat…”
- [community] “Migrating repos are straightforward... GitHub importer can import: repository description, Git repository data, issues, pull requests, wiki …”
Bitbucket is fundamentally a Git hosting platform, and community evidence confirms core repo hosting and commit-history browsing (praised commits view with graph, per-repo deploy keys, Mercurial repo hosting) even though some users criticize the web browsing UX and lack of a project explore/search feature. Missing for 10: first-party docs explicitly describing repo creation/management workflow, and resolution of complaints about slow/painful source browsing and missing cross-project browse/search.
- [community] “The redesigned commits view is 100 times better than Github's ever was - so much more info, and even a graph like in gitx.”
- [community] “As a daily Bitbucket user, browsing source code via web is painful and slow compared to Github's slicker UI with tree slider navigation.”
- [community] “So how do I browse projects hosted on BitBucket? No search feature by language, no Explore feature like GitHub - can't test drive before sig…”
- [community] “I love bitbucket but I would like to be able to create clusters of related projects by language/tool. Right now there isn't even a search fe…”
- [community] “Bitbucket's deploy key is read-only and can be attached to multiple repos, unlike Github's which is read-write and single-repo only - a much…”
- [community] “This is disappointing. Bitbucket is the premier place to host free private mercurial repos - there is literally not a single other place for…”
developerPropose, discuss, and merge code changes using a pull or merge request workflow
weight 3 · round drawnMerge requests are referenced pervasively across the evidence pack as the core collaboration unit — security findings, Chat search, third-party integrations (Notion, PagerDuty), and GitHub-import parity all treat MRs as the central discuss/review/merge construct, and gitlab-comm-3 confirms PR/MR review comments and workflow parity with GitHub. Missing for 10: a dedicated first-party doc excerpt walking through creating/discussing/approving/merging an MR (approvals, threads, merge rules) rather than only peripheral mentions.
- [claimed-docs] “Agents turn issues into merge requests, remediate vulnerabilities, and review code while your team stays in control.”
- [claimed-docs] “Security findings appear directly in merge requests and IDEs.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform. Security findings appear directly in merge requests and I…”
- [claimed-docs] “you can ask “Find the merge request about authentication” and Chat searches for relevant merge req”
- [claimed-docs] “Chat has access to your project, including issues, merge requests, commits, and CI/CD pipelines, and Chat maintains context across conversat…”
- [claimed-docs] “Send notification-free events from GitLab to PagerDuty services regarding important changes, such as merge requests, to provide context for …”
- [claimed-docs] “Notion's synced databases integration with GitLab allows users to bring merge requests, issues, and more into their Notion workspace, so tea…”
- [community] “Migrating repos are straightforward... GitHub importer can import: repository description, Git repository data, issues, pull requests, wiki …”
Bitbucket docs confirm comprehensive PR/code review features (opening PRs, reviewing diffs, merge checks, opening Jira tickets from PR screen) which directly support the propose/discuss/merge workflow. missing for 10: independent hands-on corroboration of the actual PR discussion/merge UX (community evidence focuses on repo browsing, pricing, and UI gripes rather than PR workflow specifics), and no detail on review comment threading or approval mechanics.
- [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
- [claimed-docs] “Enforce code quality policies and compliance requirements across the organization with standardized, customizable merge checks.”
- [claimed-docs] “Be confident in your software delivery by enforcing coding standards, CI/CD policies, and change management workflows across all teams and r…”
Security — security posture and hardening storiesSecurity
Security posture and hardening stories
Access security
devops-leadRestrict repository access to specific IP address ranges
weight 2 · round to BitbucketGitLabnone0/10The evidence pack contains no documentation of IP allowlisting/IP range restriction features for repository access; nothing about network restrictions, IP allowlists, or similar controls appears in the docs or community items.
Bitbucket docs explicitly state IP allowlisting is a security feature to restrict code access to authorized users, directly matching the story. Missing for 10: detailed documentation on granularity (per-repo vs workspace-wide IP ranges), independent/hands-on confirmation, and enterprise-tier limitations.
- [claimed-docs] “2FA and IP allowlisting keep your code accessible only by authorized users. All code is encrypted in transit and at rest.”
developerGenerate and manage personal access tokens for authenticating to the platform
weight 2 · round to GitLabGitLab's docs explicitly cover personal access tokens as a dedicated authentication mechanism (gitlab-docs-5), with usage shown in API auth flows (gitlab-docs-22) and support for HTTP Bearer/OAuth2 alongside PATs (gitlab-docs-17). This directly matches the developer story of generating/managing PATs for platform authentication. Missing for 10: no hands-on/community evidence confirming token management UX (expiration, scopes, rotation) works smoothly in practice, and no independent corroboration beyond first-party docs.
- [claimed-docs] “Personal access tokens”
- [claimed-docs] “For `http`, enter your [personal access token](/user/profile/personal_access_tokens/).”
- [claimed-docs] “GitLab supports authentication with HTTP Bearer or OAuth 2.0 credentials.”
Bitbucketnone0/10No evidence pack items mention personal access tokens or app passwords for authentication; only 2FA and IP allowlisting are cited, which do not address PAT generation/management. Missing for 10: any documentation or mention of personal access tokens, app passwords, or token scopes/lifecycle management.
developerSet up SSH keys to authenticate and connect securely to the platform
weight 2 · round to GitLabGitLab documents SSH key setup as a first-party feature (gitlab-docs-6) alongside Git version control support (gitlab-docs-7), confirming the core capability for developers to authenticate via SSH. Missing for 10: no detailed walkthrough content in the pack (e.g., key generation steps, troubleshooting), and no independent/community corroboration of SSH auth working reliably in practice.
- [claimed-docs] “SSH keys”
- [claimed-docs] “Work with the Git version control system.”
Bitbucketnone0/10The evidence pack contains no first-party documentation describing SSH key setup or authentication for Bitbucket; the only relevant reference is a community complaint (bitbucket-comm-4) describing repeated authentication failures despite adding an SSH key, which does not establish that the feature works as expected. Without any vendor documentation or successful hands-on confirmation, there is no evidence the capability is delivered.
- [community] “I have to authenticate every time I push to the repo despite adding my SSH key; can't find equivalent to github.user/github.token config for…”
developerSecure my account with two-factor authentication
weight 3 · round to BitbucketGitLabnone0/10The evidence pack covers personal access tokens, SSH keys, and various security scanning features (SAST/DAST) but contains no mention of two-factor authentication (2FA/MFA) setup or enforcement for developer accounts. Missing for 10: any documentation of 2FA/MFA enrollment, enforcement policies, or authenticator app support.
Bitbucket docs explicitly state '2FA and IP allowlisting keep your code accessible only by authorized users,' confirming native two-factor authentication support for account security. Missing for 10: no independent/hands-on corroboration of the 2FA setup flow or details on supported methods (e.g., TOTP, SMS, hardware keys).
- [claimed-docs] “2FA and IP allowlisting keep your code accessible only by authorized users. All code is encrypted in transit and at rest.”
Vulnerability scanning
ai-native userHave AI automatically generate and apply fixes for detected security vulnerabilities
weight 2 · round to GitLabGitLab explicitly markets AI agents that 'remediate vulnerabilities' via merge requests, and Duo Agent Platform lets users 'delegate...security scans' to specialized agents, with findings surfacing in MRs/IDEs from consolidated scanners (SAST/SCA/DAST). However, evidence is limited to marketing/docs snippets without a detailed workflow description of automatic fix generation-and-apply, no hands-on/independent confirmation of remediation quality or reliability, and human-in-the-loop approval is emphasized (suggesting fixes aren't auto-applied without review). Missing for 10: independent/hands-on verification of auto-generated fix quality, detailed docs on the vulnerability-to-fix pipeline, and confirmation that fixes can be applied without human approval when desired.
- [claimed-docs] “Agents turn issues into merge requests, remediate vulnerabilities, and review code while your team stays in control.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform. Security findings appear directly in merge requests and I…”
- [claimed-docs] “Delegate routine tasks, from code refactoring and security scans to research, to specialized AI agents.”
- [claimed-docs] “Human in the loop approvals for chat-based GitLab Duo Agent Platform sessions”
- [claimed-docs] “SAST, DAST, and compliance in every pipeline.”
Bitbucket integrates Snyk for automatic security scanning and has an AI code reviewer that 'suggests fixes' for code changes, plus AI-powered pipeline workflows that can automate fixes for some issues, but there is no evidence of AI automatically generating and applying patches specifically for detected security vulnerabilities. Missing for 10: explicit documentation of AI auto-remediation tied to Snyk/security scan findings, evidence of automatic PR creation/application of security fixes, and independent confirmation this works hands-on.
- [claimed-docs] “Our AI code reviewer reviews all code changes and suggests fixes so you can merge faster.”
- [claimed-docs] “Trigger AI-powered workflows to automate tedious tasks: clean up feature flags, update docs, draft release notes, fix flaky tests, and more …”
- [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
developerAutomatically receive pull requests that update vulnerable dependencies
weight 3 · round to GitLabGitLab's SCA/Dependency Scanning surfaces vulnerability findings directly in merge requests, and its Duo Agent Platform explicitly states agents can 'turn issues into merge requests, remediate vulnerabilities' (gitlab-docs-1, gitlab-docs-2, gitlab-docs-29), which implies auto-generated MRs to fix vulnerable dependencies. However, there's no explicit documentation of a Dependabot/Renovate-style automatic bot that proactively opens dependency-bump PRs on a schedule — the evidence only shows scan findings appearing in MRs and agent-driven remediation, not a dedicated automated dependency-update workflow. missing for 10: explicit doc of automatic scheduled dependency-update merge requests (Renovate/Dependabot-equivalent), independent/hands-on confirmation of this exact workflow.
- [claimed-docs] “Agents turn issues into merge requests, remediate vulnerabilities, and review code while your team stays in control.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform. Security findings appear directly in merge requests and I…”
Bitbucketnone0/10Evidence only shows Bitbucket offers security scanning via a Snyk integration (bitbucket-docs-12), but there is no mention of automatically generated pull requests to update vulnerable dependencies (a Dependabot-like feature). Missing for full credit: any documentation of automated dependency-update PR creation, PR scheduling/frequency settings, or dependency graph triggers.
- [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
devops-leadConsolidate static analysis, dependency, secret, and dynamic security scanning into one platform
weight 3 · round to GitLabGitLab explicitly documents consolidating SAST, SCA (dependency scanning), Secret Detection, and DAST into one platform, with findings surfacing directly in merge requests and IDEs, plus compliance controls and audit evidence per pipeline — directly matching the devops-lead's consolidation story. Missing for 10: independent/hands-on third-party validation of the combined scanning workflow (only vendor docs are present, no community corroboration specific to security scanning consolidation).
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform.”
- [claimed-docs] “Security findings appear directly in merge requests and IDEs.”
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform. Security findings appear directly in merge requests and I…”
- [claimed-docs] “SAST, DAST, and compliance in every pipeline.”
- [claimed-docs] “Apply controls for compliance and collect audit-ready evidence automatically in every pipeline.”
Bitbucket documents an out-of-the-box Snyk integration for automatic security scans and mentions viewing third-party code reports in PRs, but this is a single third-party integration rather than a native unified platform combining static analysis, dependency, secret, and dynamic scanning. Missing for 10: native SAST/secret/DAST scanning tools, evidence of a single consolidated security dashboard, and independent confirmation the integration covers all four scan types.
- [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
- [claimed-docs] “Comprehensive code review features to help you find and fix bugs before you deploy. Review large diffs with ease, view third-party code repo…”
devops-leadDetect and remediate leaked secrets across the organization's repositories
weight 2 · round to GitLabGitLab's docs mention Secret Detection as part of a consolidated scanning platform with findings surfacing in merge requests/IDEs, which supports detection of leaked secrets, but there is no specific evidence of organization-wide scanning across all repos, remediation workflows (revocation, rotation, historic commit scrubbing), or any alerting/dashboard for leaked secrets specifically. Missing for 10: org-wide/cross-repo secret scanning details, concrete remediation workflow (auto-revoke, git history purge), independent/hands-on validation of Secret Detection efficacy.
- [claimed-docs] “Consolidate scanners like SAST, SCA, Secret Detection, and DAST into one platform.”
- [claimed-docs] “Security findings appear directly in merge requests and IDEs.”
Bitbucketnone0/10The evidence only mentions generic security scanning via Snyk integration and general permission/2FA controls, with no specific mention of secret detection, leaked credential scanning, or organization-wide remediation workflows. Missing for 10: any documentation of secret-scanning capability, push-protection, or remediation workflow for leaked credentials.
- [claimed-docs] “Run automatic security scans with out-of-the-box integration with Snyk, or connect to other providers. Simply open an existing repository or…”
- [claimed-docs] “2FA and IP allowlisting keep your code accessible only by authorized users. All code is encrypted in transit and at rest.”
Self hosting — running it yourself — self-hosted servers, open-source clientsSelf hosting
Running it yourself — self-hosted servers, open-source clients
Deployment options
devops-leadRun my self-hosted instance on my choice of operating system and architecture, including containers
weight 2 · round to GitLabGitLab documents multiple self-hosting install paths: the Linux package for various distros, official Docker images, Helm chart/Operator for Kubernetes/cloud-native deployments, and self-compilation as a fallback for unsupported distros, plus scaling guidance for larger installs. This covers OS flexibility and containerized deployment well, but there is no explicit mention of architecture support (e.g., ARM64 vs x86_64) or non-Linux host OS options. Missing for 10: explicit CPU architecture support details, broader OS coverage beyond Linux, and independent/community confirmation of multi-arch or container deployment success.
- [claimed-docs] “The Linux package includes services and tools to install GitLab without laborious configuration.”
- [claimed-docs] “If you're using cluster management, we recommend the Helm chart or the Operator for installing cloud-native GitLab.”
- [claimed-docs] “GitLab maintains a set of official Docker images based on the Linux package.”
- [claimed-docs] “If the Linux package isn't available for your distribution, you can self-compile GitLab.”
- [claimed-docs] “Scale your GitLab installation by using the recommended configurations.”
Bitbucketnone0/10Evidence confirms a self-hosted Bitbucket Data Center product exists (migration tooling, DC license trials) but contains no documentation of supported operating systems, CPU architectures, or containerized/Docker deployment options.
- [claimed-docs] “Our free app moves your code and users from Bitbucket Server or Data Center to Cloud.”
- [claimed-docs] “Sign up for a free Bitbucket Cloud Premium trial for the same user count and duration as your Bitbucket Data Center license.”
devops-leadScale my self-hosted installation using reference architectures supporting tens of thousands of users
weight 2 · round to GitLabGitLab documents reference architectures and scaling guidance ('Scale your GitLab installation by using the recommended configurations') plus supporting deployment options (Helm chart/Operator, Docker images, Linux package) that underpin large-scale self-hosted setups. However, there is no explicit mention of specific reference architecture tiers (e.g., 10k/25k/50k users) or benchmarks, and community evidence highlights real operational reliability issues (downtime, failed backups, performance problems) that raise doubts about smooth scaling in practice. Missing for 10: explicit named reference-architecture tiers for tens of thousands of users, third-party validation of scaling at that size, and resolution of community-reported reliability/performance concerns at scale.
- [claimed-docs] “Scale your GitLab installation by using the recommended configurations.”
- [claimed-docs] “If you're using cluster management, we recommend the Helm chart or the Operator for installing cloud-native GitLab.”
- [claimed-docs] “GitLab maintains a set of official Docker images based on the Linux package.”
- [claimed-docs] “The Linux package includes services and tools to install GitLab without laborious configuration.”
- [community] “GitLab's recent performance has been abysmal... we've had entire days where the team was unable to deploy because the CI workers did not run…”
- [community] “Meanwhile GitLab is crashing... Getting a 502 currently. I feel sorry for the Gitlab on-call right now.”
- [community] “So in other words, out of 5 backup/replication techniques deployed none are working reliably or set up in the first place.”
devops-leadUse migration tooling to move my code and users from another platform or from self-hosted to cloud
weight 2 · round to BitbucketCommunity evidence confirms GitLab has a GitHub importer that migrates repos, issues, PRs, wikis, labels and comments (gitlab-comm-3), and partner directory lists third-party services like Relokia and Unito for migrating from other platforms/PM tools (gitlab-intdir-12, gitlab-intdir-13). However there's no first-party documentation in the pack describing GitLab's own self-managed-to-SaaS migration tooling or user/account migration specifics. Missing for 10: official GitLab docs on bulk/group migration between self-managed and GitLab.com, user account migration details, and independent hands-on validation of a full self-hosted-to-cloud migration.
- [community] “Migrating repos are straightforward... GitHub importer can import: repository description, Git repository data, issues, pull requests, wiki …”
- [claimed-docs] “Relokia offers an advanced project management migration service, enabling effortless data transfer between GitLab and PM tools such as Asana…”
- [claimed-docs] “Manage your entire development cycle more efficiently from a single tool by syncing GitLab with Unito. With Unito, you can connect GitLab wi…”
- [claimed-docs] “The Linux package includes services and tools to install GitLab without laborious configuration.”
Bitbucket documents a free migration app to move code and users from Bitbucket Server/Data Center to Cloud, plus a Cloud Premium trial matching Data Center license user count/duration to ease migration. This directly addresses moving from self-hosted to cloud, though evidence is limited to first-party claims with no independent/hands-on corroboration and no mention of migrating from other platforms (e.g., GitHub/GitLab). Missing for 10: independent verification of the migration tool's reliability, and evidence of tooling for migrating from third-party platforms other than Bitbucket Server/Data Center.
- [claimed-docs] “Our free app moves your code and users from Bitbucket Server or Data Center to Cloud.”
- [claimed-docs] “Sign up for a free Bitbucket Cloud Premium trial for the same user count and duration as your Bitbucket Data Center license.”
devops-leadInstall a self-managed instance of the platform without laborious configuration
weight 3 · round to GitLabGitLab explicitly documents an omnibus 'Linux package' that 'includes services and tools to install GitLab without laborious configuration,' plus alternate self-managed paths (Docker images, Helm chart/Operator for cloud-native, self-compile) and scaling guidance, directly matching the devops-lead's self-hosting install story. Missing for 10: independent/hands-on confirmation that the install is actually low-effort in practice, and no step-count/time-to-install evidence beyond vendor docs.
- [claimed-docs] “The Linux package includes services and tools to install GitLab without laborious configuration.”
- [claimed-docs] “Scale your GitLab installation by using the recommended configurations.”
- [claimed-docs] “If you're using cluster management, we recommend the Helm chart or the Operator for installing cloud-native GitLab.”
- [claimed-docs] “GitLab maintains a set of official Docker images based on the Linux package.”
- [claimed-docs] “If the Linux package isn't available for your distribution, you can self-compile GitLab.”
Bitbucketnone0/10The evidence only mentions migrating from self-managed Bitbucket Server/Data Center to Cloud and trial licensing (bitbucket-docs-15, bitbucket-docs-16), but provides no documentation of an actual self-managed installation process, ease of setup, or reduced configuration effort. No evidence describes install steps, deployment tooling, or admin experience for a self-hosted instance.
- [claimed-docs] “Our free app moves your code and users from Bitbucket Server or Data Center to Cloud.”
- [claimed-docs] “Sign up for a free Bitbucket Cloud Premium trial for the same user count and duration as your Bitbucket Data Center license.”
Not comparable on these axes
ai-native userRead the product's source under an open license
weight 2 · not comparableGitLabnone0/10The axis clearly applies (a DevOps platform's source licensing is a fair comparison point), but nothing in the evidence pack documents GitLab's source code being available under an open license (e.g., no mention of the Community Edition repo, MIT license, or open-source status). Community items reference transparency in incident handling, not source-code licensing.
Bitbucketn/aBitbucket is a proprietary closed-source SaaS/on-prem product; there is no evidence its own source code is available under an open license, and this axis is not a fair question for this kind of commercial hosted product's category — it's a category error, not a gap in an applicable capability.