GitLab vs Gitea
free-tier · subscription-per-seat · usage-based · enterprise-custom
·open-source · hosted-paid · subscription-per-seat · support-contracts
GitLab wins · 35–22 (12 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.”
Giteanone0/10The probe explicitly shows llms.txt returns 404 at docs.gitea.com, and no other evidence indicates agent-oriented documentation exists elsewhere; the OpenAPI probe also failed, further indicating no machine-readable/agent-friendly docs endpoint.
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnGitLab 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”
Gitea deploys as a single binary or container with no complex dependencies, runs on Linux/Windows/macOS/Kubernetes, and exposes a full REST API, webhooks, and an official CLI ('tea') for scripting — all enabling headless/CI automation. Community evidence corroborates smooth Docker-based headless deployments on small VPS/servers. Missing for 10: an explicit first-party guide on running Gitea itself as an ephemeral CI service/container, and independent hands-on proof of automated CI orchestration beyond deployment reports.
- [claimed-docs] “It can be easily deployed on various servers without complex configurations or dependencies.”
- [claimed-docs] “Universally compatible with diverse operating systems and environments, including Linux, Windows, macOS, FreeBSD, and Kubernetes. Compatible…”
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [probe] “official CLI documented at https://gitea.com/gitea/tea”
- [community] “Used Gitea (previously Gogs) for a team of 45; setup with Docker was smooth and worked easily with Certbot, but documentation is lacking (ha…”
- [community] “Put Gitea on a $5 VPS for personal projects; works great, though unsure how secure it is if exposed publicly (uses SSH port-forwarding inste…”
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.”
Giteanone0/10The story asks whether Gitea itself can consume external MCP servers' tools (client-side), but the only MCP-related evidence shows Gitea publishing its own MCP server (gitea-mcp) for others to call into Gitea, not Gitea invoking outside MCP tools. No evidence of Gitea acting as an MCP client or integrating third-party MCP servers into its workflows.
- [probe] “official MCP server documented at https://gitea.com/gitea/gitea-mcp”
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 Gitea MCP server repository (gitea/gitea-mcp) that would let AI agents connect to Gitea, and Gitea is not itself an agent product so the axis applies. Missing for 10: detailed docs on setup/configuration, independent hands-on validation, and tool/capability list exposed via MCP.
- [probe] “official MCP server documented at https://gitea.com/gitea/gitea-mcp”
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”
Gitea has an official CLI ('tea') documented, but the evidence pack gives no detail on AI-native features (scripting for agents, structured output, automation-friendly design) — it's just a generic CLI reference. missing for 10: documentation of AI-native/agentic use cases for the CLI, details on output formats or automation support, independent corroboration of CLI capabilities.
- [probe] “official CLI documented at https://gitea.com/gitea/tea”
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 …”
Gitea documents a public API and webhooks for building custom workflows, and third-party evidence confirms scriptable behavior (e.g., creating private repos via git push without UI/CLI), plus an official CLI (tea) exists. However, probes found no discoverable OpenAPI spec or llms.txt at the expected docs endpoints, and there's no first-party documentation snippet in the pack showing detailed API reference structure or auth flows. Missing for 10: verifiable OpenAPI/swagger spec discovery, llms.txt or AI-friendly docs, and independent hands-on confirmation of API usage beyond one anecdote.
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [community] “You can create a private repo without using the UI/CLI just by adding a git remote and pushing—Gitea auto-creates it as private.”
- [probe] “official CLI documented at https://gitea.com/gitea/tea”
- [probe] “PROBE llms.txt: HTTP 404 at https://docs.gitea.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.gitea.com/openapi.json, https://docs.gitea.com/swagger.json, https://docs.gitea.com/api…”
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.”
Gitea's docs mention general permission management/ACLs and an API for building custom workflows, which implies some capability to control access, but the evidence pack contains no explicit documentation of fine-grained/scoped personal access tokens or least-privilege credential issuance for agent use. Missing for 10: explicit docs on scoped API token creation, granular permission scopes for tokens, and any hands-on confirmation that an agent can be issued a least-privilege credential.
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [claimed-docs] “Gitea places a strong emphasis on security, offering features such as user permission management, access control lists, and more to ensure t…”
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.”
Giteanone0/10Gitea documents a general REST API and webhooks (gitea-docs-4) but no evidence of official client SDKs/libraries; OpenAPI/spec probes returned 404 (gitea-probe-2) and no llms.txt exists (gitea-probe-1). CLI (tea) and an MCP server exist but these are not SDKs for building integrations.
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [probe] “PROBE llms.txt: HTTP 404 at https://docs.gitea.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.gitea.com/openapi.json, https://docs.gitea.com/swagger.json, https://docs.gitea.com/api…”
ai-native userSubscribe to events via webhooks
weight 2 · round to GiteaGitLabnone0/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.
Gitea's docs explicitly mention webhooks as a way to extend functionality and create custom workflows, and Gitea is well-known for repo/issue/PR event webhooks, which is a mainstream Gitea feature referenced in official docs. missing for 10: detailed documentation of specific webhook event types/payloads, independent hands-on confirmation of webhook reliability, and any AI-specific integration examples.
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
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…”
Giteanone0/10No evidence of any AI-generated insights, summaries, or suggestions surfaced from Gitea's own data (e.g., code review AI, issue analysis, PR summarization). The MCP server exposes Gitea data to external agents but doesn't itself generate insights, and no other AI-native features are documented.
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…”
Gitea Actions (gitea-docs-2) provides CI/CD workflows that run autonomously in response to events/schedules, and webhooks/API (gitea-docs-4) allow further custom automations, both of which enable background automations without manual triggering. missing for 10: independent/hands-on corroboration of Actions running reliably at scale, and AI-specific orchestration examples.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
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…”
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”
Giteanone0/10No evidence Gitea itself exposes natural-language command interfaces; the CLI (tea) and API/webhooks are structured, not NL-based, and llms.txt/openapi probes returned 404s. Presence of an MCP server implies external agents could translate NL into API calls, but that is a separate integration axis, not Gitea natively supporting NL commands.
- [probe] “PROBE llms.txt: HTTP 404 at https://docs.gitea.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.gitea.com/openapi.json, https://docs.gitea.com/swagger.json, https://docs.gitea.com/api…”
- [probe] “official MCP server documented at https://gitea.com/gitea/gitea-mcp”
- [probe] “official CLI documented at https://gitea.com/gitea/tea”
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.”
Giteanone0/10While Gitea documents having an API (gitea-docs-4), the evidence pack shows no interactive API reference or runnable examples—probes for OpenAPI/Swagger specs at the docs site returned 404s, and no community or docs evidence mentions a Swagger UI or interactive playground.
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.gitea.com/openapi.json, https://docs.gitea.com/swagger.json, https://docs.gitea.com/api…”
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.”
Giteanone0/10Gitea's docs mention a generic 'API' for extending functionality (gitea-docs-4), but there is no evidence of a downloadable OpenAPI/Swagger spec; direct probes for openapi.json/swagger.json/llms.txt at the docs site all returned 404 (gitea-probe-1, gitea-probe-2). No first-party or community evidence confirms a machine-readable API spec is published.
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [probe] “PROBE llms.txt: HTTP 404 at https://docs.gitea.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.gitea.com/openapi.json, https://docs.gitea.com/swagger.json, https://docs.gitea.com/api…”
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]”
Giteanone0/10Evidence only shows generic API/webhook extensibility (gitea-docs-4) with no mention of API versioning scheme or a documented deprecation policy; probes for OpenAPI/llms.txt spec both 404 (gitea-probe-1, gitea-probe-2). A community report even describes a breaking change (1.17.0 reserved usernames) with maintainers dismissing concerns, further indicating no formalized deprecation process (gitea-comm-17).
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [probe] “PROBE llms.txt: HTTP 404 at https://docs.gitea.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.gitea.com/openapi.json, https://docs.gitea.com/swagger.json, https://docs.gitea.com/api…”
- [community] “Complaint about Gitea 1.17.0 breaking changes (e.g. reserving usernames) and maintainers allegedly ignoring valid concerns about email regex…”
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.”
Gitea exposes a REST API and webhooks (gitea-docs-4) and an official CLI 'tea' (gitea-probe-4) that could be scripted for bulk operations, but there is no direct evidence of built-in bulk-action features (e.g., multi-item issue/PR batch edits, bulk merges) or documentation describing bulk workflows for AI-native automation. missing for 10: explicit documentation or examples of bulk/batch operations across many items, evidence of API rate limits or batch endpoints suited for large-scale automation, and independent confirmation that CLI/API supports bulk operations at scale.
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [probe] “official CLI documented at https://gitea.com/gitea/tea”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to GiteaGitLab'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.”
Gitea Actions provides GitHub Actions-compatible YAML workflows that trigger automatically on repo events (push, PR, etc.), and webhooks/API allow custom automation rules to fire on additional events. This directly satisfies 'rules that trigger actions automatically on events.' Missing for 10: independent/hands-on corroboration of Actions triggers in practice, and any AI-native-specific tooling or examples (e.g., AI agent hooked to webhook events) beyond generic docs.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to GiteaGitLabnone0/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.
Gitea Actions is described as YAML-based and 'compatible with GitHub Actions,' which implies support for scheduled/cron workflow triggers since that's a core GitHub Actions feature, but no citation explicitly confirms a 'schedule' event trigger or documents recurring job scheduling. missing for 10: explicit documentation of cron/schedule triggers in Gitea Actions, hands-on confirmation from users running recurring workflows, and details on any limitations vs GitHub Actions' scheduling.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
ai-native userVersion, review, and roll back my automations
weight 1 · round to GiteaGitLab'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.”
Gitea Actions workflows are YAML files stored in-repo, so they inherit full git history, branch/PR review, and revert capability like any other code (gitea-docs-1, gitea-docs-2, gitea-docs-3). This gives version control, review via pull requests, and rollback via git history for automation definitions, though Gitea provides no automation-specific rollback UI or workflow-run diffing beyond generic git tooling. Missing for 10: dedicated workflow versioning/rollback UI (e.g. one-click revert of a workflow run), independent hands-on confirmation of rolling back Actions specifically, and clarity on whether workflow run history itself (not just definitions) is preserved/reversible.
- [claimed-docs] “Gitea supports creating and managing repositories, browsing commit history and code files, reviewing and merging code submissions, managing …”
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [claimed-docs] “Code review supports both the Pull Request workflow and AGit workflow. Reviewers can browse code online and provide review comments or feedb…”
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.”
Gitea Actions provides GitHub Actions-compatible YAML workflows and reuses the Actions ecosystem, which supports building deployment pipelines, and its API/webhooks allow custom deployment automation. However, evidence lacks specifics on deployment-oriented features like environments, secrets management, or runner scaling, and community evidence mostly shows pairing Gitea with an external CI tool (Drone) rather than using Actions itself for deployment. Missing for 10: concrete deployment pipeline examples, environment/secrets support details, independent corroboration of Actions-based deployment success.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [community] “Using Gitea + Drone for several years: stable, fast, and doesn't consume a lot of RAM.”
devops-leadMap incidents to deployments and require change approval before releases
weight 1 · round drawnGitLabnone0/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.
Giteanone0/10Evidence shows Gitea's PR/code review workflow and Actions CI/CD, but nothing about mapping incidents to deployments or requiring formal change-approval gates before releases (e.g., no incident tracking integration, no deployment-approval workflow beyond generic branch protection mentions). This capability is a fair ask for a CI/CD platform but is simply unevidenced here.
Pipeline authoring
developerReuse community-built CI/CD actions or plugins in my pipelines
weight 2 · round to GiteaEvidence 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.”
Gitea Actions is explicitly documented as GitHub Actions-compatible, using standard YAML workflows and allowing reuse of existing Actions plugins from the ecosystem, directly matching the story. Missing for 10: independent hands-on confirmation of reusing specific community actions and marketplace-scale ecosystem evidence beyond vendor docs.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
developerDefine CI/CD pipelines as code using a YAML syntax
weight 3 · round to GiteaEvidence 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…”
Gitea Actions explicitly supports CI/CD pipelines defined in YAML, compatible with GitHub Actions syntax, and Gitea+CI (Drone/Actions) usage is corroborated by community reports. missing for 10: independent hands-on validation specifically of Gitea Actions YAML syntax (most community evidence discusses Drone as external CI rather than native Actions).
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [community] “Using Gitea + Drone for several years: stable, fast, and doesn't consume a lot of RAM.”
Runners
devops-leadRun CI/CD jobs on runners hosted by the platform without managing infrastructure
weight 3 · round to GitLabThe 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…”
Giteanone0/10Gitea Actions (gitea-docs-2) provides CI/CD workflow support compatible with GitHub Actions syntax, but Gitea is self-hosted software and the evidence never mentions a Gitea-operated hosted runner fleet — users must deploy and manage their own runners as part of self-hosting Gitea. No evidence of a managed/SaaS runner offering exists in this pack.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
devops-leadGet centralized visibility into CI/CD workflow runs across the organization
weight 2 · round to GitLabEvidence 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.”
Gitea Actions provides CI/CD workflow execution compatible with GitHub Actions syntax (gitea-docs-2), which is the prerequisite for any visibility into pipeline runs, and community reports confirm real-world CI usage via Gitea+Drone or Actions (gitea-comm-8). However, the evidence pack contains no mention of an organization-wide dashboard or aggregated view across repos' Actions runs — only per-repo Actions functionality is documented. Missing for 10: evidence of a centralized/org-level CI dashboard, cross-repo run aggregation, notifications rollup, or reporting APIs for workflow status across an organization.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [community] “Using Gitea + Drone for several years: stable, fast, and doesn't consume a lot of RAM.”
devops-leadRun CI/CD jobs on my own self-hosted or private runners
weight 2 · round to GiteaGitLabnone0/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.”
Gitea Actions is documented as a native CI/CD system compatible with GitHub Actions YAML workflows, which by design runs on self-hosted runners since Gitea itself is self-hosted (gitea-docs-2). However, the evidence pack lacks explicit runner registration/configuration details, and community reports show long-time Gitea users relying on external CI tools like Drone rather than native Actions (gitea-comm-8, gitea-comm-14), suggesting the built-in CI/CD runner feature is newer/less proven in practice. missing for 10: explicit runner setup/registration docs, hands-on confirmation of self-hosted runner reliability, independent corroboration beyond vendor docs.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [community] “Using Gitea + Drone for several years: stable, fast, and doesn't consume a lot of RAM.”
- [community] “Migrated from self-hosted Gitlab to Gitea, Nexus and Drone because maintaining Gitlab's size/complexity was too cumbersome; Gitea's UI is a …”
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 to GiteaGitLabnone0/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.
Gitea's own marketing explicitly claims syncing with Slack, Discord, MS Teams, Lark via webhooks/integrations, but this is only vendor-stated with no independent/hands-on corroboration of notification sync working in practice. missing for 10: hands-on/community verification of chat notification sync, details on which events sync (issues, PRs, activity) and any setup limitations.
- [claimed-docs] “Sync seamlessly with tools like Slack, Discord, MS Teams, Lark, and more.”
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
External ci cd integration
devops-leadConnect the platform to external CI/CD tools instead of using its native pipelines
weight 1 · round to GiteaGitLabnone0/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 …”
Gitea exposes webhooks and a full API explicitly for building custom workflows/integrations, and real-world users confirm pairing Gitea with external CI systems like Drone for years as an alternative to native Actions. This shows the platform is commonly used with third-party CI/CD tools rather than being locked into its own pipeline system. Missing for 10: dedicated first-party documentation on integrating specific external CI/CD tools (e.g. Jenkins, CircleCI) and more than one independent corroborating source.
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [community] “Using Gitea + Drone for several years: stable, fast, and doesn't consume a lot of RAM.”
- [community] “Migrated from self-hosted Gitlab to Gitea, Nexus and Drone because maintaining Gitlab's size/complexity was too cumbersome; Gitea's UI is a …”
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.”
Gitea supports extensibility via Actions (reusing GitHub Actions-compatible plugins), API/webhooks, and package registries, but there's no evidence of a curated marketplace for third-party apps or AI models specifically. missing for 10: a dedicated marketplace/app store UI, AI model integrations or marketplace, curated third-party app listings, and independent confirmation of ecosystem breadth.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [claimed-docs] “Gitea supports over 20 different types of public or private software package management, including Cargo, Chef, Composer, Conan, Conda, Cont…”
- [probe] “official MCP server documented at https://gitea.com/gitea/gitea-mcp”
- [probe] “official CLI documented at https://gitea.com/gitea/tea”
Security tool integrations
devops-leadInstall third-party security scanning integrations directly from a security tab
weight 1 · round drawnGitLabnone0/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.”
Governance — stories about governance in this arenaGovernance
Stories about governance in this arena
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”
Giteanone0/10The evidence pack covers Gitea's own feature docs (repos, CI/CD, issues, packages) but contains no mention of built-in tutorials, guides, or learning resources for the Git VCS itself. This is a plausible axis for a git hosting platform, but no evidence shows Gitea provides such educational content.
Policy enforcement
devops-leadRequire automated change approval workflows before code reaches production
weight 1 · round to GiteaGitLab'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”
Gitea's docs confirm a pull-request based code review workflow with reviewer comments and Actions-based CI/CD that could gate merges, giving the building blocks for an approval gate, but the evidence pack never documents branch-protection rules requiring N approvals or status checks before merge, which is the core mechanism for enforced pre-production approval. missing for 10: explicit branch-protection/required-reviewer-approval documentation, evidence of blocking merge until CI passes, independent confirmation the workflow is enforced in practice.
- [claimed-docs] “Code review supports both the Pull Request workflow and AGit workflow. Reviewers can browse code online and provide review comments or feedb…”
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [claimed-docs] “Gitea places a strong emphasis on security, offering features such as user permission management, access control lists, and more to ensure t…”
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.”
Gitea provides building blocks for governance—Actions-based CI/CD (gitea-docs-2), permission management and ACLs (gitea-docs-7), and PR-based code review workflows (gitea-docs-3)—plus API/webhooks for custom policy automation (gitea-docs-4). However, there's no direct evidence of org-wide branch protection templates, mandatory status-check enforcement across all repos, or centralized policy dashboards that a devops-lead would use to enforce standards uniformly; community feedback also notes scaling pain points once organizations grow (gitea-comm-13, gitea-comm-15). Missing for 10: explicit branch-protection/required-checks documentation, organization-wide policy templates, and independent evidence of successful multi-team governance enforcement.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [claimed-docs] “Gitea places a strong emphasis on security, offering features such as user permission management, access control lists, and more to ensure t…”
- [claimed-docs] “Code review supports both the Pull Request workflow and AGit workflow. Reviewers can browse code online and provide review comments or feedb…”
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [community] “Gitea is fine for a one-man show or small company, but once you scale up you start hitting various issues and wish for GitHub again.”
- [community] “At a startup using self-hosted Gitea without dedicated DevOps required extra maintenance; during SOC-2 audits it was much easier to justify …”
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/”
Gitea is documented as having a general-purpose API and webhooks for custom workflows (gitea-docs-4), and community evidence shows some UI-equivalent actions (e.g., creating a private repo purely via git push) work outside the UI (gitea-comm-10). However, there is no evidence of a comprehensive, discoverable API spec (openapi/swagger probes 404'd) or explicit documentation confirming parity across all UI features (Actions, Packages, Issues, etc.). Missing for 10: a published OpenAPI/swagger reference, explicit parity claims/documentation, and evidence that CI/CD, package management, and project boards are fully API-accessible.
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [community] “You can create a private repo without using the UI/CLI just by adding a git remote and pushing—Gitea auto-creates it as private.”
- [probe] “PROBE llms.txt: HTTP 404 at https://docs.gitea.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.gitea.com/openapi.json, https://docs.gitea.com/swagger.json, https://docs.gitea.com/api…”
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 …”
As self-hosted, open-source software, Gitea inherently stores data in open git format and gives full server access, which supports 'exporting and leaving,' and it exposes an API for programmatic extraction (gitea-docs-4). However, there is no explicit documented data-export/portability feature, and community reports specifically flag that Gitea's backup-and-restore mechanism is not good and that importing/migrating repos was surprisingly difficult, undercutting confidence in a clean full data exit. Missing for 10: explicit documented full-instance export tool, verified backup/restore reliability, and independent confirmation of smooth migration away from Gitea.
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
- [community] “Complaint about Gitea's backup and restore mechanism reportedly still not being good, cited as a blocker for migrating from Gogs.”
- [community] “Last time I tried Gitea, migrating existing git repos into it was surprisingly difficult.”
ai-native userRead the product's source under an open license
weight 2 · round to GiteaGitLabnone0/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.
Community evidence strongly implies Gitea is an open, publicly forkable codebase (it forked from Gogs, has public GitHub stars, and its internal codebase/architecture is openly critiqued by outsiders), but no evidence pack item explicitly states the license or links to the source repository/license file. missing for 10: explicit license documentation, direct source repo link, first-party confirmation of open-source status.
- [community] “Comparison of GitHub stats: Gogs had 24,564 stars vs Gitea's 5,971, and Gogs' README listed a much more thorough features list; Gogs looked …”
- [community] “Critique: Gitea's codebase has issues—migrations lack 'down' support, uses nonstandard go-macaron framework, too much logic in Go templates,…”
- [community] “Gogs, which Gitea forked from, works just as well, has no clear technical advantage in the fork, and had far more GitHub stars, questioning …”
ai-native userSelf-host the core product
weight 3 · round drawnGitLab'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…”
Gitea is explicitly designed for self-hosting, with docs confirming easy deployment across OS/architectures (Linux, Windows, macOS, FreeBSD, Kubernetes, x86/arm64) without complex dependencies, and this is heavily corroborated by numerous independent hands-on community reports of running Gitea in production (single binary, Docker, low RAM footprint, VPS deployments, migrations from GitLab/Gogs) across small teams and personal projects. Missing for 10: some community reports note documentation gaps, backup/restore weaknesses, and scaling friction that mildly complicate the self-hosting story at larger scale.
- [claimed-docs] “It can be easily deployed on various servers without complex configurations or dependencies.”
- [claimed-docs] “Universally compatible with diverse operating systems and environments, including Linux, Windows, macOS, FreeBSD, and Kubernetes. Compatible…”
- [community] “Used Gitea to deploy a Git server for 8 users; much simpler than a full Gitlab instance, just one binary to run, and users found the GitHub-…”
- [community] “Used Gitea (previously Gogs) for a team of 45; setup with Docker was smooth and worked easily with Certbot, but documentation is lacking (ha…”
- [community] “Put Gitea on a $5 VPS for personal projects; works great, though unsure how secure it is if exposed publicly (uses SSH port-forwarding inste…”
- [community] “Using Gitea + Drone for several years: stable, fast, and doesn't consume a lot of RAM.”
- [community] “Migrated from self-hosted Gitlab to Gitea, Nexus and Drone because maintaining Gitlab's size/complexity was too cumbersome; Gitea's UI is a …”
- [community] “Gitea performs well even on slow, low-resource computers (e.g. Atom x7-E3950 with 16GB RAM), unlike Gitlab which struggles on the same hardw…”
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 GiteaEvidence 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.”
Gitea is self-hosted software deployable on any server, OS, or cloud region a user chooses (Linux/Windows/macOS/FreeBSD/Kubernetes, easy deployment without complex config), which inherently gives full control over where data resides; community evidence confirms real-world self-hosting on VPS, Docker, and on-prem hardware. Missing for 10: explicit documentation addressing data residency/compliance framing (e.g., GDPR region controls) or multi-region replication features beyond generic self-host deployability.
- [claimed-docs] “It can be easily deployed on various servers without complex configurations or dependencies.”
- [claimed-docs] “Universally compatible with diverse operating systems and environments, including Linux, Windows, macOS, FreeBSD, and Kubernetes. Compatible…”
- [community] “Used Gitea to deploy a Git server for 8 users; much simpler than a full Gitlab instance, just one binary to run, and users found the GitHub-…”
- [community] “Put Gitea on a $5 VPS for personal projects; works great, though unsure how secure it is if exposed publicly (uses SSH port-forwarding inste…”
- [community] “Migrated from self-hosted Gitlab to Gitea, Nexus and Drone because maintaining Gitlab's size/complexity was too cumbersome; Gitea's UI is a …”
ai-native userPrevent my data from being used to train AI models
weight 3 · round to GiteaGitLabnone0/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.
Gitea is self-hosted software (deployable on your own servers, docs-9/docs-10), which inherently means no vendor cloud service ingests your repository data for AI training since Gitea itself doesn't host your data. However, there is no explicit privacy policy, documentation, or setting addressing AI/ML training data usage, nor any statement about third-party AI integrations respecting this. missing for 10: explicit documentation or policy on AI training data usage, any built-in opt-out/control mechanism, confirmation that bundled features (e.g. any AI-assisted tooling) don't train on repo data.
- [claimed-docs] “It can be easily deployed on various servers without complex configurations or dependencies.”
- [claimed-docs] “Universally compatible with diverse operating systems and environments, including Linux, Windows, macOS, FreeBSD, and Kubernetes. Compatible…”
ai-native userControl data retention and deletion
weight 2 · round to GiteaGitLabnone0/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.
Gitea being self-hosted implies the operator controls their own data and infrastructure, and gitea-docs-7 mentions access control and security features, but no evidence explicitly documents data retention policies, repository/account deletion mechanisms, or audit-log retention controls. missing for 10: explicit documentation of data deletion/export features, retention policy settings, GDPR-style data controls.
- [claimed-docs] “Gitea places a strong emphasis on security, offering features such as user permission management, access control lists, and more to ensure t…”
- [claimed-docs] “It can be easily deployed on various servers without complex configurations or dependencies.”
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 drawnGitLabnone0/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.
developerAutomatically update linked issue tracker statuses by referencing issue keys in my commits
weight 2 · round drawnGitLabnone0/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.
Giteanone0/10The evidence pack confirms Gitea's issue tracking capabilities (branches, tags, milestones, dependencies) but contains no documentation or community report of automatically closing/updating issue status via commit message keywords (e.g., 'fixes #123'), which is the specific capability the story asks about.
Issue tracking
developerTrack requirements, features, and bugs using issues with milestones, time tracking, and dependencies
weight 3 · round to GiteaGitLabnone0/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 …”
gitea-docs-6 directly confirms issues with milestones, time tracking, due dates, and dependencies for tracking requirements/features/bugs, matching the story closely. Missing for 10: independent hands-on corroboration of these specific project-planning features (community evidence focuses on performance/resource usage, not issue tracking depth).
- [claimed-docs] “Gitea tracks project requirements, features, and bugs through columns and issues. Issues support features like branches, tags, milestones, a…”
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.
Giteanone0/10Evidence confirms Gitea has project/task tracking via issues, columns, assignments, milestones (gitea-docs-6), but there is no evidence of a mobile app, mobile-optimized web UI, or any mobile-specific access path for managing projects or assigning tasks.
- [claimed-docs] “Gitea tracks project requirements, features, and bugs through columns and issues. Issues support features like branches, tags, milestones, a…”
developerOrganize work from high-level roadmaps to everyday tasks using project boards
weight 2 · round to GiteaGitLabnone0/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.”
Docs confirm Gitea has kanban-style project boards with columns/issues supporting milestones, due dates, dependencies, and time tracking, which covers day-to-day task organization, but there's no evidence of higher-level roadmap features (e.g., cross-repo project views, roadmap timelines) or any community validation of using boards for roadmap planning. Missing for 10: evidence of roadmap/timeline views, cross-project or organization-level board hierarchy, and independent/hands-on confirmation of the project board feature in practice.
- [claimed-docs] “Gitea tracks project requirements, features, and bugs through columns and issues. Issues support features like branches, tags, milestones, a…”
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.”
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.”
Giteanone0/10No evidence Gitea supports assigning AI reviewers or automated AI-based PR review; docs only mention human reviewer workflows (PR/AGit review, comments) and general API/webhook extensibility, with no AI reviewer integration or feature documented.
- [claimed-docs] “Code review supports both the Pull Request workflow and AGit workflow. Reviewers can browse code online and provide review comments or feedb…”
- [claimed-docs] “Extend Gitea's functionality with our API and webhooks, creating custom workflows to match your unique needs.”
developerReview code changes online and respond to inline review comments
weight 3 · round to GiteaThe 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…”
Gitea docs explicitly confirm PR-based code review with online code browsing and inline review comments/feedback (gitea-docs-3), backed by broader repo/collaboration docs (gitea-docs-1). However, there's no independent/hands-on evidence specifically validating the inline comment reply/thread experience, and community evidence focuses on other aspects (performance, deployment) rather than review UX quality. Missing for 10: independent corroboration of inline comment threading/resolution workflow, detail on review approval states, and hands-on account of the review UI experience.
- [claimed-docs] “Code review supports both the Pull Request workflow and AGit workflow. Reviewers can browse code online and provide review comments or feedb…”
- [claimed-docs] “Gitea supports creating and managing repositories, browsing commit history and code files, reviewing and merging code submissions, managing …”
developerReview large diffs and view third-party code quality reports directly in the review screen
weight 2 · round to GitLabGitLab 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.”
Gitea's docs confirm online code review with PR/AGit workflows and inline comments (diff review), but there is no evidence of built-in or first-party support for displaying third-party code quality reports (e.g., linting/coverage/security scan annotations) directly in the review screen. Missing for 10: documentation of large-diff handling/optimizations, and any integration surfacing third-party code quality report annotations in the PR diff view.
- [claimed-docs] “Code review supports both the Pull Request workflow and AGit workflow. Reviewers can browse code online and provide review comments or feedb…”
- [claimed-docs] “Gitea supports creating and managing repositories, browsing commit history and code files, reviewing and merging code submissions, managing …”
devops-leadEnforce standardized, customizable merge checks before code can be merged
weight 2 · round to GitLabEvidence 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.”
Gitea's docs show pull-request based code review, CI/CD via Actions, and permission/ACL controls—building blocks for merge gating—but the evidence pack never mentions explicit branch-protection rules, required status checks, or required-approval enforcement that would let a devops-lead standardize and customize merge checks. Missing for 10: explicit branch protection/required status check documentation, evidence of enforceable required reviewers before merge, and independent confirmation these gates actually block merges in practice.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [claimed-docs] “Code review supports both the Pull Request workflow and AGit workflow. Reviewers can browse code online and provide review comments or feedb…”
- [claimed-docs] “Gitea places a strong emphasis on security, offering features such as user permission management, access control lists, and more to ensure t…”
Package registry
open-source-maintainerPublish and consume software packages in multiple package formats from the same platform
weight 2 · round to GiteaGitLabnone0/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.
Gitea's docs explicitly state built-in package registry support for over 20 formats (Cargo, npm, Maven, PyPI, Container, Helm, NuGet, RubyGems, etc.) hosted natively on the same platform as repos, PRs, and issues, enabling maintainers to publish/consume packages without a separate tool. missing for 10: no independent/hands-on community confirmation of the package registry feature in the evidence pack, and no detail on publish/consume workflow specifics.
- [claimed-docs] “Gitea supports over 20 different types of public or private software package management, including Cargo, Chef, Composer, Conan, Conda, Cont…”
Repo management
devops-leadControl granular access permissions at the workspace, project, repository, and branch level
weight 2 · round to GiteaEvidence 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”
Gitea docs mention repository/collaborator management, user permission management, and access control lists, implying repo- and branch-level access control is possible, but there's no explicit documentation of workspace/project-level granular permission hierarchies or branch protection rules in the evidence pack. missing for 10: explicit docs on organization/team permission scoping, branch protection rule configuration, and any independent verification of granular access control working as described.
- [claimed-docs] “Gitea places a strong emphasis on security, offering features such as user permission management, access control lists, and more to ensure t…”
- [claimed-docs] “Gitea supports creating and managing repositories, browsing commit history and code files, reviewing and merging code submissions, managing …”
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…”
Giteanone0/10The evidence pack covers repo creation, commit browsing, code review, packages, issues, and security, but no citation explicitly documents a code/file/commit search feature across repositories. Missing for 10: any documentation or community mention of a search function, its scope (code/file/commit), or its limitations.
developerCreate and manage Git repositories and browse their commit history
weight 3 · round drawnGitLab 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 …”
Gitea's core purpose is Git repo hosting with commit history browsing, code review, and branch management, confirmed by first-party docs and corroborated by extensive hands-on community use (self-hosting for teams, private repo creation, browsing). One minor gap noted by a hands-on report: browsing commit history/Activity on large repos can be slow due to lack of caching. missing for 10: independent benchmark confirming commit history browsing performance at scale, deeper detail on repo creation workflow.
- [claimed-docs] “Gitea supports creating and managing repositories, browsing commit history and code files, reviewing and merging code submissions, managing …”
- [claimed-docs] “Code review supports both the Pull Request workflow and AGit workflow. Reviewers can browse code online and provide review comments or feedb…”
- [community] “Used Gitea to deploy a Git server for 8 users; much simpler than a full Gitlab instance, just one binary to run, and users found the GitHub-…”
- [community] “You can create a private repo without using the UI/CLI just by adding a git remote and pushing—Gitea auto-creates it as private.”
- [community] “Used the 'Try Gitea' service to load a large repo's Activity tab for a 1-year period; page load took nearly 90 seconds with no caching, sugg…”
developerPropose, discuss, and merge code changes using a pull or merge request workflow
weight 3 · round to GiteaMerge 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 …”
Gitea docs explicitly describe pull request workflow with code review, comments, and AGit workflow support, alongside repo management and merging (gitea-docs-1, gitea-docs-3). Community evidence corroborates real-world usage of Gitea as a git hosting platform for collaboration. Missing for 10: independent hands-on account specifically describing PR review/merge experience (most community evidence focuses on resource usage/ops rather than PR workflow specifics).
- [claimed-docs] “Gitea supports creating and managing repositories, browsing commit history and code files, reviewing and merging code submissions, managing …”
- [claimed-docs] “Code review supports both the Pull Request workflow and AGit workflow. Reviewers can browse code online and provide review comments or feedb…”
- [claimed-docs] “Gitea tracks project requirements, features, and bugs through columns and issues. Issues support features like branches, tags, milestones, a…”
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 drawnGitLabnone0/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.
Giteanone0/10No evidence of IP allow/deny-listing or CIDR-based repository access restriction; docs mention only user permission management and access control lists generically, without any IP-based restriction feature documented or discussed in community threads.
- [claimed-docs] “Gitea places a strong emphasis on security, offering features such as user permission management, access control lists, and more to ensure t…”
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.”
Giteanone0/10The evidence pack mentions general security/access-control features (gitea-docs-7) and API/webhook extensibility (gitea-docs-4) but never specifically describes personal access token generation or management. Missing for 10: explicit documentation or community confirmation of PAT creation/management UI or API endpoints.
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.”
Giteanone0/10The evidence pack contains no documentation or community confirmation of Gitea's SSH key management/authentication feature; only a tangential community mention of using SSH port-forwarding (not key setup) appears. Missing for 10: any docs on adding/generating SSH keys, key-based git push/pull authentication, or admin-side SSH config.
developerSecure my account with two-factor authentication
weight 3 · round drawnGitLabnone0/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.
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.”
Giteanone0/10No evidence of any AI-driven vulnerability detection or automated fix generation/application in Gitea; it offers permission management and ACLs but no security scanning or AI remediation features are documented.
- [claimed-docs] “Gitea places a strong emphasis on security, offering features such as user permission management, access control lists, and more to ensure t…”
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…”
Giteanone0/10No evidence of a Dependabot-like automated dependency-vulnerability scanning/update feature that opens pull requests; Gitea's evidence covers package registry hosting, CI/CD via Actions, and code review, but nothing about automated dependency vulnerability detection or auto-generated PRs to bump vulnerable dependencies.
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.”
Giteanone0/10Gitea's evidence covers repo hosting, CI/CD via Actions, code review, packages, and access control, but there is no mention of built-in SAST, dependency/SCA scanning, secret scanning, or DAST features, and community evidence explicitly notes Gitea 'deliberately stays focused on git hosting rather than bundling CI/chat like Gitlab' (gitea-comm-5), implying it does not bundle a security scanning suite like GitLab's.
- [claimed-docs] “Gitea Actions supports CI/CD functionality, compatible with GitHub Actions. Users can write workflows in familiar YAML format and reuse a va…”
- [claimed-docs] “Gitea places a strong emphasis on security, offering features such as user permission management, access control lists, and more to ensure t…”
- [community] “Gitea kept OAuth2 support that Gogs dropped, and has more useful features than Gogs overall, but Gitea deliberately stays focused on git hos…”
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.”
Giteanone0/10No evidence of any secret-scanning, credential-detection, or leaked-secret remediation feature across repositories in Gitea's docs or community reports; only general permission/access-control security mentions (gitea-docs-7) which do not address secret detection.
- [claimed-docs] “Gitea places a strong emphasis on security, offering features such as user permission management, access control lists, and more to ensure t…”
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 GiteaGitLab 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.”
Gitea docs explicitly state cross-platform support for Linux, Windows, macOS, FreeBSD, and Kubernetes, plus multiple architectures (x86, arm64), and easy deployment without complex dependencies. Community evidence corroborates real-world Docker deployments and single-binary installs across varied low-resource hardware, confirming this in practice. missing for 10: independent verification of Windows/macOS/FreeBSD production usage beyond docs (community reports focus mostly on Linux/Docker deployments).
- [claimed-docs] “It can be easily deployed on various servers without complex configurations or dependencies.”
- [claimed-docs] “Universally compatible with diverse operating systems and environments, including Linux, Windows, macOS, FreeBSD, and Kubernetes. Compatible…”
- [community] “Used Gitea to deploy a Git server for 8 users; much simpler than a full Gitlab instance, just one binary to run, and users found the GitHub-…”
- [community] “Used Gitea (previously Gogs) for a team of 45; setup with Docker was smooth and worked easily with Certbot, but documentation is lacking (ha…”
- [community] “Gitea performs well even on slow, low-resource computers (e.g. Atom x7-E3950 with 16GB RAM), unlike Gitlab which struggles on the same hardw…”
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.”
Giteanone0/10No evidence in the pack of official reference architectures, HA/clustering guidance, or documented deployments supporting tens of thousands of users; community reports instead note performance issues at scale (slow Activity tab, wishing for GitHub 'once you scale up') rather than confirming large-scale reference architectures.
- [community] “Used the 'Try Gitea' service to load a large repo's Activity tab for a 1-year period; page load took nearly 90 seconds with no caching, sugg…”
- [community] “Gitea is fine for a one-man show or small company, but once you scale up you start hitting various issues and wish for GitHub again.”
- [community] “At a startup using self-hosted Gitea without dedicated DevOps required extra maintenance; during SOC-2 audits it was much easier to justify …”
devops-leadUse migration tooling to move my code and users from another platform or from self-hosted to cloud
weight 2 · round to GitLabCommunity 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.”
Giteanone0/10The evidence pack contains no vendor documentation describing dedicated migration tooling (e.g., importing from GitHub/GitLab/Bitbucket, bulk user import) for moving code and users from another platform or to a cloud instance. In fact, community reports directly contradict this capability: one user found migrating existing git repos into Gitea 'surprisingly difficult' [gitea-comm-16], and another cites Gitea's backup/restore mechanism as 'still not being good' and a blocker for migrating from Gogs [gitea-comm-20]. Missing for 10: any first-party migration/import documentation, evidence of successful cross-platform user/data migration, and independent confirmation the process works smoothly.
- [community] “Last time I tried Gitea, migrating existing git repos into it was surprisingly difficult.”
- [community] “Complaint about Gitea's backup and restore mechanism reportedly still not being good, cited as a blocker for migrating from Gogs.”
devops-leadInstall a self-managed instance of the platform without laborious configuration
weight 3 · round to GiteaGitLab 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.”
Docs claim easy deployment without complex configuration or dependencies, and multiple independent community reports corroborate simple single-binary/Docker setups, low resource needs, and successful small-to-mid scale deployments on limited hardware. Missing for 10: more detailed first-party install/config walkthrough evidence and resolution of community complaints about incomplete documentation.
- [claimed-docs] “It can be easily deployed on various servers without complex configurations or dependencies.”
- [claimed-docs] “Universally compatible with diverse operating systems and environments, including Linux, Windows, macOS, FreeBSD, and Kubernetes. Compatible…”
- [community] “Used Gitea to deploy a Git server for 8 users; much simpler than a full Gitlab instance, just one binary to run, and users found the GitHub-…”
- [community] “Used Gitea (previously Gogs) for a team of 45; setup with Docker was smooth and worked easily with Certbot, but documentation is lacking (ha…”
- [community] “Gitea is massively less resource hungry than Gitlab; a Gitlab install using 4 cores/8GB RAM/2.3TB disk still had backup rake tasks trigger O…”
- [community] “Using Gitea + Drone for several years: stable, fast, and doesn't consume a lot of RAM.”
- [community] “Migrated from self-hosted Gitlab to Gitea, Nexus and Drone because maintaining Gitlab's size/complexity was too cumbersome; Gitea's UI is a …”
- [community] “Gitea performs well even on slow, low-resource computers (e.g. Atom x7-E3950 with 16GB RAM), unlike Gitlab which struggles on the same hardw…”
Not comparable on these axes
ai-native userTest against a sandbox environment without touching production data
weight 1 · not comparableGitLabnone0/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.”
Gitean/aGitea is a self-hosted git hosting/CI platform, not an AI agent testing tool; the concept of a 'sandbox environment vs production data' for AI-native testing is not a fit axis for this product category. Users could self-host separate instances, but no evidence frames this as a sandbox testing feature.
developerLaunch a ready-to-code cloud-based development environment in seconds
weight 2 · not comparableGitLabnone0/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.
devops-leadMake a single annual commitment and flexibly allocate spend across seat-based and usage-based licensing
weight 1 · not comparablegitlab-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”