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.
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, shared runner pool, community support. The on-ramp. |
| Team | Private repos with no cap, a dedicated runner pool, daily snapshots (30-day retention), standard support. |
| Pro | Everything in Team, plus larger storage and runner pools, multi-region warm standby with point-in-time restore, and an email support SLA. |
Pricing is per instance and read from the plan catalog, never hard-coded here. See the rate card on the landing site, fjord.sh.
What comes with an instance
Runners
A shared pool on Starter; a dedicated pool registered to your instance on Team and Pro. Power your Actions.
Pages
Managed static hosting that ships with the forge. Deploy a site straight from a workflow. Pages →
Backups
Daily forgejo dump snapshots with 30-day retention on Team; WAL-based point-in-time restore and a warm standby on 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
requestedtoprovisioningto ready. - Point your runners, Pages, mobile app, and the
fjCLI at it.
- Stephen Way