Gitea Alternatives
Seven Git forges to replace Gitea, from free self-hosted forks to hosted platforms, with their real limits and prices.
Short answer: Forgejo is the closest replacement for Gitea, the same lightweight forge in Go, now under GPL v3+ with its domains held by a non-profit. GitHub is the pick if you would rather stop hosting anything, GitLab if you want a full DevOps platform and have the hardware, and OneDev if you want CI and boards built in. Bitbucket suits Jira teams, Codeberg free open source projects, and Gogs the smallest servers. One warning before you compare: the easy database swap to Forgejo only works from Gitea 1.22 or older.
The ranking is editorial: a sponsored placement is always flagged on its card, and no affiliate link changes a score.
Why teams look past Gitea
Gitea is a lightweight, self-hosted Git forge written in Go, free under the MIT license with unlimited users and repositories, and its repository on GitHub counts 59.2k stars. It still does its job well. What pushes teams to compare is less the code than who owns the project, what the paid edition holds back, and how CI behaves.
A for-profit company owns the name
SAML and support sit in a paid edition
Security notices reach paying customers first
Actions is compatible, with exceptions
The door to Forgejo is narrowing
Forgejo
Forgejo is Gitea's fork, born in 2022 when Gitea's domains and trademark moved to a for-profit company. For about a year it tracked Gitea line by line; in early 2024 it became a hard fork and its code began to diverge. Day to day, a Gitea user finds the same screens: repositories, issues, pull requests, wikis, a package registry and Forgejo Actions, a built-in CI whose YAML looks like GitHub Actions. Its domains are held by Codeberg e.V., a German non-profit, and it runs on volunteer work, grants and donations. Codeberg.org, the forge of that same association, runs on it.
The license is the real change. Forgejo v9.0 and later ship under the GPL v3+, while versions up to v8.0 stay MIT. If you install an official build for your team, you are very unlikely to be affected; if you redistribute a modified build, you must publish its source under the same license. Stable releases come every quarter, and one release each spring is a long-term support release: 15.0 LTS is maintained until 2027.
- Same interface and concepts as Gitea
- GPL v3+ since v9.0, domains held by a non-profit
- Quarterly releases, one LTS per year
- Built-in Forgejo Actions and package registry
- ✓Free, with no paid edition holding features back
- ✓Gitea users are productive on day one
- ✓Advance notice of security releases open to everyone
- ✗Direct upgrade only from Gitea 1.22 or older
- ✗No vendor SLA: support comes from the community or paid providers
- ✗Its CI is close to GitHub Actions, not identical
| Criterion | Forgejo | Gitea |
|---|---|---|
| License | GPL v3+ (v9.0 and later) | MIT |
| Paid edition | None | Enterprise, $9.5/user/mo, 1-year |
| Domains held by | Codeberg e.V. (non-profit) | For-profit company |
| Upgrade path | From Gitea up to 1.22 | n/a |
Pick Forgejo if you want Gitea's lightness without its company; choose GitLab instead if you need SAML, security scanning and a vendor to call when something breaks.
GitHub
GitHub is what Gitea imitates, so moving there feels like going to the original. Gitea Actions was designed to be compatible with GitHub Actions, so most workflows move with few edits, and the GitHub Marketplace offers ready-made actions and apps for almost every tool. For a small team, the maths is often the real reason: the Free plan already gives unlimited public and private repositories, 2,000 CI/CD minutes a month and 500MB of package storage.
Team costs $4 per user per month and adds required reviewers, code owners, draft pull requests, repository rules and 3,000 CI/CD minutes. Enterprise, at $21 per user per month, adds SAML single sign-on, the audit log API and 50,000 minutes; it is also the only plan that includes GitHub Enterprise Server, the self-hosted edition. Large files have a quota: Git LFS includes 10 GiB of storage and 10 GiB of bandwidth on Free, 250 GiB of each on Team and Enterprise Cloud, and usage above that is billed per GiB. If you later want to leave GitHub too, our guide to switching from GitHub lists what to move.
- Unlimited private repositories on the Free plan
- 2,000 CI/CD minutes a month free, 3,000 on Team
- GitHub Marketplace of reusable actions and apps
- Enterprise Server for on-premises at $21 per user
- ✓No server to run, back up or upgrade
- ✓Gitea Actions was built to match its workflow syntax
- ✓Team seat at $4, against $29 for GitLab Premium
- ✗Your code sits on GitHub's cloud, not your server
- ✗Self-hosting means the $21 Enterprise plan
- ✗No importer for Gitea issues and pull requests
| Criterion | GitHub | Gitea |
|---|---|---|
| Hosting | Cloud, or Enterprise Server | Self-hosted or Gitea Cloud |
| Entry paid seat | $4/user/mo (Team) | $9.5/user/mo (Enterprise, 1-year) |
| CI minutes included | 2,000/mo on Free | Your own runners |
| SAML SSO | Enterprise ($21) | Enterprise ($9.5) |
Pick GitHub if hosting Gitea was a chore and your code can live in the cloud; stay self-hosted with Forgejo or GitLab if data location or cost per seat at 100 users matters more.
GitLab
GitLab is the opposite trade to Gitea: far more features for far more hardware. One application covers source code, merge requests, issue boards, a container registry, CI/CD pipelines with environments, static analysis (SAST) even on Free, and full application security testing and compliance on Ultimate. You can run it yourself, as the free Community Edition or a paid self-managed licence, or use GitLab.com, where the Free plan covers 5 users per top-level group with 400 compute minutes a month.
Premium costs $29 per user per month billed annually, on GitLab.com and self-managed alike, with 10,000 compute minutes on GitLab.com; Ultimate is priced on request. Budget the server too. GitLab sets 16 GB of memory and 8 vCPU as the baseline for a single-node install, and 8 GB as the floor in a memory-constrained setup. A built-in importer pulls Gitea repositories with their issues, pull requests, milestones and labels. Our page on leaving GitLab shows the other side: what teams miss when the bill or the server grows.
- CI/CD, registry and planning in one application
- Built-in Gitea importer for issues and pull requests
- Same $29 Premium price self-managed or on GitLab.com
- Application security testing on Ultimate
- ✓Code, CI, registry, planning and security in one place
- ✓Imports Gitea projects with their history
- ✓Free Community Edition for self-hosting
- ✗16 GB of RAM as the single-node baseline
- ✗Major upgrades need planning and care
- ✗Premium is billed annually, $29 a seat
| Criterion | GitLab | Gitea |
|---|---|---|
| Memory for one node | 16 GB baseline, 8 GB floor | Runs on a small VPS |
| Paid seat | $29/user/mo, annual | $9.5/user/mo, 1-year |
| Security testing | SAST on Free, full suite on Ultimate | Through external tools |
| Gitea importer | Yes | n/a |
Pick GitLab if you want one platform for code, CI and planning and can give it a 16 GB server; choose Forgejo instead if Gitea's simplicity is what you liked.
OneDev
OneDev is a self-hosted forge with its own CI/CD engine, issue tracker, Kanban boards and package registry for Docker, npm, Maven, NuGet, PyPI, RubyGems and Helm. Where Gitea asks you to install and register runners, OneDev runs jobs in containers or sandbox VMs, scales them with agents or Kubernetes, and lets you create jobs without writing YAML. It adds code search by symbol in any commit, comments on any part of the code without opening a pull request, and AI users you can assign issues to. It runs on a box with 2 cores and 2 GB of memory, and its code is MIT licensed.
The Community Edition is free. Enterprise costs $6 per user per month and adds clustering for high availability, cross-project code search, security and license scans, audit logs, time tracking and priority email support with a reply within two business days. Each order covers at least 12 user-months, and the subscription period is those user-months divided by your users: 3 users on a minimum order get 4 months, for $72.
- CI/CD jobs created without writing YAML
- Kanban boards and package registry in the box
- Runs on 2 cores and 2 GB of memory
- Enterprise at $6 per user, clustering included
- ✓One install replaces forge, CI server and tracker
- ✓Paid seat at $6, under Gitea Enterprise's $9.5
- ✓MIT license for the free edition
- ✗Its CI spec is its own, so GitHub-style workflows need rewriting
- ✗15.4k GitHub stars, against 59.2k for Gitea
- ✗Enterprise orders start at 12 user-months
| Criterion | OneDev | Gitea |
|---|---|---|
| CI | Built-in engine, no YAML needed | Gitea Actions + runners |
| Paid seat | $6/user/mo | $9.5/user/mo, 1-year |
| Issue boards | Kanban, custom states | Projects boards |
| License | MIT (Community) | MIT |
Pick OneDev if you want forge, CI and boards in one small install and do not reuse GitHub workflows; choose Forgejo instead if your pipelines are Actions YAML today.
Bitbucket
Bitbucket Cloud is Atlassian's Git hosting, and its main argument is everything around it: Atlassian builds it to work with Jira and Confluence, so code reviews and builds sit next to the tickets and pages your team already uses. Bitbucket Pipelines is the built-in CI, configured in a YAML file of its own. For a team leaving Gitea because nobody wants to maintain the server, it is the cheapest paid seat on this list.
The Free plan covers up to 5 users with 1 GB of Git LFS file storage and 50 build minutes a month. Standard costs $3.65 per user per month with 2,500 build minutes, and Premium $8 with 3,500 minutes and AI and automation features. Extra minutes cost $10 per 1,000 a month, and extra LFS storage $10 per 100 GB; Standard includes 5 GB of LFS and Premium 10 GB. Atlassian also sells Bitbucket Data Center, its self-managed edition, through sales for teams with strict regulatory or security requirements. Teams who later outgrow it read our guide to switching from Bitbucket.
- Built by Atlassian to work with Jira
- Standard at $3.65 per user per month
- Bitbucket Pipelines with 2,500 minutes on Standard
- Data Center for self-managed installs
- ✓Lowest paid seat price on this list
- ✓Jira and Confluence from the same vendor
- ✓No server to maintain on Cloud
- ✗Only 50 build minutes on the Free plan
- ✗Pipelines YAML differs from Gitea Actions
- ✗Self-managed Data Center is sold through sales
| Criterion | Bitbucket | Gitea |
|---|---|---|
| Paid seat | $3.65/user/mo | $9.5/user/mo, 1-year |
| CI minutes | 50 free, 2,500 Standard | Your own runners |
| Same vendor as Jira | Yes, Atlassian | No |
| Self-hosted | Data Center, via sales | Free, MIT |
Pick Bitbucket if your team lives in Jira and wants cheap hosted seats; choose GitHub instead if you rely on the Actions ecosystem, or Forgejo if code must stay on your servers.
Codeberg
Codeberg is a hosted forge run by Codeberg e.V., a non-profit association in Germany, and it runs on Forgejo. For a Gitea user that means the same interface with nothing to install: you sign up, push, and keep working in issues and pull requests that look familiar. It is free as in beer and as in freedom, and membership of the association is optional. Its mission is free software, so content should carry a free license, and private repositories are tolerated for contributors, not offered as commercial hosting.
Fair use replaces a price list. Before going over 750 MiB of Git storage or 1.5 GiB of packages, LFS and attachments, you ask the team first, and accounts start with a limit of 100 repositories. Hosted CI exists: a Woodpecker CI instance that a volunteer opens after reviewing your request, provided as-is. Forgejo Actions also works on Codeberg with self-hosted runners you attach.
- Runs on Forgejo, the same interface as Gitea
- Free, run by a non-profit association
- Woodpecker CI on request, or your own runner
- Servers on its own hardware in Berlin
- ✓Zero cost and zero server work
- ✓Same workflow as a Gitea instance
- ✓Governed by the votes of association members
- ✗Made for free software, not company code
- ✗750 MiB of Git storage before asking for more
- ✗CI access needs a manual approval
| Criterion | Codeberg | Gitea |
|---|---|---|
| Price | Free (donations) | Free self-hosted, or paid |
| Software | Forgejo | Gitea |
| Private company code | Not the purpose | Yes, self-hosted |
| CI | Woodpecker on request, or own runner | Your own runners |
Pick Codeberg if your project is open source and you are tired of running a server; choose a self-hosted Forgejo instead for private company code or heavy CI.
Gogs
Gogs is the project Gitea forked from, and it is still alive, still in Go, still a single binary. Its pitch has not changed: a Git service that installs in minutes on Linux, macOS, Windows or ARM and runs on 64 MiB of RAM and a quarter of a vCPU. It has been MIT licensed since 2014. You get repositories, issues, pull requests with merge, rebase and squash, wikis, releases, organizations and teams, webhooks for Slack and Discord, and sign-in through LDAP, SMTP or PAM.
What Gogs does not give you yet is automation: in its own feature list, Actions and compute are marked as in development, so there is no built-in CI to replace Gitea Actions. Several features, such as inline reviews, code owners and OAuth sign-in, carry the same mark. For a backup forge, a mirror or a home lab, that rarely matters; for a team that relies on pipelines, it does.
- Runs on 64 MiB of RAM and a quarter vCPU
- Single Go binary for Linux, macOS, Windows, ARM
- MIT licensed since 2014
- PostgreSQL, MySQL or SQLite3
- ✓The smallest footprint on this list
- ✓Very little to configure or upgrade
- ✓Fine as a mirror or backup forge
- ✗Actions and CI still in development
- ✗Inline reviews and code owners not there yet
- ✗OAuth 2.0 and SAML sign-in still in development
| Criterion | Gogs | Gitea |
|---|---|---|
| Built-in CI | In development | Gitea Actions |
| License | MIT | MIT |
| Paid edition | None | Enterprise |
Pick Gogs if you want the lightest possible Git server and no CI; choose Forgejo instead as soon as your team needs pipelines, packages or richer code review.
7 Gitea alternatives compared
The seven forges side by side. Each score is the average of five criteria: ease of setup, value for money, features and depth, support and governance, integrations and CI. Prices are those of each pricing page in 2026; check the billing period, since GitLab and Gitea Enterprise bill by the year.
| Best for | What it does better than Gitea | Free plan | Team size | Visit | ||||
|---|---|---|---|---|---|---|---|---|
| 1 | Forgejo | Closest replacement for Gitea | Same forge, GPL v3+, no paid edition | 4.4/5 | Free (self-hosted) | ✓ | Any team that self-hosts | Visit → |
| 2 | GitHub | Best if you stop self-hosting | No server, 2,000 free CI minutes | 4.3/5 | Free; Team $4/user/mo | ✓ | Any size, cloud | Visit → |
| 3 | GitLab | Best full DevOps platform | Planning, CI and security in one app | 4.1/5 | Free; Premium $29/user/mo, annual | ✓ | Larger teams, 16 GB server | Visit → |
| 4 | OneDev | Best all-in-one on a small server | CI and boards built in, no YAML | 3.9/5 | Free; Enterprise $6/user/mo | ✓ | Small and mid-size teams | Visit → |
| 5 | Bitbucket | Best for Jira teams | Native Jira links, $3.65 seats | 3.8/5 | Free (5 users); Standard $3.65/user/mo | ✓ | Teams on Jira | Visit → |
| 6 | Codeberg | Best free home for open source | Hosted Forgejo, free, non-profit | 3.8/5 | Free (donations) | ✓ | Open source projects | Visit → |
| 7 | Gogs | Lightest self-hosted Git server | Runs on 64 MiB of RAM | 3.5/5 | Free (self-hosted) | ✓ | Solo devs and tiny teams | Visit → |
Is your tool missing from this page? Email us: hello@hackceleration.com
You're leaving Gitea because... take this
Same interface, GPL v3+, non-profit.
You are tired of running a serverGitHubFree plan, Team at $4 a seat.
Your CI and planning outgrew GiteaGitLabPipelines, boards, scanning; 16 GB server.
You want CI and boards without YAMLOneDevVisual job editor, $6 Enterprise.
Your tickets live in JiraBitbucketStandard at $3.65 per user.
Your project is open sourceCodebergHosted Forgejo, free.
Your server is a Raspberry PiGogs64 MiB of RAM, no CI.
How to choose a Gitea alternative
Gitea belongs to the software forge category: a web application that hosts Git repositories and adds the collaboration around them. A forge stores your repositories and serves them over SSH and HTTPS, then layers issues, pull requests with review, wikis, releases, a package registry and, more and more, CI that runs your tests on each push. Self-hosted forges such as Gitea, Forgejo, Gogs, OneDev or GitLab run on your server; hosted ones such as GitHub, Bitbucket or Codeberg run on theirs. Before comparing prices, decide which side you are on, then check the points below. Our ranking of the best Git hosting services goes wider than this list, and if your problem is only CI, our guide to GitHub Actions alternatives covers runners and build services.
Check your Gitea version before anything else
gitea --version. Up to 1.22, Forgejo upgrades your instance in two steps: first to Forgejo v10.0, then to any later release, keeping users, issues and settings. From 1.23 on, the upgrade guide offers no path, so the move becomes a migration of each repository through the new forge's import screen. Keep the old instance read-only until the last repository is checked on the new one.Size the server for the forge you pick
Count the paid seat over a full year
Read what the importer leaves behind
Other forges we compared and left out
Treat CI as its own migration
- Your Gitea version, from gitea --version
- The number of users who log in each month
- Total size of repositories, LFS objects and packages
- The workflows that build and ship releases
- Your identity provider: LDAP, OAuth or SAML
- A tested backup restored on a scratch server
Gitea alternatives: your questions
Does the free Gitea support LDAP and single sign-on?
Partly. The free edition connects to Active Directory and LDAP, syncs LDAP users, and signs people in through OpenID Connect or an external OAuth 2.0 provider, with two-factor authentication and WebAuthn. SAML 2.0 is the gap: it is missing from the free edition and comes with Gitea Enterprise. If your identity provider speaks OpenID Connect, you may not need the paid edition at all.Why did Forgejo split from Gitea?
In 2022, Gitea's domains and trademark were transferred to a for-profit company without the knowledge or approval of the community. Contributors wrote an open letter; when the takeover was confirmed anyway, they started Forgejo under the non-profit Codeberg e.V., and it became a hard fork in early 2024.Do GitHub Actions workflows run unchanged on Forgejo?
Not always. Forgejo describes its Actions as designed to be familiar to GitHub Actions users but not designed to be compatible, so a workflow may need small edits. Gitea, by contrast, aims for compatibility and documents its exceptions, which matters if you move from Gitea to Forgejo.Can Gitea keep pushing to GitHub while I trial another forge?
Yes. Gitea supports push mirrors, which sync commits to an external repository, and pull mirrors in the other direction. Set a push mirror to the new forge during the trial, so both stay current and you can cut over on a quiet day without a freeze.How do I back up Gitea before migrating?
Stop Gitea, then run gitea dump, which saves the installation to a ZIP file you can unpack to restore it; the instance must be shut down for a consistent backup. On MySQL or PostgreSQL, add a native mysqldump or pg_dump, since gitea dump uses XORM, which has open restore issues.Should my new forge use SQLite or PostgreSQL?
Use PostgreSQL or MySQL if the team will grow. Gitea's own documentation warns that SQLite does not scale and that converting one database type to another may cause issues, so the final database is best chosen at the first installation.Does a mirror back up my Gitea issues and pull requests?
No. A push mirror syncs commits to an external repository and a pull mirror syncs commits from one: issues, pull request reviews, users and settings stay in Gitea's database. Only a full backup such as gitea dump, plus a native database dump, keeps them. Use a mirror to keep code current during a trial, never as your only copy.Which Forgejo release should I run in production?
Run the current long-term support release. Forgejo ships a stable release every quarter, and one release each spring is an LTS: 15.0 is supported until 2027 and 19.0 follows in 2027. A non-LTS release stops getting fixes about two weeks after the next one ships.