Skip to content
SPECIFICTION
Get listed

GitLab Package Registry vs Gogs

GitLab Package Registry

docs.gitlab.com

Gogs

gogs.io

Side by side

FigureGitLab Package RegistryGogs
Price from$2.42/moFree
Free planYesYes
Free trialYes—
Open source——
WebYesYes
Windows—Yes
macOS—Yes
LinuxYesYes
APIYesYes
Self-hostedYesYes
Plans published31
Spec score · Git Hosting Services8.3 (#11)8.5 (#4)
Founded20112014
PurposeThe registry lets users publish and share packages that downstream projects can consume as dependencies.Gogs is a simple, stable, extensible self-hosted Git service.

Plans

GitLab Package Registry

  • FreeFree
  • Premium$29 a year
  • UltimatePriced on request

GitLab Package Registry pricing →

Gogs

  • GogsFree

Gogs pricing →

In their own words

GitLab Package Registry

GitLab Package Registry lets projects publish packages for downstream projects to use as dependencies. It can be private or public for supported package managers and is available on GitLab.com, GitLab Self-Managed, and GitLab Dedicated within Free, Premium, and Ultimate. Generally available formats include Generic packages, Helm, Maven, npm, NuGet, and PyPI; Composer and Conan are beta, while Debian, Go, and Ruby gems are experiments. Conda, CRAN, RPM, and Swift are not supported. A project can host multiple package types, including packages built from a monorepo. GitLab CI/CD can build or import packages, with jobs authenticating through CI_JOB_TOKEN, and the registry can be administered through an API. Project roles govern access; protection rules can restrict pushes or deletions for supported formats. Publication and deletion audit events are available when enabled, but require Premium or Ultimate. The dependency proxy is a beta feature on those paid tiers. GitLab is all-remote and has no physical headquarters.

Visit docs.gitlab.com

Gogs

Gogs has no write-up on Specifiction yet; its figures are above.

Visit gogs.io