Platform overview
Fjord is managed Forgejo hosting. You sign up for a Fjord Account, provision one or more hosted Forgejo instances, and Fjord runs the server, the runners, and the backups. Everything else in these docs (Actions, Pages, the mobile app, the CLI) plugs into the instance you provision here.
The account is free, and it comes with Fjord Commons, a shared Forgejo instance you can use straight away. Commons is the way to try Forgejo without provisioning anything; the rest of this page is about the dedicated instances you provision when you want a forge of your own.
Dedicated Fjord instances do not have a free tier; they are sold per instance. Fjord Commons is available free for people who want to use Forgejo without provisioning a dedicated instance. See Plans and billing.
How it’s sold
The unit of sale is the instance, never the seat. A single account can own multiple instances at different tiers, and collaborators inside an instance are not metered or per-seat charged. The instance tier governs storage, runner capacity, backups, support, and a few capability gates.
Tiers
| Tier | What you get |
|---|---|
| Starter | Single-user instance, public repos only, CI on the shared runner pool, community support. The on-ramp. |
| Team | Private repos with no cap, the dedicated runner add-on available (up to one), nightly, encrypted, off-site backups with 90-day rolling retention, standard support. |
| Pro | Everything in Team, plus larger storage, a higher dedicated runner cap (up to three), and email support with a business-day response target. |
Pricing is per instance and read from the plan catalog, never hard-coded here. See the rate card on the landing site, fjord.sh.
Connecting the Fjord app directly to a self-hosted Forgejo instance needs no
Fjord Account and no plan: any Forgejo 7.0+ instance reachable over HTTPS works
with a personal access token, the same as the fj CLI. Linking an external forge to your Fjord
Account, so it shows up across your account, is different: that needs a Team or
Pro plan.
What comes with an instance
Runners
Every tier includes the shared runner pool. Dedicated, unmetered Linux runners are a paid add-on, capped at one on Team and three on Pro, and not offered on Starter. Power your Actions.
Pages
Managed static hosting that ships with the forge. Deploy a site straight from a workflow. Pages →
Backups
Nightly, encrypted, off-site snapshots with 90-day rolling retention on Team and Pro.
Native Forgejo
The real Forgejo /api/v1, OIDC IdP, 2FA, and repo controls underneath. The Fjord app and fj CLI talk to it directly.
Getting on
- Create a Fjord Account (identity, sessions, and 2FA are handled centrally).
- Provision a Forgejo instance at the tier you need; watch it move from
requestedtoprovisioningtoready. - Point your runners, Pages, mobile app, and the
fjCLI at it.
Already running Forgejo yourself? You don’t need the platform to use Fjord’s Actions, Pages tooling, or the CLI against your own instance. The platform is the option for not running the server at all.
In this section
- Your Fjord Account: sign-in, sessions, and two-factor.
- Provision an instance: from
requestedtoready. - Manage your instance: the dashboard and signing in to your forge.
- Runners: the compute behind your Actions.
- Backups and restore: snapshots, retention, and recovery by tier.
- Plans and billing: per-instance pricing and the tiers.
- Migrate to Fjord: bring an existing repository in.
- Security and privacy: how your account and data are protected.
- FAQ: common questions about the hosted platform.
- Stephen Way (agent)