Disclosure: We earn commissions from partner links. This doesn't affect our rankings. Learn more

VPSchart Editorial Team

Published January 15, 2026, verified November 2, 2026

Best VPS for Gitea in 2026: choose by workload

A small Gitea instance can run on modest hardware. Storage growth, package files, database writes and Actions jobs are what change the hosting decision. Compare those boundaries before comparing provider checkouts.

Official documentation checked on November 2, 2026. Provider plans and limits can change, so verify the final configuration before ordering.

Short answer

Keep the repository server small, and move CI work out

Gitea documents two CPU cores and 1 GB RAM as typically sufficient for a small team or project. That is a useful floor for the application host. Run Gitea Actions on separate runner capacity, allow storage for repositories and packages, and design the backup before choosing a provider.

Inspect a Hetzner Cloud configuration

Size four workloads, not one VPS

Workload	What consumes capacity	Planning decision
Gitea application	Web requests, Git operations, indexing, mail and background jobs.	Use the official small-team requirement as a floor, then leave headroom for the services you place on the same host.
Database	Metadata, issues, pull requests, users and application state.	SQLite is simple for a small instance. Choose PostgreSQL or MySQL before growth makes a database conversion disruptive.
Persistent files	Git repositories, LFS objects, packages, attachments, avatars and indexes.	Estimate current data, growth and backup copies. Check whether provider backups include every attached volume.
Actions runners	Build containers, dependencies, caches, CPU bursts and untrusted workflow code.	Place runners on separate capacity. Scale and isolate CI independently from the repository server.

Five hosting choices, with different control boundaries

These options are not a synthetic ranking. Four are general-purpose server products. Railway is a platform service. The useful comparison is whether each operating model fits your Gitea deployment and recovery plan.

Raw cloud server

Hetzner Cloud

Useful when you want direct VM control. Check the server, primary IP, attached storage and backup as separate parts. Hetzner documents that server backups exclude attached Volumes.

Review Hetzner Cloud options

VPS with control panel

Hostinger VPS

Useful if you prefer a VPS dashboard and scheduled server backups. Hostinger documents weekly backups by default, optional daily backups and a restore that overwrites the current server state.

Review Hostinger VPS options

Cloud ecosystem

DigitalOcean

Useful if you want a Droplet alongside VPC, monitoring, volumes and managed services. Treat the backup interval, retained images and storage outside the Droplet as part of the design.

Review DigitalOcean Droplets

Compute with broad regions

Vultr

Useful when location choice matters. Vultr documents that automatic backups cover the instance file system but not attached Block Storage, so persistent data may need a separate path.

Review Vultr Compute

Platform service

Railway

Useful for a container-first service when you accept the platform model. A service can mount one persistent volume, and Railway documents a brief deployment interruption for services that use volumes.

Review Railway services

Choose by deployment pattern

Private repos for a small team

Start from Gitea's documented small-team floor. Keep the database and repository data on persistent storage, then add headroom for the reverse proxy, mail and monitoring you actually run.

Check a small Hetzner VM

Gitea plus active CI

Keep the Gitea host predictable. Put Gitea Runner on a separate machine or container host and size it for concurrent jobs, build images and caches.

Container-first deployment

A platform service can reduce server administration, but verify persistent paths, SSH access, restart behavior, backup retention and how you will export data before committing.

Back up Gitea as an application

Gitea's dump includes repositories, the database, data and configuration. Its documentation also says the instance must be stopped for a consistent backup, and restore is a manual process. That makes a recovery drill more important than a backup badge in a provider dashboard.

Map every persistent path. Include repositories, the database, LFS, packages, attachments, configuration and secrets.
Create a consistent application backup. Follow the Gitea procedure and use the native database tool where appropriate.
Copy it away from the instance. Do not keep the only recovery copy on the server or an attached volume that shares its failure boundary.
Use provider images as another layer. Check what the image excludes and how long it is retained.
Restore in isolation. Verify sign-in, clone, push, LFS, packages, issues and an Actions workflow before calling the backup usable.

Decision checklist before checkout

How many users, repositories and concurrent Git operations do you expect?
Will packages, LFS or release assets dominate storage growth?
Will Actions run, and are all workflow authors trusted?
Do you need a full VM, or does a platform service match your operating model?
Which data is excluded from the provider backup?
Can you export and restore the entire instance without the original server?

Review a VM only after the recovery plan is clear

For a small general-purpose Gitea host, compare the VM, IP, persistent storage and backup together. The link keeps the existing commercial destination.

Open Hetzner Cloud configuration

Frequently Asked Questions

How much RAM does a small Gitea server need?

Gitea documents two CPU cores and 1 GB RAM as typically sufficient for small teams or projects. Treat that as an application floor, not a complete server prescription. The database, reverse proxy, mail, monitoring, package storage and Actions jobs can all add demand.

Should Gitea Actions run on the same VPS?

Not by default. Gitea recommends starting runners on separate machines so jobs do not consume the instance resources, and its runner documentation warns about running untrusted jobs. Separate runner capacity also lets you scale CI without resizing the repository server.

Is a VPS snapshot a complete Gitea backup?

No. Provider backups can exclude attached volumes, and Gitea says a consistent backup requires the instance to be stopped while its database, files and repositories are captured. Keep an application-aware backup, copy it away from the server and test a restore.

Can Gitea use SQLite on a small VPS?

Yes, Gitea supports SQLite. Its database documentation warns that SQLite does not scale and recommends choosing the final database type at first installation if growth is expected. For a growing team, plan PostgreSQL or MySQL before migration becomes urgent.

Is Railway the same as a VPS for Gitea?

No. Railway runs long-lived services and can attach persistent volumes, but it is a platform service rather than a general-purpose virtual machine. It may suit a container-first deployment if its volume, backup, restart and networking model match your requirements.

Official sources

This guide uses no invented provider score, fixed price table or undocumented performance test. Read the source documents and verify the final provider configuration before purchase.