Self-hosted Git control, without self-hosted operations.
If you are running a Git server or about to stand one up, Fjord is the managed alternative: dedicated Forgejo operated for your team, with the operational work made explicit.
Managed, not self-hosted
Use the words for what you have now, then choose the responsibility you want.
Self-hosted Git can be the right answer. It also means somebody owns patches, backups, restore tests, runner security, monitoring, and the late-night edge cases. Fjord keeps the private-forge shape while moving that operations job into a managed service.
When Fjord is the wrong answer
Keep self-hosting when you need root-level control, custom Forgejo or Gitea patches, air-gapped placement, unusual storage or network policy, or an operations team that wants the Git server as part of its own platform.
The job that comes with the server
Upgrades and security patches
Self-hosted Git is not installed once. Someone owns Forgejo, Gitea, GitLab, OS packages, TLS, and emergency patch timing.
Backups and restore tests
A backup plan only matters after a restore works. Fjord keeps that as a managed service question instead of a spare-hour chore.
Runners and isolation
CI turns a quiet Git server into compute, secrets, logs, and untrusted job boundaries. Treat that as infrastructure, not a checkbox.
Migration and exit
The point is control you can use: standard Git, Forgejo-native workflows, migration planning, and export paths that stay readable.
What this page delegates
Put numbers on the DIY job
The cost calculator owns the self-hosting math: staff time, VM costs, backups, runners, maintenance, and incident time.
Estimate self-hosting cost ->
Compare managed and self-hosted
The self-hosting comparison owns the deeper tradeoff between control, responsibility, price, backups, support, and compliance proof.
Read the self-hosting comparison ->
Check operations readiness
The readiness tool owns the operational checklist before you decide to keep running your own Git server.
Run the readiness check ->