Application hosting

Hosting Forgejo

A self-hosted Git collaboration service for repositories, issues and code review. Repository storage and optional automation runners need separate planning, especially when projects build untrusted code.

See cheapest plans Size a server

Understand the setup

Check runtime, storage and installation requirements before choosing a server.

See requirements

Budget your resources

Allow room for the operating system, database and your actual workload.

Open resource planner

Build your shortlist

See the cheapest plans that meet the starting size, then check each provider's page.

See plans

Must have

Installation requirements

A supported binary installation or container environment.
Persistent repository and application storage.
A configured database appropriate to the installation.

Recommended

Planning guidance

Use the resource planner to size a server for your workload.

No official hardware minimum for Forgejo

Size the web service separately from build runners. Repository count alone does not describe clone traffic, large files or the resource demand of CI jobs.

Deploy with

Supported paths

Binary with service management
Docker installation

The host must provide

Runtime

Git: Required by the binary installation; check the selected release instructions
Database: Configure using the database preparation guide

Storage

Persistent data

Account for Git repositories, large-file objects, attachments and database records. Preserve configuration and secrets with the recovery procedure. Automation artifacts can grow separately from the source repositories.

Step by step

Plan a Forgejo deployment

Select the release

Follow binary or Docker instructions for the chosen supported release and architecture.
Official instructions
Configure persistent state

Set repository storage, database access and the public address before allowing team registration.
Official instructions
Separate automation

If enabling Actions, review runner registration and isolation. Keep build execution away from unrelated production workloads.
Official instructions

Security

Before you go public

Use HTTPS and review account registration and repository visibility.
Restrict runner privileges and avoid sharing production secrets with untrusted jobs.

Cost

Beyond the server price

Include repository growth, backups and any separate build machines.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.