Skip to main content

Fully Managed Gogs
as a Service

Deploy Gogs as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Gogs is the original lightweight self-hosted Git server. Repositories, issues, pull requests, webhooks — the GitHub-style workflow without the hosted service. Written in Go, MIT-licensed since 2014, still shipping signed releases in 2026.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

Gogs

Gogs

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Gogs Preview Image

ABOUT THE SOFTWARE

What is Gogs

Gogs is a self-hosted Git service written in Go. Single binary, single config file, runs anywhere — from a Raspberry Pi to a production server. Repositories, issues, pull requests, webhooks, LDAP authentication, Git LFS. MIT-licensed since 2014, maintained by Unknwon (Joe Chen).

The project started in 2014 to give teams a GitHub-style workflow without the hosted service. The repository on GitHub stands at 48k stars and 5.1k forks. Releases are signed; the maintainer's key fingerprint is Nkwk3kNZpPN9sdNYYWWILtWOkaqCjfsMnd1cNGgg9GE. Cadence is security-driven.

Gogs deliberately stays small. No built-in CI runner, no package registry, no project boards. What it ships is the Git server, the web UI, and the integration hooks — clean. For teams that want CI, the standard pattern is a webhook to an external runner (Drone, Woodpecker, Jenkins). For teams that want everything in one binary, Gitea or Forgejo are the descended forks. Gogs's pitch is the smaller surface.

FEATURES

What Gogs does

Gogs ships the Git server and the web UI as one Go binary. Repositories with full Git over HTTP/SSH. Organizations, teams, issues, and pull requests with merge controls. Webhooks, mirrored repos, and LDAP/SMTP/PAM authentication. The features below are upstream Gogs capabilities — not DANIAN's platform layer.

Repositories and organizations

Public, private, and mirrored repos. Organizations group teams and apply permissions in bulk. Per-repo collaborator controls and branch protection on protected branches.

Git LFS for large files

LFS v2.5+ supported for binary assets — game art, design files, firmware images. SHA-256 hash verification on upload since v0.14.2.

LDAP and SMTP authentication

LDAP with both BindDN and simple-auth providers. SMTP, PAM, and reverse-proxy header auth supported. Mature against corporate directories.

Built-in code browser and search

Source viewer with syntax highlighting, blame, history. Per-repo search across files and commit messages. Markdown and Org-mode rendering.

Issues, milestones, and pull requests

Issue tracker with labels, milestones, and assignees. Pull requests with review approvals, merge controls (merge / squash / rebase), and conflict detection.

Webhooks and integrations

Built-in webhook formats for Gogs, Slack, and Discord. Standard JSON payload schema makes it straightforward to wire CI runners or chat.

Repository mirroring

Mirror an external Git repository on a fixed interval. Push mirrors and pull mirrors both supported. Useful for keeping a private copy of an upstream fork.

Multiple database backends

PostgreSQL, MySQL, MSSQL, TiDB, or SQLite. Production deployments use MySQL; the SQLite default is the documented hobby option.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Gogs

The move usually starts with a pricing event somewhere else. Bitbucket Cloud cut its free-plan workspace limit to 1 GB in May 2025. GitHub Copilot's training opt-out shifts to off-by-default for private-repo context on April 24, 2026. Both push asset-heavy and IP-sensitive teams toward self-hosted Git. Then the question is who runs it.

Running Gogs yourself isn't difficult — that's the project's whole point. Running it in production is a different exercise. The default install puts SQLite in a data directory. Gogs's in-process SSH server runs on port 22. Git LFS objects sit in a single global directory keyed only on Object ID. That layout works on day one. It stops working at month six. The first LFS overwrite incident. The first failed gogs backup restore. The first CVE that ships on a Friday.

We run Gogs the way the documentation tells you to run it in production. MySQL replaces the SQLite default. The built-in SSH server is off. System OpenSSH handles port 22; Gogs writes the git user's authorized_keys via the documented integration. Gogs's own Docker README is blunt: "Builtin SSH server is not recommended inside Docker Container." LFS lives on a snapshot-capable mount.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Gogs on DANIAN

Gogs's niche is small to mid-size teams that need the GitHub-style workflow without the hosted service. The three patterns we see most often: asset-heavy studios that hit free-tier limits on the proprietary platforms, education programs with per-cohort isolation requirements, and freelancers who want each client's code in its own org.

12-PERSON INDIE GAMEDEV STUDIO

Replacing Bitbucket Cloud after the May 2025 free-plan 1 GB cap

Germany region for low-latency binary push. Git LFS on a snapshot-capable mount for art and audio assets. Running v0.14.2 with LFS hash verification enforced. System OpenSSH on port 22, built-in SSH off. Webhook to a Drone CI runner that packages Steam build candidates. Trello kept for production tracking.

UNIVERSITY CS DEPARTMENT, ~80 STUDENTS PER SEMESTER

Per-course orgs with directory-bound logins for assignment grading

Netherlands region. LDAP BindDN against the department's Active Directory. Self-registration disabled, sign-in required to view repos. Per-course org pattern: one org per course code, instructor as admin, students invited at term start. Webhook from assignment repos fires an autograder on the department's Jenkins runner. Quarterly archive snapshots.

SOLO FREELANCE CONSULTANCY, ~25 CLIENT REPOS

One org per client, contractors added per engagement, revoked on handoff

Region nearest the operator. One Gogs organization per client; contractors invited per engagement and removed at handoff. Per-client webhooks point at each client's CI rather than the consultancy's. Built-in repository mirror keeps a private copy of any upstream fork. Nightly backup to client-isolated buckets via a restic script.

COMPARISON

Four ways to run Gogs

Most teams arrive at managed Gogs from one of three places. From GitHub Team, because the pricing math at 5+ users flips. From a homelab box that's gotten serious enough that downtime hurts. Or from a self-managed VPS running Gogs that eats an afternoon a month. Here's the math at common team sizes.

 PATHAT 1 USERAT 5 USERSAT 10 USERS WHAT'S ALSO ON THE BILLYOUR OPERATOR TIME
GitHub Team
(proprietary SaaS)
$4/mo$20/mo$40/mo+ $19–30/month per active committer for secret and code scanning (Advanced Security)Zero
Self-host
on a $24/month production-class VPS
$24/mo
+ your time
$24/mo
+ your time
$24/mo
+ your time
Backup storage, monitoring tools, certificate renewal1–2 hr/month patching, backups, on-call
Home server
(Synology DS923+, HP ProLiant ML30, business mini-PC)
€85–187/mo
all-in
€85–187/mo
all-in
€85–187/mo
all-in
Hardware amortised, electricity, business internet with static IP, off-site backup target, exposed home IP on every clone URL2–4 hr/month
DANIAN Managed Gogs€9/mo€9/mo€9/moNothing — backups, monitoring, SSL, patching, support all includedZero

Below 2 users, GitHub Team is cheaper on the headline price. At 3+ users the math flips; by 10+ it's not close. Non-price factors apply at every team size: Copilot training opt-out, included secret and code scanning, full export rights, custom domain, and no per-seat math as you grow.

BY INDUSTRY

Gogs for specific industries

These three industries put specific demands on a Git server that Gogs is well-suited for: tight IP custody, regional data control, and binary-asset workflows. None of them need the full social-platform surface of GitHub. All three benefit from the operational defaults DANIAN ships.

Firmware teams working on contracts that require source-code custody outside US-headquartered cloud platforms have an explicit decision to make about where Git lives. In June 2025 testimony at the French Senate's Commission of Inquiry, Microsoft France could not guarantee customer data would stay outside the reach of US authorities under the CLOUD Act. The exposure pattern extends to GitHub repos hosted on Microsoft Azure.

We run Gogs in the region you pick — Germany, France, Brazil, Singapore, Australia, etc — with daily incremental backups replicated to a second region. LDAP bound to your corporate directory; self-registration off. Firmware repos carry .hex and .bin artefacts in Git LFS on a snapshot-capable mount; a webhook fires on signed-tag push to a build runner.

Resource floor: Gogs runs on a 1 vCPU box per upstream's own positioning. The 2 vCPU / 4 GB instance we ship supports roughly 50 active contributors with headroom.
University CS departments and coding bootcamps run Gogs for a specific workflow shape: per-course organizations, directory-bound logins, and a hard stop on student work leaving the institution's infrastructure. Some jurisdictions add FERPA-adjacent considerations on educational records; others add student-data residency requirements.

We bind to the institution's LDAP or Active Directory using Gogs's documented ldap_bind_dn provider. Registration is disabled — accounts only appear via directory sync. Per-course org template: one organization per course code, instructor as admin, students invited at term start and archived at term end.

The autograding pattern: assignment template repo, forked per student, webhook on push to the department's Jenkins runner that runs the grading harness. Quarterly archive snapshots cover audit needs. Storage math: 80 students × 10 assignments × ~1 MB ≈ 800 MB per semester — comfortably under a small instance's footprint.
Independent game studios commonly hit two walls on hosted platforms: free-tier storage limits that bite once binary assets land in Git LFS, and publisher contracts that require source-code custody outside any third-party platform the studio doesn't fully control. The dated trigger: Bitbucket Cloud cut its free-plan workspace storage to 1 GB on May 29, 2025.

We run Gogs with Git LFS on a snapshot-capable mounted volume, sized to the studio's typical 20–80 GB combined source-plus-asset footprint. The release floor is v0.14.2 (LFS hash verification on uploads, post-CVE-2026-25921 patch). System OpenSSH on port 22, built-in SSH off.

The build pattern: webhook from a tagged release fires a CI runner (Drone, Woodpecker, or Jenkins) that pulls down assets via LFS and packages a Steam upload candidate. Asset directors keep their pipeline; the studio keeps its IP.

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

Carefully. Gogs stores LFS objects in a single global directory keyed by Object ID. Local filesystem only — no S3 backend in upstream (open feature request since April 2020). We put the LFS path on a snapshot-capable mount. We run v0.14.2 or newer (CVE-2026-25921 patched February 19, 2026). We back up the LFS directory alongside repos.
LDAP works well — both BindDN and simple-auth providers, mature against corporate directories. SMTP, PAM, and reverse-proxy header auth are supported. SAML is not implemented; the request has been open since April 2015. OAuth-as-provider is not first-class. For SAML or OIDC SSO, the standard pattern is to front Gogs with an authenticating reverse proxy — Authelia or oauth2-proxy.
MySQL for production. Gogs supports PostgreSQL, MySQL, MSSQL, TiDB, and SQLite. The default is SQLite, which is the documented hobby option — fine on a Raspberry Pi, not fine when you need point-in-time recovery, concurrent writes under load. We provision MySQL by default and dump it nightly.
No. That's deliberate. Gogs ships the Git server, the web UI, and webhooks; CI runs elsewhere. The standard pattern is a webhook to Drone, Woodpecker, Jenkins, or any runner that accepts a Gogs- or GitHub-shaped JSON payload. If you want CI in the same binary, the descended Gitea and Forgejo forks include built-in Actions; that's their pitch, not Gogs's.
Yes. Gogs supports pull mirrors and push mirrors on a configurable interval. The common pattern is pulling an upstream open-source repo into a private mirror your team can fork without depending on the upstream's uptime, or pushing your authoritative Gogs repo into a public GitHub mirror for visibility while keeping the source of truth on your side.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
Yes for repositories — Gogs's built-in "New Migration" supports cloning any HTTP(S) Git remote, including from GitHub, GitLab, Bitbucket, or any Gogs, Gitea, or Forgejo instance. Issues and pull requests do not transfer automatically; the standard workaround is the source platform's API export plus a per-repo import script.
Not cleanly. Gitea and Forgejo schemas have diverged from Gogs since the 2016 fork. A 2024 community proposal for a modern Gogs-to-Gitea migration tool was closed as rejected, and the reverse direction is not supported. The practical answer: clone the repositories over (Git history preserved), and rebuild issues and pull requests from API exports.
SSH keys: paste each user's public key into their Gogs profile, or bulk-load via the API. Personal access tokens are issued fresh on Gogs — old tokens from the source platform won't work and shouldn't. CI integrations that authenticated via tokens need fresh ones generated against the Gogs URL.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Gogs for 7 days

No card. Cancel from the dashboard.