AltFreeStack
ESEN
Dev Toolsdocker-ready1-click-deploypermissive-licenseOpen-Core🟡 Standard · ~1GB

Gitea: Open-Core alternative to GitHub in 2026

Gitea is a lightweight Git platform with issues, pull requests, wiki and built-in Actions, built for teams who want their own self-hosted GitHub with very few resources.

Core is open source, but advanced features or enterprise support may be behind a paid tier — check the license.

Alternative to GitHub
License MIT58.5k starsWebsite GitHub Repository

Audit Snapshot

View notes →

  • License — Matches GitHub

  • GitHub — Active

  • Latest release — v28.1.0 · 6 days ago

  • Docker Compose — Partial

  • Production — Not production-tested by AltFreeStack

Gitea vs. GitHub

Pros

  • Runs perfectly on a 1GB RAM VPS

Things to consider

  • Smaller integration ecosystem than GitHub

Quick Docker installation guide

Copy this docker-compose.yml, adjust the example passwords and run docker compose up -d on your server. See the full step-by-step guide →

💡 Official SaaS or self-hosted with AltFreeStack?

  • On the official cloud: a recurring monthly fee and usage limits on GitHub.
  • On your own VPS: the core is free to self-host on your own server — no more monthly SaaS fee, though some advanced features stay behind a paid plan.
docker-compose.yml
version: "3.9"
services:
  gitea:
    image: gitea/gitea:28.0
    restart: unless-stopped
    ports:
      - "3000:3000"
      - "222:22"
    environment:
      - GITEA__database__DB_TYPE=postgres
      - GITEA__database__HOST=gitea-db:5432
      - GITEA__database__NAME=gitea
      - GITEA__database__USER=gitea
      - GITEA__database__PASSWD=change-me-postgres-password # must match POSTGRES_PASSWORD below
    volumes:
      - gitea_data:/data
    depends_on:
      - gitea-db
  gitea-db:
    image: postgres:15-alpine
    restart: unless-stopped
    environment:
      - POSTGRES_USER=gitea
      - POSTGRES_PASSWORD=change-me-postgres-password # REQUIRED: generate a random secret before first run
      - POSTGRES_DB=gitea
    volumes:
      - gitea_pg_data:/var/lib/postgresql/data
volumes:
  gitea_data:
  gitea_pg_data:

🚀 Deploy in 1 command

Recommended for beginners

Copy this single command and paste it into your freshly created VPS's console (Vultr, DigitalOcean...). It downloads the script, prints it to your screen so you can see exactly what it's about to do (never a blind direct pipe), and only then installs Docker if needed, writes the files with secrets already generated, and starts everything — no nano, no pasting code blocks.

curl -sSL ".../api/deploy?stack=gitea" -o deploy.sh && cat deploy.sh && bash deploy.sh
See what this script does →

This docker-compose corresponds to an actively maintained project — last commit today.

This docker-compose not working for you? Report it on GitHub →

Technical profile

License
MIT
Category
Dev Tools
Replaces
GitHub
Tech stack
GoPostgreSQL

Under the hood

Database

PostgreSQL / MySQL / SQLite

Language

Go

Platforms

Web

Key features

  • Built-in issues, PRs and wiki
  • Gitea Actions compatible with GitHub Actions
  • Very low resource usage

Preview

Gitea interface preview

Public image provided by Gitea on its own website.

💾 Backups in 3 steps (Day 2)

As long as the ./data folder (the "volume" mapped into the container) exists on your server, your data survives any restart or container update — that's the only thing you need to back up.

1. Create a compressed backup on the server

tar -czvf backup-$(date +%F).tar.gz ./data

2. Download it to your computer

From your computer's terminal (not your server's):

scp root@YOUR_IP:~/app/backup-*.tar.gz ./

3. Restore in case of emergency

tar -xzvf backup-file.tar.gz
🌐 Connect your domain with free SSL

Step 1 — Set up the DNS

In your domain registrar's dashboard (Cloudflare, Namecheap, GoDaddy...), create a record:

Type
A
Name/Host
@ (root domain) or a subdomain, e.g. app
Content/Value
Your server's public IP

Wait 5 to 15 minutes for the record to propagate across the internet.

Step 2 — Automatic reverse proxy with Caddy

One single file, no Nginx config or manual certificates — Caddy issues and renews Let's Encrypt HTTPS on its own.

Create a file called Caddyfile:

yourdomain.com {
    reverse_proxy localhost:3000
}

Start Caddy with this command (pulls the image and runs it in the background):

docker run -d -p 80:80 -p 443:443 --name caddy --restart always -v $PWD/Caddyfile:/etc/caddy/Caddyfile -v caddy_data:/data caddy