Skip to main content
Fjord
Platform
Managed Forgejo
Architecture
How Fjord isolates tenants, regions, runners, and backups.
Operations
What Fjord runs, watches, restores, and reports for each forge.
Security
Controls for access, infrastructure, secrets, and incident handling.
No AI Training
Contractual boundaries for private code and customer data.
Clients
CLI
Ship, authenticate, and inspect Fjord from the terminal.
Mobile
Native iPhone and iPad access for review and triage.
Solutions
Coming from
GitHub alternative
Private repositories on your own forge, no per-seat bill, and where GitHub still wins.
GitLab alternative
Git and CI without operating or buying the whole DevSecOps suite.
Self-hosted Git
Keep the private forge, hand back the upgrades, backups, and on-call.
Gitea hosting
Forgejo is Gitea's fork. What carries over, what does not, and which Fjord runs.
Who it's for
Agencies
A separate forge per client, billed per instance rather than per seat.
Startups
When the default stops being free enough to ignore, priced against GitHub and GitLab.
AI development
Dedicated tenancy and CI boundaries for teams running coding agents.
Before you commit
Start free on Commons
The shared instance, on a free account. No card, and no trial clock.
Compare Git hosts
Nine comparisons, from GitHub and GitLab to running it yourself.
Hosting cost calculator
Rough monthly cost across GitHub, GitLab, DIY operations, and Fjord.
Resources
Learn
Guides
Practical references for adoption, migration, and operations.
Resources
The public library for Fjord decisions and product context.
Plans and state
Roadmap
What is planned, shipped, and intentionally out of scope.
Incidents
Public notes on outages, response, and follow-up work.
Help
Support
How to reach Fjord for account, product, and operations help.
Security Review
Evidence for teams evaluating Fjord before adoption.
Pricing
Login
Get Started
Reset your password
Enter the email you signed up with. We'll send a link to set a new password.
Email
Email a reset link
Back to sign in
