Repositories and limits

Public and private repositories

Public repositories are unlimited on every plan. Anyone can read and clone them.

Private repositories are limited by your plan. The dashboard and billing page show how many slots you use. Changing a repository from private to public frees a slot. Changing one from public to private needs a free slot, because a private repository that exceeds the plan is made read-only by the enforcement pass instead of being deleted.

Storage

Each plan has a storage allowance. The dashboard shows current usage for your account and for organisations you own.

When the allowance is full, Forgejo rejects new pushes until you free space or upgrade. Nothing is deleted automatically, and existing content stays readable and cloneable.

Archived repositories

Repositories that exceed the private repository limit are archived, which makes them read-only. They remain visible, cloneable and downloadable, and nothing inside them is removed.

Freeing a slot or upgrading unlocks the repositories that enforcement archived. Archiving is reversible; deletion is not.

Organisations and seats

Organisations are available on the Business plan and above. A Business subscription has a seat count:

• The organisation owner holds one seat.
• The remaining seats are available to members.
• Members beyond the seat count are removed from the organisation. Their repositories and data are not touched.

Add members in Forgejo under the organisation's Members page. The MCP server can remove a member but cannot add one, because Forgejo adds members through the Owners team and that grants co-owner rights.

Branch protection and repository settings

Forgejo supports protected branches, collaborators, webhooks and deploy keys in the repository settings. Those settings are independent of your plan: a public repository on the Free plan can use them just like a Business repository.

Importing and exporting

Repositories are standard Git. Clone or mirror them at any time:

git clone --mirror <clone URL>

For issues and pull requests, Forgejo's New migration flow can import from GitHub, GitLab, Gitea, Forgejo and other HTTP remotes. What the receiving host accepts depends on the source platform, so check the result after the import.

Your account data can be exported as JSON from your profile, see Account and security.

Backups

CodeTrunk backs up the service, but a backup is not a substitute for your own copy. Keep a clone or mirror of anything you cannot recreate.