Day 1
Install Forgejo
Pick a VM, point DNS, configure TLS and mail, create the first admin, and import or create repositories.
We've done it. It is good software, and running it yourself can be the right answer. The real question is whether you still want to operate it in six months.
Forgejo is not the hard part. The install is a beginning, not the bill. The durable cost is the responsibility that follows: backups, restore practice, upgrades, runners, disk space, mail, monitoring, and the occasional advisory that arrives at an inconvenient time.
Day 1
Pick a VM, point DNS, configure TLS and mail, create the first admin, and import or create repositories.
Week 2
Add monitoring, log rotation, disk alerts, database backups, object storage policy, and a restore runbook.
Month 2
Read release notes, schedule a window, snapshot the instance, apply the update, and keep a rollback path.
Month 5
CI grows, storage grows, users want private repos or SSO, and the small install starts needing operating habits.
Month 10
A security advisory lands while you are away from the keyboard. The question is not whether you can fix it. It is whether you still want that job.
| Area | Self-hosting | Fjord |
|---|---|---|
| Forgejo updates | Track releases, test upgrades, schedule maintenance, and own rollback. | Applied by Fjord as part of managed operations. |
| Backups | Design the backup job, retention, off-site storage, restore procedure, and periodic restore checks. | Included on Team and Pro with nightly encrypted backups and 90-day rolling retention. Starter has no managed snapshot backups. |
| Monitoring | Watch disk, CPU, memory, queues, certificates, mail delivery, database health, and HTTP availability. | Fjord operates the instance infrastructure and watches the service. |
| TLS, DNS, and mail | Configure certificates, renewal, DNS records, SMTP, deliverability, and failure alerts. | Handled as part of the managed instance. |
| CI capacity | Run, patch, isolate, and replace runner hosts if you use Forgejo Actions. | Shared runner pool is included. Dedicated runner add-ons are available by plan. |
| Incident response | Own the investigation, restore, and user communication when the forge is down. | Fjord owns the managed service operation; support targets vary by plan and are not contractual SLAs. |
| Work | Typical / approximate effort | Shape |
|---|---|---|
| Initial install and hardening | 4 to 12 hours | Once, then revisited |
| Backups and restore testing | 6 to 18 hours | Yearly |
| Updates and security patches | 8 to 24 hours | Across the year |
| Monitoring and alert tuning | 4 to 16 hours | As usage changes |
| CI runner care | 6 to 30 hours | If you run CI |
| Incident handling | 0 to 20+ hours | Unplanned |
Most self-hosted instances don't fail because of Forgejo. They fail because life gets busy.
Fjord Starter is $19/month per instance. Team is $49/month and Pro is $149/month. Self-hosting can still be the right choice, but compare it against the hours you spend maintaining the forge, not only the VM bill. For many teams the useful comparison is the price of a coffee habit against a Saturday every few months.
Self-hosting is very reasonable here: install Forgejo, configure the basics, and you have a working forge.
Fjord starts with a dedicated managed Forgejo instance and keeps the setup path short.
You own user support, storage growth, logs, mail delivery, alerts, and runner behavior.
Fjord handles the operating layer so the forge can stay a tool instead of a recurring task.
You decide when to update, read the notes, snapshot first, and validate after.
Fjord applies managed updates for you.
A backup is only useful if it restores. You own both the schedule and the proof.
Team and Pro include nightly encrypted backups. Starter does not include managed snapshot backups.
You find the last good backup, rebuild the host, restore data, and communicate status.
Fjord owns recovery work for the managed service within the limits of the selected plan.
You revisit capacity, storage, runners, SSO, permissions, and operational boundaries.
Per-instance plans let many users share one instance price without per-seat billing.
The instance becomes another production service, with all the small chores that implies.
Fjord is built for teams that want Forgejo without making forge operations part of the job.
Sometimes. If your time is free to you, your infrastructure is already paid for, and you like maintaining it, self-hosting can be cheaper. If a Saturday every few months costs more than a managed instance, the math changes.
Yes. Fjord runs upstream Forgejo. Your repositories and Forgejo data are not converted into a proprietary product.
No. You keep standard Forgejo repositories and can leave. Fjord is a managed operating model, not a new source-control format.
One Team instance is $49/month before any optional add-ons, not 30 separate seats.
A shared Starter instance is $19/month when public repositories and a single-user forge fit. Team is $49/month when private repos and team ownership matter.
A project with many contributors still maps to an instance plan. Starter is $19, Team is $49, and Pro is $149 per month.
Choose self-hosting if infrastructure is part of the hobby. Choose Fjord if software is the job. Both are valid. We built Fjord for the second group.