Fjord vs Gitea Cloud.
Gitea Cloud is a commercial Gitea offering with public pricing. Fjord is managed upstream Forgejo, Gitea's fork, so the forge concepts are familiar but a current Gitea move is still a real migration. The verified public pricing page did not confirm tenancy, regions, CI, Pages, mobile access, CLI, MCP, backups, export, no-AI-training terms, or compliance posture.
The Short Version
Gitea Cloud is strongest when Gitea itself is the target and staying on Gitea avoids migration work. Fjord is strongest when you want Forgejo, Gitea's fork, and the operating model must be publicly documented before a managed forge decision. If you are moving from a current Gitea server, read the Gitea migration guide before assuming the switch is a drop-in move.
Fjord And Gitea Cloud, By Capability
| Dimension | Fjord | Gitea Cloud |
|---|---|---|
| Forge lineage | Managed upstream Forgejo, Gitea's fork. | Commercial Gitea offering. |
| Moving from Gitea | Repository migration into Forgejo; see /migrate/gitea. | Staying on Gitea avoids a Gitea-to-Forgejo migration. |
| Tenancy | Dedicated single-tenant VM per customer. | Not documented. |
| Jurisdiction and regions | Operated from the United States with EU Central, US, and Singapore regions. | Not documented. |
| Hosted CI | Managed runners, with dedicated runner add-ons by plan. | Not documented. |
| Pages | Managed Pages are documented. | Not documented. |
| Mobile | Native iPhone and iPad app on the App Store. | Not documented. |
| CLI | Yes. | Not documented. |
| Public MCP server | Not documented. | Not documented. |
| Pricing model | Per-instance plans, not per-seat. | Public pricing is documented; operating model details are not documented in the verified source. |
| Backups | Included: nightly encrypted backups. | Not documented. |
| Export | Forgejo-native export and exit are documented. | Not documented. |
| No-AI-training | Contractual no-AI-training commitment and Content-Signal ai-train=no. | Not documented. |
| Compliance posture | No published SOC 2 or ISO 27001 claim. | Not documented. |
Choose Gitea Cloud When
- You specifically want Gitea Cloud.
- The public Gitea Cloud pricing page is enough for your buying decision.
- You do not need public confirmation of tenancy, regions, backups, CI, Pages, MCP, export, or compliance posture before evaluation.
Choose Fjord When
- You want managed Forgejo, Gitea's fork, and accept a real migration from current Gitea.
- You need dedicated tenancy, CI, Pages, mobile access, CLI, export, and no-AI-training terms documented before purchase.
- You want region and operations details stated publicly.
- You prefer per-instance managed Forgejo.
What Fjord Is Not For
Fjord is not Gitea Cloud and does not claim database-level takeover of a current Gitea server. If you need to stay on upstream Gitea without a Gitea-to-Forgejo migration, choose a Gitea provider.
Read the architecture notes, data residency details, no-AI-training terms, and pricing for the current Fjord commitments.