Gitea self-hosted architecture review: when to scale past the default binary

We evaluate Gitea in a fully decoupled production architecture, comparing its performance, resource footprint, and CI/CD capabilities against self-hosted GitLab and the lesser-known OneDev engine.

For teams requiring a lightweight, highly customizable Git platform, Gitea in a decoupled state (using Postgres, Valkey, and external runners) is the optimal choice. It avoids the massive resource overhead of GitLab while retaining fast Git operations. However, if your workflow demands native, deeply integrated Kubernetes CI/CD pipelines without managing external runner daemons, or if you want built-in, complex project management out of the box, GitLab or OneDev are better fits. Stick with Gitea if you already use external tools like Plane for project tracking.

Methodology

This review evaluates Gitea version 1.21/1.22 (observed May 2026) in a multi-component self-hosted architecture. This v0 review draws on architectural patterns and claims published by user seamonn on Reddit, alongside official documentation for Gitea, GitLab, and OneDev. Independent performance benchmarks on identical hardware are pending. This analysis covers the operational complexity of decoupling Gitea (using PostgreSQL, Valkey for caching, Elasticsearch for code search, Authentik for OIDC, and Act Runner with Nvidia GPU support) versus the monolithic omnibus installation of GitLab and the Java-based architecture of OneDev. It does not cover long-term database migration paths, high-availability clustering, or edge-case repository sizes exceeding 100GB.

Decoupled core Git operations

In its default state, Gitea runs as a single Go binary with SQLite. When scaled, it decouples its state. PostgreSQL handles metadata, Valkey replaces the internal queue and cache layers, and Elasticsearch indexes code search. This architecture keeps the core Gitea process extremely light, often consuming under 500MB of RAM, while offloading heavy operations to dedicated services.

Containerized CI with Act Runner

Gitea offloads CI/CD to Act Runner, an independent daemon based on nektos/act that executes GitHub Actions workflows. By configuring Act Runner with Nvidia container toolkit support, self-hosted deployments can run GPU-accelerated machine learning pipelines directly within their local Git infrastructure, bypassing expensive cloud GPU runners.

Authentication and external integrations

Gitea provides native OpenID Connect (OIDC) integration, allowing seamless authentication mapping through identity providers like Authentik. It deliberately limits its scope on project management, relying on external API integrations with dedicated tools like Plane for issue tracking, rather than bundling a heavy project management suite.

What is interesting

What is interesting is Gitea's ability to act as a drop-in, lightweight GitHub replacement using standard GitHub Actions syntax via Act Runner. This allows teams to maintain pipeline parity between public GitHub repositories and private self-hosted instances without rewriting YAML files. The addition of Valkey for caching and Elasticsearch for indexing turns Gitea into a highly responsive enterprise-grade platform at a fraction of the hardware cost of GitLab.

What is not interesting is the operational overhead of maintaining this decoupled stack. While a default GitLab Omnibus installation is notoriously heavy, requiring at least 4GB of RAM just to boot, it is packaged as a single, cohesive unit. A fully decked out Gitea setup requires managing five separate stateful services (Postgres, Valkey, Elasticsearch, Authentik, and Act Runner). If any of these services fail, the pipeline or authentication breaks. OneDev presents an interesting middle ground here. It is a Java-based Git server that includes built-in, highly customizable CI/CD and deep project management without requiring external runners or search engines, yet it runs on a much smaller footprint than GitLab.

Pricing

Gitea is open-source under the MIT license and completely free to self-host. GitLab self-hosted offers a Free tier with basic features, a Premium tier at $29 per user per month, and an Ultimate tier at $99 per user per month (pricing snapshot May 2026). OneDev is open-source under the MIT license and free to self-host.

Verdict

Gitea is the best choice for teams that want a fast, modular, and resource-efficient Git platform and are comfortable managing a decoupled infrastructure stack. It is especially powerful if you already use GitHub Actions and want to reuse those pipelines locally via Act Runner. Skip Gitea and choose GitLab if you require an all-in-one enterprise platform with built-in security compliance and do not want to stitch together external tools. Choose OneDev if you want a single, integrated tool with advanced CI/CD and issue tracking but cannot justify GitLab's high resource demands.

What we would test next

In v2, we plan to run synthetic load tests comparing Gitea, GitLab, and OneDev on a single 4-core, 16GB RAM VPS. We will measure Git push/pull latency under concurrent load, memory consumption during active CI/CD execution, and the search indexing speed of Elasticsearch against OneDev's built-in Lucene indexer on a 50GB repository.

The investor read

The self-hosted developer tooling market is undergoing a quiet fragmentation. While GitLab pioneered the single-application DevOps platform, its heavy resource footprint and high pricing tiers ($29 to $99 per user per month) have created an opening for modular, lightweight alternatives. Gitea represents the modular approach, allowing developers to assemble a highly optimized stack using best-of-breed open-source components like Valkey and Authentik. For investors, this signals that enterprise tooling spend is shifting away from monolithic suites toward composable infrastructure. While Gitea itself is a bootstrapped, open-source project, its adoption patterns validate the market for specialized, high-performance developer tools that integrate via standard APIs rather than forcing a single platform lock-in.

Pull quote: “A fully decked out Gitea setup requires managing five separate stateful services (Postgres, Valkey, Elasticsearch, Authentik, and Act Runner).”