#Managed Forgejo hosting, on your own single-tenant instance

Fjord is managed Forgejo hosting for teams that want control of their source forge without becoming the operations team for it. You get a Forgejo instance that is single-tenant by architecture, operated by Fjord, with managed Linux CI runners, Pages, and nightly, encrypted, off-site backups with 90-day rolling retention.

Start with Fjord or read the GitHub migration guide.

#What you get

#Unmetered CI, with Linux live today

Every instance runs CI on the shared runner pool. On Team and Pro you can also attach dedicated runners as a paid add-on, registered to your instance alone and not billed by the CI minute. Today, the live dedicated runner flavor is Linux: target it from Forgejo Actions with runs-on: ubuntu-latest and keep using GitHub Actions compatible workflow files.

That means your .github/workflows jobs can move with the repository. Rename to .forgejo/workflows when you want Forgejo-native layout, or keep the familiar shape while you migrate. The Fjord Actions bundle provides drop-in cache, artifact, language setup, Docker, and automation actions by full Forgejo URL, so workflows do not depend on github.com at runtime.

#Backups and restore

Team and Pro instances have nightly, encrypted, off-site backups with 90-day rolling retention. Recovery is from the most recent nightly snapshot in that window and is operator-run.

#Sovereignty without the ops burden

Running your own Forgejo gives you sovereignty, but it also gives you backups, upgrades, runner capacity, incident response, and operational drift to manage. Hosted source forges reduce the work, but usually move you back into a shared platform you do not control.

Fjord is built for the middle ground: a managed Forgejo instance with clear single-tenant boundaries, standard Forgejo interfaces, and operations handled by people who run the platform every day.

If you are comparing options, see the self-hosted GitHub alternative page for the tradeoffs between Fjord, GitHub, DIY Forgejo, and GitLab.

#Pricing model

Fjord is sold per instance. A single account can own multiple Forgejo instances, and collaborators inside an instance are not metered per seat. The public rate card on fjord.sh is the source of truth for current prices.

Starter is the on-ramp for a single user and public repositories. Team adds private repositories and nightly, encrypted, off-site backups with 90-day rolling retention. Pro builds on Team with larger storage plus email support with a business-day response target. Every tier includes the shared runner pool; dedicated Linux runners are a paid add-on on Team and Pro, priced per runner on the rate card.

#Migration path

Forgejo includes repository migration tools for moving repositories, issues, pull requests, labels, milestones, releases, and LFS data from GitHub. Forgejo Actions is compatible with GitHub Actions workflow syntax, so most workflow files come across as ordinary YAML rather than a CI rewrite.

Use the migrate from GitHub to Forgejo guide when you are planning the move. It covers one-time imports, mirror-then-switch cutovers, and CI checks before you point teams at the new forge.

#FAQ

#Is this Forgejo cloud hosting or a shared forge?

It is managed Forgejo hosting on your own single-tenant instance. You get the Forgejo product surface without sharing one hosted Forgejo namespace with other customers.

#Do I need to maintain runners?

No. Fjord registers and operates the runners for your instance. Every tier includes the shared runner pool, and dedicated Linux CI is available today as a paid add-on on Team and Pro.

#Are backups included?

Team and Pro include nightly, encrypted, off-site backups with 90-day rolling retention. Starter users should keep their own copies of anything critical.

#Does Fjord lock me into a proprietary API?

No. Fjord runs standard Forgejo underneath, including the Forgejo API and git remotes. The Fjord dashboard and fj CLI are added around the forge rather than replacing it.

#Can I migrate from GitHub?

Yes. Forgejo can import GitHub repositories and project metadata, and Forgejo Actions can run GitHub Actions compatible workflow files. Start with the migration guide to plan the cutover.