Forgejo Hosting: Your Own Private Git Server

Forgejo is a self-hosted Git forge: repositories, issues, pull requests and code review on your own server, in a web interface that will feel familiar if you have used GitHub. Choose it with a plan, pay, and we build the VPS (KVM, NVMe, Ubuntu 24.04 LTS) and install Forgejo in about three minutes after boot. You get:

• Forgejo 17.0.1 with PostgreSQL 18, with Git LFS switched on for large files.
• An HTTPS address like yourname-x7k2.devoster.app with a Let's Encrypt certificate, and Git over SSH on port 2222, opened in the server's firewall for you.
• Your admin account already created. You sign in with your Devoster account email and a generated password shown in the dashboard. (Signing in with the username works too, but it isn't "admin", which Forgejo reserves.) The web installer is skipped, so there is no setup page for anyone to claim.
• Registration closed. Nobody can sign up from the public site; you create accounts for your team in Site administration.
• Dashboard controls to open Forgejo, reset the admin password, restart, stop or start it, read its logs, run an update and connect your own domain.

Forgejo is free; you pay only the VPS plan, with 10% off yearly. The server comes with full root, free nightly backups kept 3 days plus one snapshot, a dedicated IPv4, 1 Gbps with unlimited bandwidth and DDoS protection. See the other apps that install this way on the One-Click Apps page.

Forgejo started as a fork of Gitea and is now developed independently. It is governed by its community under the umbrella of Codeberg e.V., a non-profit, and released under the GPLv3 or later. It stays compatible with Gitea in the ways that matter day to day: the API, repository migrations and most tooling that speaks to Gitea work with Forgejo too.

What you can do with it:

• Repositories with branches, protected branches, releases and Git LFS.
• Issues, pull requests and code review, with labels, milestones and project boards.
• Wikis and a package registry for publishing your own packages next to the code.
• Organisations and teams with per-repository permissions, webhooks and mirrors to or from other forges.
• Migrations from GitHub, GitLab, Gitea and others, including issues and pull requests where the source allows it.

For a wider look at where self-hosted Git fits against GitHub, GitLab and Bitbucket, see our Git hosting guide.

Both protocols work from the first minute, and the clone URLs Forgejo shows already include the right port:

git clone https://yourname-x7k2.devoster.app/team/app.git
git clone ssh://git@yourname-x7k2.devoster.app:2222/team/app.git

• SSH uses Forgejo's built-in SSH server on port 2222. Add your public key under your Forgejo user settings. Port 22 stays the server's own SSH for root administration, so the two don't collide.
• HTTPS works through any firewall. Use an access token from your user settings instead of your password for Git operations and CI.

One catch with Cloudflare: if you connect your own domain and turn on Cloudflare's proxy (the orange cloud) for it, Git over SSH stops working on that name, because Cloudflare's proxy only passes web traffic. Set that DNS record to "DNS only", or use HTTPS for Git.

Forgejo Actions, Forgejo's built-in CI system, is enabled, but no runner is installed. Workflows are not executed by Forgejo itself; they are handed to a runner, a separate program (Forgejo Runner) that you register with your instance. Until you add one, workflows queue and wait.

• On another server is the cleaner option: builds use their own CPU and RAM, and a runaway job can't slow down your Git server.
• On the same VPS works too, since you have root, but size up: builds and Forgejo then share the plan's memory. Starter or Basic is a sensible floor for that.

The workflow syntax is designed to feel familiar to GitHub Actions users but is not fully compatible, so expect small changes when you bring workflows over. Forgejo reads .forgejo/workflows, and falls back to .github/workflows if that directory doesn't exist.

Forgejo is light: about 150 MB of RAM at idle with its database. Memory goes up during clones and pushes of big repositories and while the web UI renders large diffs. Disk is usually what you run out of first, especially with LFS files and packages.

Micro is the plan we recommend for a team: the extra gigabyte keeps big pushes and diff views comfortable. You can upgrade from the panel later.

Forgejo sends no email here. Outbound mail ports are blocked by default on Devoster VPS plans, so Forgejo's mailer is switched off: there are no forgot-password emails and no email notifications. Team members follow activity through Forgejo's in-app notifications, or you can send events to Slack, Discord or Matrix with webhooks. You set passwords when you create accounts, and reset the admin password from the Devoster dashboard.

Updates: we test new Forgejo versions and apply them in a maintenance hour you choose, or when you press Update now, with a VPS snapshot first and an automatic rollback if Forgejo doesn't come back healthy. Forgejo releases new major versions regularly, and we move installs to them through the same managed updates once they are tested. Auto-update can be switched off.

The server is unmanaged: you have full root, and its security and your code are your responsibility. Nightly backups (3 days) cover the whole VPS; for code you can't lose, keep a push mirror to another forge as well. Our VPS hardening checklist is a good first hour. If you'd rather deploy straight from your repositories, Coolify pairs well with a Forgejo server.