Must have
Hard prerequisites
No universal server-size prerequisite is published. Check the exact release and configuration before you deploy.
Application hosting
Hosting Gitea
Gitea is a self-hosted Git service. Its official binary includes SQLite, MySQL, and PostgreSQL support; database and storage choices should reflect repository growth and expected users.
- Min vCPU
- Depends on workload
- Min memory
- Depends on workload
- Min storage
- Depends on workload
Recommended
Documented guidance
No further general recommendations are published for this version.
Capacity depends on your workload
The cited installation pages do not specify a universal server size. Repository count, Git operations, attachments, CI runners, and user activity affect capacity.
We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.
Deploy with
Supported paths
The host must provide
Runtime
- Database
- SQLite, MySQL, or PostgreSQL included in official binary; check supported database versions for the chosen Gitea release
- Git
- Install a Git version supported by the selected Gitea release
Storage
Persistent data
Persistent space is needed for repositories, attachments, packages, database, logs, and backups. No single capacity fits every installation.
Step by step
Gitea deployment outline
-
Select a release and database
Match the official binary to the server platform and select a supported database before initial installation.
Official instructions -
Prepare persistent data
Keep repositories and application data on persistent storage and create a dedicated database account when using MySQL or PostgreSQL.
Official instructions -
Protect and maintain the service
Configure TLS at the public endpoint, restrict administration, and test restoration of repositories, database, and configuration together.
Official instructions
Security
Before you go public
- Use TLS for public access.
- Keep Git, Gitea, and the database updated.
- Back up repositories, database, and configuration together.
Cost
Beyond the server price
- Budget for persistent repository storage, backups, and outbound traffic.
- CI runners, package registries, and attachments can add separate compute and storage demand.
Matching plans
Plans with published evidence
DigitalOcean
CPU-Optimized Regular Droplet · 2 vCPU / 4 GiB
2vCPU
4 GiBRAM
25 GiBStorage
4 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
DigitalOcean
General Purpose Droplet · 2 Dedicated vCPU / 8 GB
2vCPU
8 GBRAM
25 GBStorage
4 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Hetzner Cloud
Hetzner Cloud CCX53 (Germany and Finland)
32vCPU
128 GBRAM
600 GBStorage
50 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Hetzner Cloud
Hetzner Cloud CCX63 (Germany and Finland)
48vCPU
192 GBRAM
960 GBStorage
60 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
No published runtime facts let us confirm a match.
Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.