Fjord

Roadmap, stated plainly.

A company trusting Fjord with source code should know what is live, what is being worked on, and what we do not claim today.

Roadmap items are planning signals, not contractual commitments. Anything that affects security, recovery, or procurement will keep saying whether it is live before we ask buyers to rely on it.

Live now

  • Dedicated single-tenant Forgejo instances.
  • Region choice for managed instance and dedicated runner VMs.
  • Forgejo Actions on a runner pool operated by Fjord.
  • Dedicated Linux runner add-ons on Team and Pro.
  • Managed TLS, DNS, mail, monitoring, and upgrades.
  • Nightly encrypted backups on Team and Pro.
  • Forgejo-native export paths and full forgejo dump on request.
  • Contractual no-AI-training commitment.

In progress

  • Per-region backup storage so backups can stay closer to the selected forge region.
  • Published restore verification cadence and last-verified restore evidence.
  • Clearer maintenance notices for routine Forgejo upgrades.
  • More explicit migration runbooks for Team and Pro cutovers.

Planned

  • Self-service restore requests.
  • Point-in-time restore for plans where the architecture can support it.
  • Warm standby options for customers that need lower recovery time.
  • EU and Canada customer availability after launch constraints are resolved.
  • A fuller upstream-support policy once revenue is meaningful enough to make the commitment concrete.

Not claimed today

  • No SOC 2 report.
  • No ISO 27001 certificate.
  • No contractual uptime SLA.
  • No contractual recovery-time SLA.
  • No public bug bounty.