Git hosting for teams
without per-seat surprises.
Give your team repositories, organisations, code review, and EU-native data protection without buying an entire DevOps suite.
The Business plan adds organisations, team access, unlimited repositories, 30 GB of storage, and a DPA. Each organisation member counts as one seat, so billing follows the people actually using the workspace.
Git hosting for teams
Work together in one forge
Create organisations, invite collaborators, manage access, and review changes with pull requests and built-in code review. The platform stays focused on Git instead of surrounding your team with unrelated modules.
Pricing that explains itself
Business starts at €18 per active organisation member per month, with yearly billing available. There are no minimum terms, and you can adjust seats as your team changes.
Compliance for the whole team
Business includes a DPA, EU data residency, documented infrastructure, and the guarantee that we do not train AI on your data on every plan.
The details behind the summary
The decisions, definitions, and trade-offs that a short guide cannot show.
Organisations, teams, and least privilege
Forgejo organisations group repositories and people. Teams grant access to specific repositories, so a contractor can be added to one project without seeing the rest. The details that matter are whether repository admins can change access, whether outside collaborators are supported, and whether removing someone from a team revokes their SSH keys and tokens. A flat permission model is fine for five people and painful at fifty.
Code review that a small team will actually use
Pull requests, line comments, approvals, and protected branches are the core. The question is not whether the feature exists, but whether it is fast enough that people use it. A review flow that requires a separate tool or a long checklist will be bypassed under deadline. Forgejo keeps review next to the diff, which is the right default for a team without a platform group.
CI without a platform team
Forgejo Actions uses GitHub-style YAML workflows, so a build-test-deploy pipeline is familiar. Hosted runners are not included in the current CodeTrunk plans; teams can connect their own runner if they need CI. That is a real limitation for a team that wants zero infrastructure. If hosted CI is a hard requirement, a larger platform or a dedicated runner setup is the honest answer.
Seats, billing, and growth
The Business plan counts each active organisation member as a seat. That is simple to explain to finance, and it means a contractor who joins for a month is a seat for that month. Compare that with per-user suites that charge for every module. The right model depends on whether you grow by adding people or by adding capabilities.
When a DevOps suite is the better fit
If you need portfolio planning, security scanning, a container registry, and test management in one contract, a suite such as GitLab or Azure DevOps is a better fit. CodeTrunk deliberately does not replicate those modules. The case for CodeTrunk is a team that wants Git hosting, review, and a clear seat price, and already has the rest of its toolchain.
Frequently asked questions
How are team seats counted?
Each member of an organisation counts as one seat. You pay for active members and can adjust the seat count from billing.
Does the team plan include a DPA?
Yes. The Business plan includes a data processing agreement, and the public DPA can be reviewed before signup.
Can a team use private repositories?
Yes. Business includes unlimited private repositories, organisations, team access, and 30 GB of storage.
Do you offer hosted CI runners?
Forgejo Actions workflows are supported, but hosted runners are not included in the current plans. Teams can connect their own runner if they need CI. If fully hosted CI is a hard requirement, that is the one area where a larger platform is currently a better fit.
Can a contractor access only one repository?
Yes. Forgejo teams can be scoped to specific repositories, so an outside collaborator gets access to the project they work on without seeing the rest of the organisation. Removing them from the team revokes that access.
Sources and further reading
Primary sources for the claims in this guide, last checked 20 October 2026. Product terms change; check the source before you decide.
-
Create and manage an organisation
Codeberg Docs · Organisation and team structure
-
Repository permissions
Forgejo Docs · Users, teams, and access levels
-
Forgejo Actions
Forgejo Docs · Workflow syntax and runner model
-
Pull requests and Git flow
Forgejo Docs · Review, branches, and merge flow
Start with the plan that fits.
Create an account with no credit card. Upgrade when your repositories or team need more.
Start Building