#Manage your instance

Each instance you own has a management view in the dashboard and a live Forgejo server underneath it. The dashboard is where you see status and reach the forge; the forge itself is standard Forgejo, so everything you already know about repos, issues, pull requests, and Actions works the same way.

#The instance dashboard

From an instance’s page you can:

• See its current state and URL.
• Sign in to your forge — open the Forgejo web UI for the instance.
• Check the runner pool status, including how many runners are registered and how many are currently busy.
• Manage Pages sites and reveal a deploy token.
• Reach billing and tier controls (see Plans and billing).

#Working with your forge

Under the hood the instance is the real Forgejo, exposing the standard /api/v1 (documented in the upstream

• The mobile app and the fj CLI talk to it directly. The fj CLI connects to any Forgejo host with a personal access token at no extra cost; pointing the Fjord app or platform at a self-hosted Forgejo instance that Fjord does not host for you (a custom server) requires a Pro account. The instances you provision here are covered by your account either way.
• Your CI uses Fjord Actions on the instance’s runners.
• You can publish static sites with Fjord Pages.

#Drive it from the CLI

Point fj at the instance once and the rest is ordinary forge work:

fj instances list                 # instances owned by your Fjord Account
fj instances use my-instance      # route subsequent commands here
fj repo create my-app --private
fj pr list

See the fj CLI guide for the full command surface.

#Collaborators

Add collaborators inside your forge the normal Forgejo way. Collaborators are not metered or charged per seat; billing is per instance. See how it’s sold.