Self-hosted Forgejo mobile

A mobile app for self-hosted Forgejo needs clear authentication, notification, and network assumptions.

Mobile

What this solves

You run Forgejo yourself and want to understand how mobile access should work.

Best fit

Self-hosted teams
Private networks
Managed hosting evaluation

How to think about it

Self-hosted mobile access depends on the boring infrastructure details: public reachability or VPN, TLS, authentication policy, token scope, notification delivery, and how the app behaves when the forge is temporarily unreachable.

Self-hosted access checklist

Host reachable from mobile network: yes/no
TLS certificate trusted by iOS: yes/no
OAuth or token policy chosen: yes/no
Notifications tested: yes/no
Lost-device access revocation documented: yes/no

Practical path

01 Confirm the Forgejo host is reachable from mobile networks.
02 Choose OAuth or token-based sign-in according to your policy.
03 Review notification and approval workflows before broad rollout.

When to choose another path

Private-network forges need a mobile network strategy before rollout.

Token revocation should be part of device offboarding.

Notification behavior may differ when the host is behind strict firewalls.

Next resources

Fjord Mobile

Mobile product page.

Download on the App Store

Install Fjord Mobile for iPhone and iPad.

Mobile docs

Setup and usage guides.

Security review

Review trust and access model.

Managed hosting

A Forgejo instance operated for your team.