Skip to content
3 min read

Plans and billing

Fjord bills per instance, never per seat. One account can own several instances at different tiers, and collaborators inside an instance are not metered.

Dedicated Fjord instances do not have a free tier. Fjord Commons is available free for people who want to use Forgejo without provisioning a dedicated instance: it is a shared Forgejo, not a free plan on a dedicated one, and nothing on it is billed.

The tiers

TierBest for
StarterA single user, public repos only, CI on the shared runner pool, with community support. The on-ramp.
TeamTeams that need unlimited private repos, the option of dedicated runners as an add-on, and nightly, encrypted, off-site backups with 90-day rolling retention and standard support.
ProTeams that want larger storage, a higher dedicated-runner cap, the same nightly, encrypted, off-site backups with 90-day rolling retention, and email support with a business-day response target.

The full feature breakdown is on the platform overview. Current prices are on the rate card at fjord.sh; pricing is read from the live plan catalog, so the landing site is always the source of truth.

What each tier includes

Exact figures live on the rate card; the shape of the limits by tier is:

  • Repositories. Starter is public repos only; Team and Pro add private repos.
  • Managed runners. Every tier includes the shared runner pool, so managed CI works on Starter, Team, and Pro. Nothing dedicated is included at any tier. A dedicated, unmetered Linux runner is a $29/mo per-runner add-on on top of the plan price, and the per-instance cap on how many you may attach scales with the tier (0 / 1 / 3 for Starter / Team / Pro). See Runners.
  • Backups. Team and Pro include nightly, encrypted, off-site backups with 90-day rolling retention. Starter has none, so keep your own copies. See Backups and restore.
  • Storage. The per-instance storage allowance scales with the tier, smallest on Starter and largest on Pro. The rate card lists the current figure.
  • Support. Community on Starter, standard business-day support on Team, and priority email with a business-day response target on Pro.
Note

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 you can change

  • Change tier. Plan changes are handled by support for now. See Changing your tier for what a change does to runners, storage, and backups.
  • Add capacity. Where a tier offers the dedicated runner add-on, you can attach runners up to that tier’s cap (one on Team, up to three on Pro), each at the current add-on price; Starter does not offer the add-on. Add a runner when you deploy, or later from your instance page. Leave the add-on off and you pay the plan price only.
  • Manage payment. Manage your payment method, invoices, and subscription from the billing portal.

Changing your tier

Plan changes are handled by support for now: reach out at support to move an instance up or down.

Upgrading takes the instance to the higher tier’s limits: a larger runner cap and storage allowance, private repositories from Team up, and, from Team up, nightly encrypted backups. Upgrading requires a payment method on file.

Downgrading drops the instance to the lower tier’s limits. That means a lower dedicated runner cap and a smaller storage allowance, and moving below Team ends managed nightly backups. Because the lower tier includes less storage and Starter has no managed backups, export or copy anything you need first (see Backups and restore); reducing storage or losing backup coverage can put data at risk if you are near or over the new limit.

Proration, and whether a change applies immediately or at your next billing cycle, follow your subscription terms; support will confirm the exact effect before making the change.

Cancellation

You can cancel an instance’s subscription from the dashboard. Cancellation stops future billing for that instance; export anything you need first (see Backups and restore). Non-payment and cancellation handling follow the terms of service.

Questions

Billing questions go to support.

Contributors
  • Stephen Way (agent)