Gogs Hosting

How Gogs works

Gogs stores Git repositories behind a web interface where users can create projects, organise repositories, inspect activity, manage collaborators, and work through issues or pull requests. Protected branches, deploy keys, Git LFS, repository mirrors, migrations, wikis, and web editing extend the basic push-and-clone workflow.

Organisations group repositories and members, while webhooks connect repository events to supported external systems. The application supports several authentication and database backends upstream, but the catalogue package does not declare a PostgreSQL or MariaDB service, so the public hosting page treats the relational-database requirement as Not required.

Key Gogs features

The project deliberately targets a simple, stable, and extensible self-hosted Git service with a small footprint. Its interface covers common repository collaboration without presenting every function of a full DevSecOps suite. That makes it suitable for controlled teams whose main need is source hosting, review, and issue tracking.

Gogs documents SMTP-based authentication and notifications among optional capabilities. The hosted Gogs package has application email disabled, so email delivery, verification messages, notifications, and password recovery are unavailable. CI runners, deployment targets, external identity providers, and third-party webhook destinations are also separate services.

Gogs vs GitHub

Gogs provides a self-hosted Git service with repositories, organisations, issues, pull requests, wikis, protected branches, webhooks, mirrors, and LFS. GitHub is a provider-run development platform that combines repositories and code review with Issues, Projects, Actions, security products, a marketplace, and desktop, mobile, and command-line clients.

GitHub may suit teams that want maintained automation infrastructure, broad integrations, enterprise administration, and collaboration under a commercial account. Gogs is appealing when a small team values a focused server and is prepared to operate repository storage, access policy, backups, integrations, and any separate build system.

Who uses Gogs

Small engineering teams use Gogs for private repositories, review queues, issue tracking, documentation wikis, and mirrors of upstream projects. Agencies can separate customer work into organisations, while homelab operators may use it as a central Git remote for configuration and infrastructure code.

Gogs does not include hosted build minutes, a managed runner fleet, deployment environments, or the breadth of security and governance features found in larger commercial platforms. Repository growth, Git LFS objects, clone traffic, and concurrent operations should be monitored as the team expands.

Self-hosting Gogs: requirements and cost

Resource use is shaped by repository count and size, concurrent pushes and clones, pull-request activity, issue history, wikis, mirrors, webhooks, and Git LFS objects. The catalogue records PostgreSQL and MariaDB as Not required; repositories, configuration, application records, and uploaded data still need coordinated persistence and recovery.

On AvaHost, Gogs uses Plan 1 at €2. The hosted Gogs package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Application email is disabled, so mail notifications, verification, and email recovery are unavailable. Build runners, deployment infrastructure, external identity systems, LFS storage outside the plan, and webhook receiver services are not included.