Managed Forgejo hosting, without pretending it is self-hosting.
Fjord gives your team a dedicated, single-tenant upstream Forgejo instance and runs the operational work around it: upgrades, TLS, monitoring, runners, and backups on Team and Pro.
What Fjord is
Fjord is managed Forgejo hosting for teams that want their own forge without becoming a Forgejo operations team. Your team uses upstream Forgejo. Fjord runs the infrastructure underneath it.
Who Fjord is for
Fjord is for teams that want a private, dedicated forge; no per-seat pricing; a written no-AI-training commitment; and a path away from a hosted silo without taking on upgrades, certificates, runner machines, storage, and backup work themselves.
What customers receive
A dedicated upstream Forgejo
One Forgejo instance for one customer, on its own machine with its own database and storage volume.
Managed operations
Fjord handles Forgejo updates, TLS certificates, monitoring, runner capacity, infrastructure, and restores.
Backups on Team and Pro
Nightly encrypted backups with 90-day rolling retention. Starter has no managed snapshot backups.
Forgejo Actions and Pages
Every plan runs on a runner pool Fjord operates. Pages static hosting deploys from your workflows.
Per-instance pricing
Plans are $19, $49, or $149 per instance per month. Fjord does not charge per seat.
Open exit
Forgejo stays upstream and exportable. Export through the API any time, or ask for a full forgejo dump.
Why managed, not self-hosted
Self-hosting is still the right answer when policy requires the forge to live on hardware you own. Fjord is for the other case: you want the forge, but not the upgrade calendar, certificate renewal, runner pool, restore drill, and late-night infrastructure work.
Why dedicated instances
Each customer gets a single-tenant Forgejo instance on its own machine. That means your repositories are not a namespace in a shared database, and your forge is not part of a cross-customer corpus.
Why upstream Forgejo
Fjord runs upstream Forgejo, not a proprietary fork that traps your work in a different format. The API, repository data, and export path stay Forgejo-shaped, which is the point of owning the forge in the first place.
Pricing philosophy
Fjord is billed per instance, not per seat. Plans start at $19/mo. Team and Pro include managed backups; Team and Pro can add dedicated Linux runners at $29/mo each within their plan limits.
See pricingMigration
Forgejo's migrator can import from GitHub and GitLab over their APIs, including repositories, issues, pull and merge requests, labels, milestones, releases, and wikis. For larger moves, ask Fjord to plan the cutover with you.
Read the migration guideRegions and backup placement
Instances and CI runner VMs run in the region you choose: EU Central (Falkenstein), United States, Asia Pacific (Singapore). Fjord is operated from the United States. Backups are currently stored in EU (Helsinki, Finland) for every Instance, whichever region you choose; per-region backup storage is being rolled out. Team and Pro backups are encrypted before they leave the instance and kept on a rolling 90-day window.
When Fjord is not the right fit
Fjord is not the right fit when procurement requires SOC 2, ISO 27001, or a contractual uptime SLA today. It is also not the answer when policy requires the forge to run on hardware you own, or when backups must already be pinned to the same region as the instance.
Managed Forgejo hosting FAQ
What is managed Forgejo hosting?
Managed Forgejo hosting means your team uses an upstream Forgejo instance while Fjord runs the infrastructure around it: updates, TLS, monitoring, runners, and backups on Team and Pro.
Is Fjord single-tenant?
Yes. Each managed Forgejo instance runs for one customer on its own machine, with its own database and storage volume.
Where can my Forgejo instance run?
Fjord offers EU Central (Falkenstein), United States, Asia Pacific (Singapore). Backups are currently stored in Finland regardless of the instance region.
Does Fjord train AI on my code?
No. Fjord does not use repositories or CI jobs to train or improve machine-learning models.
Can I leave Fjord later?
Yes. Forgejo data stays in upstream formats. You can export through the API any time, or ask for a full forgejo dump.
When is Fjord not the right fit?
Fjord is not the right fit when procurement requires SOC 2, ISO 27001, or a contractual uptime SLA today, when policy requires hardware you own, or when backups must already be pinned to the same region as the instance.