Private Git hosting
without the trade-offs.
Keep private repositories under European jurisdiction, with a familiar Git workflow and no proprietary exit cost.
CodeTrunk gives developers and teams private Git repositories on managed Forgejo infrastructure in the European Union. Your code, issues, and metadata stay in the EU and are never used to train AI models.
Private Git hosting
Private by design
Paid plans include unlimited private repositories, while the Free plan gives you one private repository with 500 MB of storage. There is no separate privacy switch and no AI opt-out to remember.
A Git workflow you already know
Clone over HTTPS or SSH, push with standard Git, and collaborate with issues, pull requests, and code review on Forgejo. Your existing remotes and tooling keep working.
Leave whenever you choose
Every repository is standard Git. Export your code, mirror it to another Forgejo instance, or move platforms without converting a proprietary archive.
The details behind the summary
The decisions, definitions, and trade-offs that a short guide cannot show.
Private means access control, not secrecy
Private repositories are a permissions model, not a vault. On Forgejo, access is granted to users, teams, and organisations, and every clone, push, and API call is checked against those permissions. The practical questions are who can add members, whether outside collaborators can be limited to one repository, how SSH keys and tokens are revoked, and whether the audit trail shows who changed access. A private repository with a shared admin account is private in name only.
Where the data lives, including backups
CodeTrunk hosts repositories, issues, and metadata on infrastructure in the European Union, with backups in the EU. The infrastructure page names the providers and the privacy policy lists the subprocessors. That matters for a private repository because backups are copies too: a provider that stores primary data in the EU but ships backups to a US region has not solved the residency question. Ask for the backup location, the retention window, and the restore test, not just the primary region.
Deletion, retention, and the awkward parts
Deleting a repository is not the same as deleting every copy. Backups rotate on a schedule, logs have their own retention, and invoices must be kept for Dutch bookkeeping rules even after an account is closed. A serious provider explains each of those paths in the DPA and privacy policy instead of promising that deletion is instant everywhere. If a regulator or a customer asks for proof, you want a documented answer, not a support ticket.
Leaving with your history
Your code is standard Git, so a clone or a push to another remote carries every branch and tag. Issues, pull requests, and releases are metadata: Forgejo migration tools can move much of it, but the receiving platform decides what it accepts. The test of a private Git host is not whether export exists, it is whether export is documented, self-service, and complete enough that you can leave without asking permission.
When self-hosting private Git is better
If you need an air-gapped network, hardware you control, or a custom integration that no managed provider will run, self-hosted Forgejo or GitLab is a defensible choice. The same applies if you already have an operations team that enjoys running forges. CodeTrunk is for the team that wants private repositories, EU residency, and a Dutch contracting entity without taking on the server, the backups, and the upgrade schedule.
Frequently asked questions
Where are private repositories hosted?
Repositories, issues, metadata, and backups are hosted on infrastructure within the European Union, with primary infrastructure and backups in Germany.
Are private repositories used to train AI?
No. Repository content, issues, and metadata are not used to train AI systems, and no third party receives access for that purpose.
Can CodeTrunk staff read my private repositories?
A managed service technically retains administrative access to the infrastructure. We restrict that access contractually and technically to what is needed to operate the service, and repository content is never used for AI training. If you need zero operator access, self-hosting or a dedicated Enterprise arrangement is the better fit.
What happens to my repositories if I delete my account?
The privacy policy and DPA define the deletion path. Repositories and metadata are removed, backups rotate out on their retention schedule, and invoice records are kept for the Dutch statutory period. Export anything you need before you delete the account.
Can I export my private repositories?
Yes. They are standard Git repositories and can be cloned, mirrored, or moved to another host at any time.
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.
-
Repository permissions
Forgejo Docs · Users, teams, and access levels
-
Create and manage an organisation
Codeberg Docs · Organisation and team structure
-
Git documentation
Git Project · Standard Git protocol and clone
-
Regulation (EU) 2016/679 (GDPR)
EUR-Lex · The legal text behind the compliance questions
Keep exploring
Start with the plan that fits.
Create an account with no credit card. Upgrade when your repositories or team need more.
Start Building