Own your forge. Don't operate it.
Fjord is for teams that want Forgejo control without becoming a Forgejo operations team.
A pattern worth taking seriously
The pattern is simple: teams want their own Forgejo instance, but they do not always want to become Forgejo administrators. Fjord exists for that control-without-chores use case.
I would like to own my forge, and I would like someone competent to run it.
The part people don't actually want
Running a forge sounds simple until you are the one responsible for:
- Upgrades
- Backups
- Email delivery
- TLS certificates
- Storage growth
- Runners
- Disaster recovery
- Security updates
Most teams don't want a hobby. They want a forge. That is the part we take off your plate.
The triggers are real, and they are not ideology
When the Zig project moved from GitHub to Codeberg, its announcement centered on lock-in, ownership, and GitHub's engineering and CI direction after the Microsoft acquisition; the AI and Copilot push was framed as a bonus, not the cause. That is the honest shape of the feeling: ownership and autonomy first, AI concerns alongside. We are not interested in selling outrage. We are interested in the calm version of that instinct.
What Fjord is
A dedicated, single-tenant Forgejo run for your team, so you don't have to. We handle updates, backups, TLS, and runners. Private by default, never used to train AI, billed per instance, never locked in.
What Fjord is not
Not a public shared forge for free and open-source projects; Codeberg already serves that role well. Not a DIY self-hosting guide (the whole point is our buyer would rather not). And deliberately not "managed, but called self-hosted." Fjord is managed. We say so.
Built in the open, and giving back
Forgejo is a community project under a nonprofit, and we do not intend to extract from it. Two things are already true today: the software stays open, and your data exports any time in Forgejo's own format, so leaving is always an option you hold. On top of that we intend to send our fixes and improvements upstream rather than hoard them, and to publish a concrete upstream-support policy once revenue is meaningful. A commercial host can be a good citizen of an open ecosystem, and we would rather be judged on what we actually do than asked to take a pledge on faith.
The Fjord team, Raster & State