Gogs
by Gogs · Self-hosted Git service that runs from a single Go binary
BenchRank score
Screenshots of Gogs
Homepage
Overview
Gogs is a self-hosted Git service written in Go and shipped as an independent binary or a Docker container, for Linux, macOS, Windows and ARM systems. Its documentation covers installation, a configuration primer, reverse proxy and run-as-service setup, authentication, webhooks, Git LFS, custom templates and localisation.
- Best for
- Small teams or individuals self-hosting Git on modest hardware, including ARM boxes
- Pricing
- The captured pages show no prices; Gogs is described only as MIT-licensed open source that you host yourself.
- Runs on
- Self-hosted
Strengths and trade-offs
Strengths
- Installs as a single binary or a Docker container
- Runs on every platform the Go toolchain supports, including ARM
- Docs claim it starts on 64 MiB of RAM and a quarter vCPU
- MIT-licensed since 2014, with all source code public
Trade-offs
- You host, upgrade and secure the server yourself
- Reverse proxy, service setup and authentication are manual configuration
Pricing
Published plans and prices from Gogs’s own pricing page.
How this score is made up
Each dimension is scored out of 100 and combined into the headline score using fixed weights.
MCP support
Whether an agent can drive the product through the Model Context Protocol, and how much setup that takes.
Documentation
Publicly reachable docs — coverage, freshness, code samples and machine readability.
Agent friendliness
How readable the site is to an automated client: llms.txt, structured data, server-rendered content, crawler access.
Changelog
A public, dated record of what shipped and when — the clearest signal that a product is still alive.
Marketing site structure
Whether the site answers a buyer's questions: clear positioning, the pages that matter, and accessibility.
Page speed
How fast the site loads for real visitors: Chrome UX Report 75th-percentile LCP, INP and CLS, with a Lighthouse mobile run standing in where a site has too little traffic for field data.
Operational trust
Status page and incident history, security disclosure, compliance and data-processing documentation.
Measured, but not part of the score
Useful to know, but not a mark for or against the product — so these do not affect the ranking.
Openness
Source availability, self-hosting, data export and open standards. Scored and shown, but not part of the composite — paid SaaS is not worse for being paid SaaS.
Maintenance
Release cadence and repository activity. Scored and shown, but not part of the composite — it is only measurable for open repositories.
This doesn’t look right — report a problem with Gogs’s score
Where this comes from
The Gogs pages BenchRank reads when it scores the product — its documentation, release notes, status and security pages, and its repository where there is one.
Alternatives in Code Review
Ranked 2
52 — BenchRank score out of 100HackerOne Code
PullRequest · AI-filtered, human-validated security review in your pull requests
Best for: Development teams wanting expert human security review of pull requests inside their existing SCM.
Ranked 3
51.3 — BenchRank score out of 100Gitea
Gitea · Self-hosted Git, CI/CD and package hosting under the MIT licence
Best for: Teams that want to self-host Git, CI/CD and package registries on their own infrastructure.
Ranked 4
24 — BenchRank score out of 100Opengrep
Opengrep · Open-source static analysis engine forked from Semgrep CE
Best for: Security teams wanting an open-source SAST engine with no features locked behind a licence.
Is this your product?
Claim Gogs to manage its profile. Claiming lets you suggest edits to the descriptive fields — it never changes scores or rankings.