Gogs

Host your own Git service painlessly with a single Go binary covering code hosting, browsing, collaboration and automation.

Source repo
gogs/gogs
Stars
★ 48k
Last updated
1d ago
License
MIT
Primary language
Go

At a glance

How it runs
Self-hosted service
Works with
Platform-specific
Cost
Free, no paid service needed
Setup effort
Medium · a few setup steps
You'll need
PostgreSQL, MySQL or SQLite3Docker (optional)Kubernetes (optional)Shell / CLINetwork accessLocal filesystem
Typical use
An individual developer who wants private Git hosting on a Raspberry Pi or a $5 cloud droplet.
Not a fit if
  • Teams that want zero-ops hosted code hosting instead of running their own server
  • Teams needing fully mature Actions or package hosting, which the README marks in development
Website
gogs.io ↗ set on GitHub
Maintenance
Commits in the last 30 dayslast commit 2026-11-20latest release v0.14.4 (2026-11-12)+5.7 ★/day over 7 days

What does this agent do, and when should you use it?

Gogs is a self-hosted Git service written in Go that aims to make setting up private code hosting as painless as possible. It ships as an independent binary for Linux, macOS, Windows and ARM systems, and also supports Docker and Kubernetes deployment. It covers Git over SSH and HTTP(S) with protocol v2, a built-in SSH server, SHA-256 repositories, deploy keys and LFS, in-browser code browsing and editing with blame and code search, rendered Markdown, Jupyter Notebooks, PDFs and Mermaid diagrams, plus Issues, Pull Requests, Wikis, releases and projects. Storage can be PostgreSQL, MySQL or SQLite3, and operations include OpenTelemetry tracing with a built-in trace viewer, Prometheus metrics and command-line backup and restore. The UI ships in over 31 languages with light and dark themes and a command palette, and it runs comfortably on modest hardware.

Gogs runs as a server process that reads Git repository data and exposes Git over SSH and HTTP(S) with protocol v2 plus a built-in SSH server, accepting pushes and maintaining repository state. It renders a web UI for browsing and editing code in the browser, viewing blame, and running code search within a repository or across all of them, and it renders Markdown, Jupyter Notebooks, PDFs and Mermaid diagrams. For collaboration it manages Issues with templates and forms, Pull Requests with merge commit, rebase and squash merges, protected branches, Wikis, releases and projects. For automation it provides webhooks for Slack, Discord, DingTalk and more, server-side Git hooks, and an experimental REST API. Operationally it writes to PostgreSQL, MySQL or SQLite3, emits OpenTelemetry traces with a built-in trace viewer and Prometheus metrics, and supports backup and restore from the command line.

  1. An individual developer who wants private Git hosting on a Raspberry Pi or a $5 cloud droplet.
  2. A small team needing Issues, Pull Requests, Wikis and code search in one internal code host.
  3. An organization that must keep code on its own network and sign users in via LDAP, PAM, OAuth 2.0 or SAML 2.0.
  4. An ops team that wants to deploy Git with Docker or Kubernetes and connect it to monitoring through Prometheus metrics and OpenTelemetry tracing.
  5. A team migrating repositories from another code host and setting up mirrors.

How do you install or deploy this agent?

The README does not provide step-by-step install commands; it states that the service can be delivered as an independent binary, via Docker, or on Kubernetes. It points to https://gogs.io for user documentation and suggests trying it online at https://try.gogs.io/gogs/gogs first. A PostgreSQL, MySQL or SQLite3 database is required. Exact download URLs, image names and startup flags are not present in the source and would need to be confirmed in the official docs.

How do you use this agent?

After deployment, open the web UI in a browser to manage repositories and collaborate through Issues and Pull Requests, navigating with the command palette. Integrations can be triggered through webhooks or server-side Git hooks; the API is an experimental REST interface documented at https://gogs.io/api-reference. Backup and restore run from the command line, though the specific subcommands are not listed in the source.

What are this agent's strengths and limitations?

Pros
  • A single Go binary distribution across Linux, macOS, Windows and ARM with a low footprint — a Raspberry Pi or 512MB RAM is enough to start.
  • Built-in SSH server plus Git protocol v2, SHA-256 repositories, deploy keys and LFS (local or S3).
  • Choice of PostgreSQL, MySQL or SQLite3, with binary, Docker and Kubernetes deployment paths.
  • Built-in OpenTelemetry tracing with a trace viewer, Prometheus metrics and command-line backup and restore for operational visibility.
  • UI localized into over 31 languages, with light and dark themes, a command palette and a mobile-friendly layout down to 375px.
Limitations
  • Actions, Packages, code owners, signed commits, inline reviews and SAML 2.0 are marked in development in the README, so production adoption needs a maturity check.
  • The REST API is still experimental, which carries interface stability risk.
  • You must provision and maintain your own database (PostgreSQL/MySQL/SQLite3) and server, which is real self-hosting overhead.
  • Installation steps are not included in the source and depend on external documentation, so first deployment details are incomplete.

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

Agent Source review Form / cost Stars Updated Language Full support on
Gogs This agent 56 · Major gaps Self-hosted serviceFree ★ 48k 1d ago Go —
Warren 78 · Good Self-hosted serviceFree + model costs ★ 521 6d ago TypeScript Claude Code
Kandev 74 · Some gaps CLIFree + model costs ★ 1.2k today Go Codex · Claude Code
Roamgate 66 · Some gaps CLIFree ★ 329 3d ago TypeScript —

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Major gaps
56/ 100 5-point scale 2.8 / 5
Trust 12/29
Reliability 9/14
Adaptability 9/18
Convention 13/18
Effectiveness 9/13
Verifiability 4/8
Why each dimension lost points
Trust12 / 29 · 2.1/5

Evidence shows this is a self-hosted Git service, not a least-privilege Agent product: AGENTS.md/CLAUDE.md grant broad capabilities (gh CLI, Chrome DevTools MCP, git push/PR) with no per-action confirmation, so least_privilege and user_confirmation score 1. On data flow, the react-doctor skill curls a remote playbook and runs npx react-doctor@latest, an unpinned remote code execution path, so data_flow_transparency and external_effects score 1. Sensitive data handling has partial strengths (SECRET_KEY refuses unsafe default, ${ENV} injection avoids plaintext), but LDAP Bind Password is stored plaintext and PAM needs /etc/shadow read access, both acknowledged in docs, so 1. Dependency security has pinned go.mod versions, trivy scanning in CI, and SHA-pinned actions, but no audit report, so 2. Rollback only mentions backup/restore commands in README without concrete procedure, so 1. Source attribution has LICENSE and acknowledgments, so 2.

Reliability9 / 14 · 3.2/5

self_consistency: AGENTS.md and CLAUDE.md match, README and install docs agree, so 2. dependency_availability: go.mod pins versions and CI covers multiple platforms and databases, so 2. failure_messages: troubleshooting doc gives concrete error text and fixes, main.go has FatalContext output, so 2; no full evidence of runtime error taxonomy, so not full marks.

Adaptability9 / 18 · 2.5/5

audience_and_scenarios: docs cover deployment, administration, and development, so 2. capability_boundaries: README marks in-development features with asterisks but boundaries are coarse, so 1. trigger_precision: skills trigger on /ghsa, /doctor commands with broad descriptions, so 1. environment_fit: explicitly supports Linux/macOS/Windows/ARM, multiple databases, Docker/K8s, so 2.

Convention13 / 18 · 3.6/5

install_notes are thorough (prerequisites, DB init, four install methods, config examples), so 3. license is full MIT text, so 3. information_architecture has layered docs and FAQ, so 2. naming_stability has version 0.15.0+dev and CHANGELOG reference, but CHANGELOG content not shown, so 2. examples_and_faq has FAQ and examples, so 2. known_limitations has asterisk markers and troubleshooting, so 2. versioning_changelog only references CHANGELOG.md without content, so 2. maintenance_responsibility: SECURITY.md states supported versions and process, but publisher identity is unverified, so 1.

Effectiveness9 / 13 · 3.5/5

output_usability: as a Git service product output is usable and docs directly guide deployment, so 2. marginal_value: self-hosted Git service has clear value but many competitors, so 2. cost_benefit: single binary, low hardware requirements, good cost-benefit, so 2; not executed, so not 3.

Verifiability4 / 8 · 2.5/5

claim_traceability: README makes many feature claims (Actions, Packages) marked in-development without corresponding code evidence, so 1. cross_source_corroboration: README, install docs, and CI workflows corroborate each other, so 2. fact_inference_separation: docs mix facts and vision without clear separation, so 1.

Risks and how to mitigate them
  • The react-doctor skill curls a remote playbook and runs npx react-doctor@latest, an unpinned remote code execution path; treat with caution.
  • LDAP Bind Password is stored plaintext and PAM auth requires reading /etc/shadow; restrict permissions when deploying.
  • AGENTS.md/CLAUDE.md grant broad capabilities (gh CLI, Chrome DevTools MCP, git push/PR) with no per-action confirmation.
  • README marks Actions, Packages, SAML and other features as in development; verify actual availability before production use.
  • Publisher identity is not verified by FollowAgents; confirm maintenance responsibility and update path independently.
Evidence confidence: Low Reviewed Nov 18, 2026 Reviewed revision 2ffed4d4a3fd New commits since this review; the score may not cover them
See the full review method →
Maintain this project? Add the FARS badge to your README

The badge shows the current review score and verdict and links back to this page. It refreshes about once an hour after a re-review.

FARS

[![FARS review](https://followagents.com/badge/gogs.svg)](https://followagents.com/en/agents/gogs)
<a href="https://followagents.com/en/agents/gogs"><img src="https://followagents.com/badge/gogs.svg" alt="FARS review"></a>

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

  1. v0.14.4
    Release notes excerpt
    Changed - Lowering [auth] ACTIVATE_CODE_LIVES or [auth] RESET_PASSWORD_CODE_LIVES now also shortens the lifetime of activation, email confirmation, and password reset links already sent. [#8478](https://github.com/gogs/gogs/pull/8478) Fixed - _Security:_ On Windows hosts, a user creating a repository with initial files or initializing its labels could read files on the server, including the configuration file. [#8488](https://github.com/gogs/gogs/pull/8488) - [GHSA-fv2v-vwmj-j74p](https://github.com/gogs/gogs/security/advisories/GHSA-fv2v-vwmj-j74p) …
    View on GitHub ↗
  2. v0.14.3 0.14.3
    Release notes excerpt
    ℹ️ Heads up! There is a new patch release [0.14.4](https://github.com/gogs/gogs/releases/tag/v0.14.4) available, we recommend directly installing or upgrading to that version. Fixed - _Security:_ Reverse proxy authentication header was honored from any remote address, allowing user impersonation when Gogs was reachable directly. The header is now only trusted from addresses listed in [auth] TRUSTED_PROXY_IPS. [#8264](https://github.com/gogs/gogs/pull/8264) - [GHSA-w6j9-vw59-27wv](https://github.com/gogs/gogs/security/advisories/GHSA-w6j9-vw59-27wv) …
    View on GitHub ↗
  3. v0.14.2 0.14.2

FAQ

Does Gogs cost anything?
No. It is released under the MIT License and can be self-hosted at no subscription cost.
What hardware do I need?
The README says a Raspberry Pi or a $5 DigitalOcean Droplet is more than enough to start, and 2 CPU cores with 512MB RAM is the baseline for teamwork; scale CPU cores as the team grows while memory stays low.
Which features are not yet production-ready?
Features marked with an asterisk as in development include GitHub two-way sync, code owners, signed commits, inline reviews, PR stacks, Actions, compute, Packages, hosting, SAML 2.0, OpenID Connect, session management, security alerts and breached password detection.
Which databases are supported?
PostgreSQL, MySQL and SQLite3.
Which browsers are supported?
Any modern browser, with Chrome 111, Edge 111, Firefox 128 and Safari 16.4 (including iOS) as the minimum versions.
Is Gogs open source?
Yes. The source code is on GitHub (gogs/gogs) under the MIT licence.
Is Gogs safe to use?
FollowAgents' FARS review (Nov 18, 2026) scored Gogs 12/29 on trust and safety. None of the eight safety controls the review checks for was missing outright. The repository has changed since that review.
Is Gogs still maintained?
Yes. The latest commit on GitHub is from 2026-11-20, within the last 30 days. The latest release is v0.14.4 (2026-11-12).
Who makes Gogs?
Gogs is published on GitHub by the account gogs. FollowAgents has not verified which person or company is behind that account.
What is Gogs's official website?
The project's GitHub repository lists https://gogs.io as its website. That link is set by the repository owner; the source code itself is on GitHub (gogs/gogs).
Was this page helpful?
View on GitHub ↗ Install ↓

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.

Related concepts