Your own Git server with Gitea or Forgejo
Keep your code, issues and packages on a server you control. Gitea and Forgejo are light Git forges written in Go: repositories, pull requests, code review, a package registry and built-in Actions CI, on a small VPS for a team or a larger server for an organisation, preinstalled as an app option or with our guide.
- Repositories, pull requests, issues and wikis
- Built-in Actions CI with your own runners
- Package registry for containers, npm, PyPI and more
- Small teams run fine on 2 vCPU and 1 GB of RAM
- StackCurrent releases: Gitea 28.1 (Gitea dropped the old 1. prefix) and Forgejo 16, with Forgejo 15 as the long-term support release.
- Go, one binary or a container
- Default portsBoth use the system’s OpenSSH by default; put the web interface behind a reverse proxy with HTTPS.
- 3000 (web), 22 (SSH)
- Minimum
- 2 vCPU and 1 GB RAM for small teams
- Your data
- Repos plus SQLite, PostgreSQL or MySQL
- Official docs
- docs.gitea.com · forgejo.org/docs
Features
- Gitea Actions
- Forgejo Actions
- Package registry
- Pull requests
- Issues and projects
- Wikis
- Repository mirrors
- OAuth2 / LDAP
Facts from the project’s official website, documentation and repository, checked in October 2026.
Plans are being prepared
We are preparing ready-to-use plans for Gitea and Forgejo. Tell us how you will use it and how many users you expect, and we will reply with a server that fits. You can also start today on a Linux VPS and install it with our guide.
Which server size fits?
Starting points for vCPU, memory and disk. Grow the server when your data and users grow.
| Feature |
Personal
Your projects and a few collaborators
|
Recommended Team
A team with CI and packages
|
Organisation
Many repositories, users and runners
|
|---|---|---|---|
| vCPUVirtual processor cores of the server. | 1–2 | 2–4 | 4–8 |
| MemoryMemory for the app, its database and the operating system. | 1–2 GB | 4 GB | 8 GB+ |
| DiskRepositories, packages, attachments and backups. | 20 GB | 50–100 GB | 200 GB+ |
| CI runnersActions jobs run on separate runners that need Docker. | None or one small runner | One runner on its own server | Several runners on separate servers |
| Server type | Linux VPS | Linux VPS | VPS or VDS |
-
Personal
Your projects and a few collaborators
- vCPUVirtual processor cores of the server.
- 1–2
- MemoryMemory for the app, its database and the operating system.
- 1–2 GB
- DiskRepositories, packages, attachments and backups.
- 20 GB
- CI runnersActions jobs run on separate runners that need Docker.
- None or one small runner
- Server type
- Linux VPS
-
Recommended
Team
A team with CI and packages
- vCPUVirtual processor cores of the server.
- 2–4
- MemoryMemory for the app, its database and the operating system.
- 4 GB
- DiskRepositories, packages, attachments and backups.
- 50–100 GB
- CI runnersActions jobs run on separate runners that need Docker.
- One runner on its own server
- Server type
- Linux VPS
-
Organisation
Many repositories, users and runners
- vCPUVirtual processor cores of the server.
- 4–8
- MemoryMemory for the app, its database and the operating system.
- 8 GB+
- DiskRepositories, packages, attachments and backups.
- 200 GB+
- CI runnersActions jobs run on separate runners that need Docker.
- Several runners on separate servers
- Server type
- VPS or VDS
Gitea’s documentation states that 2 CPU cores and 1 GB of RAM are typically enough for small teams; Forgejo publishes no figures. CI jobs need their own resources, ideally on a separate server.
A complete Git platform, without the weight
Everything a team needs around its code, on a server that costs little to run.
Code review and issues
Pull requests with reviews, protected branches, issues, project boards and wikis for every repository.
Actions CI
Gitea Actions is mostly compatible with GitHub Actions workflows; Forgejo Actions feels familiar, though workflows usually need small changes. Jobs run on your own runners.
Package registry
Publish container images, npm, PyPI, Maven, NuGet, Composer, Cargo, Helm and more next to your code.
Mirrors and migration
Import repositories with issues and pull requests from other forges, or keep push and pull mirrors in sync.
Full root access
Install what the app needs, change any setting and run more services next to it. Nothing is locked behind a panel.
App option or step-by-step guide
Order the server with the app installed as an option, or set it up yourself on a clean Linux server with our guide.
Near your users
Choose a data center in the United States, Europe or Asia. The order form estimates the latency from where you are to each location.
Backups on VPS and VDS
Free weekly and monthly backups come with VPS and VDS plans. Keep your own copies of databases and app data as well.
From order to first login
Order the app preinstalled on your server, or install it yourself with our guide.
-
Pick the server
Choose a size from the table above and the data center closest to the people who will use the app.
-
Add Gitea or Forgejo
Select Gitea or Forgejo as an app option when you order, or install it on a clean Ubuntu or Debian server with our guide.
-
Point a domain and enable HTTPS
Create a DNS record such as app.example.com for the server and put a reverse proxy with a free Let’s Encrypt certificate in front of the app.
-
Create the admin account
Finish the setup page, create the first admin, add your SSH key and push your first repository.
Step-by-step setup guides
Install, secure and update the app with our guides, written for current Ubuntu and Debian releases.
-
How to install Forgejo or Gitea with Docker Compose, PostgreSQL and HTTPS
Run your own Git forge with Forgejo or Gitea: official Docker images, PostgreSQL, Caddy for HTTPS, SSH on port 2222 and no open registration, plus dump-based backups and safe major-version updates.
40 min Intermediate
Related solutions
Frequently asked questions
Should I choose Gitea or Forgejo?
Both are light, fast forges with the same roots. Forgejo started as a community fork in 2022, became a hard fork in early 2024 and is developed by a non-profit community. Gitea is developed by its company and community. Their features overlap closely; pick the one whose project and release cycle you prefer.
How much server do I need?
Gitea’s documentation says 2 CPU cores and 1 GB of RAM are typically enough for small teams, and even a Raspberry Pi 3 can run it for small workloads. Plan more memory for many users, large repositories and code search, and give CI runners their own server.
Can I run CI pipelines?
Yes. Gitea Actions and Forgejo Actions run workflows stored in your repository on runners you register: Gitea Runner or Forgejo Runner, which use Docker for container jobs. Gitea Actions is mostly compatible with GitHub Actions; Forgejo looks in .forgejo/workflows first and usually needs small changes to GitHub workflows.
Which database should I use?
SQLite is built in and fine for a personal or small instance. For teams, use PostgreSQL or MySQL/MariaDB on the same server or a separate one; Gitea also supports Microsoft SQL Server.
How do users clone over SSH?
By default both forges use the server’s OpenSSH on port 22 and add users’ keys automatically. If you need port 22 for your own logins, move your admin SSH to another port or enable the built-in SSH server on a different port.
Can I move my repositories from GitHub or GitLab?
Yes. The migration tool imports repositories and, where the source allows it, issues, pull requests, labels, milestones and releases. You can also keep a mirror that pulls from the original until you switch.
Does Forgejo support federation?
Federation between Forgejo instances is under active development and still experimental, so expect changes. Everything else, from repositories to Actions, is stable for daily use.
How do I back up my forge?
Both include a dump command that packs repositories, the database and settings into one archive. Run it on a schedule, copy the archive off the server, and test a restore; VPS and VDS plans also include free weekly and monthly backups.
Can Gitea or Forgejo send email?
Yes. Notification and sign-up emails go out through the SMTP server you set in the mailer section of app.ini. Outbound port 25 is closed by default on HyperDC VPS. For services bought for a term of 3 months or longer, it is opened on request through a support ticket; until then, or instead, send through an SMTP relay on port 587.
Bring your code home
Tell us the app, how many people will use it and where they are, and we will suggest a server for it.