Managed Forgejo vs running it yourself.
Same software. The only question is who carries the pager.
Self-hosting, you own
- Upgrades and security patches
- Database backups and their restores
- TLS certificates
- CI runner infrastructure
- Storage and monitoring
- The 2 a.m. page when disk fills up
On Fjord, we run
- Forgejo updates, applied for you
- Nightly off-site backups, 90-day retention (Team and Pro)
- TLS handled end to end
- Dedicated runners, ready to go
- The infrastructure underneath
- On-call so you are not
When self-hosting is the right call
If you have a sysadmin with spare cycles, want total control of the host, or have a policy that the forge must live on your own metal, self-host. We mean that. Fjord is for teams that would rather not take on the operational risk: small teams with proprietary or regulated code and no one to spare for forge ops.
What doesn't change either way
It is Forgejo on both sides: same software, same open data, same API. Fjord adds no proprietary lock-in. Your data exports in the upstream format any time, and we don't use your code to train AI. Start on Fjord and later decide to self-host, and you leave with everything.
Managed Forgejo FAQ
Is Fjord self-hosted?
No. Fjord is managed Forgejo: you get a dedicated Forgejo instance, and we run the updates, backups, DNS, mail, runners, restores, and operational upkeep.
When should I self-host instead?
Self-hosting is right when you need total control of the machine, custom networking, or a policy that the forge live on your own infrastructure.
Can I leave Fjord and run Forgejo myself later?
Yes. It is Forgejo on both sides, your data exports in the upstream format, and Fjord adds no proprietary lock-in.
Do you train AI on my code?
No. We don't use your code to train AI, and the commitment is written into the service terms.