A GitHub alternative
that does not train on your data.
Same Git workflow. Hosted in the EU. We do not train AI on your data.
CodeTrunk is European Git hosting powered by Forgejo, a fully open-source Git platform. If you're looking for a GitHub alternative because of jurisdiction, AI processing, or GDPR concerns, this page shows exactly how the two compare, including the EU option GitHub added for Enterprise Cloud.
Side by side
The differences that matter when you choose a home for your code.
| CodeTrunk | GitHub | |
|---|---|---|
| Hosting jurisdiction | European Union only | GitHub.com: US. Enterprise Cloud: optional EU residency. Enterprise Server: self-hosted |
| AI features on your code | None: no AI processing of repositories | Copilot chat, code review, and cloud agent |
| AI training on your code | Never, by contract and by design | Free, Pro, Pro+, and Max interaction data may train models since 24 April 2026 unless opted out; Business and Enterprise excluded |
| GDPR & data protection | Native: EU law applies directly, DPA included | DPF and DPA; EU residency requires Enterprise Cloud |
| Platform source code | Fully open source (Forgejo) | Proprietary |
| Private repositories | 1 free, unlimited from €8/mo | Unlimited free (with feature limits) |
| CI / Actions | Forgejo Actions | GitHub Actions |
| Lock-in | None: export everything, standard Git | Proprietary features (Actions marketplace, Pages, Packages, Projects) |
| Contracting entity | StennMedia, Netherlands (KvK 99876302) | GitHub, Inc. and Microsoft Corporation (US) |
A Dutch company, not a US subsidiary
CodeTrunk is operated by StennMedia, registered with the Dutch Chamber of Commerce under KvK 99876302 and established in Breda. The contract is governed by Dutch law and VAT is paid in the Netherlands. When your legal team asks who is accountable for the data, the answer is a European company with no US parent in the chain.
- Legal entity
- StennMedia
- Registration
- KvK 99876302
- Governing law
- Netherlands
Why developers switch
Three reasons teams move their repositories to CodeTrunk.
Jurisdiction, not promises
Your repositories, issues, and metadata never leave European jurisdiction. EU data protection law applies directly, no transatlantic transfer frameworks to keep track of.
No AI features in the repository path
There is no Copilot, no code review agent, and no model endpoint. Your repositories are hosted to run the service, not to provide AI suggestions or training data for anyone.
No lock-in
Standard Git, open-source platform. Export your repositories or move to any other Forgejo instance at any time. Leaving is a feature, not a support ticket.
The details behind the table
The vendor decisions and dates that a comparison table cannot show.
What GitHub hosting actually means in 2026
GitHub's default is a US service. GitHub stores data for GitHub.com in the United States, including repositories, issues, and Actions logs for Free, Team, and ordinary Enterprise accounts. Since October 2024, GitHub Enterprise Cloud with data residency can place code and in-scope data in the EU on a dedicated ghe.com subdomain, alongside Australia, the US, and Japan. That option requires Enterprise Cloud and managed user accounts, and GitHub still stores some categories outside the region, including Copilot data by default unless you enable the in-region Copilot policy. Enterprise Server is the other EU-capable path: self-hosted, with the operational work that implies.
The Copilot training rule changed in April 2026
GitHub now uses interaction data from Copilot Free, Pro, Pro+, and Max to train and improve its models unless the user opts out. That data includes inputs, outputs, accepted or modified code, the code around the cursor, file names, repository structure, and feedback. GitHub says Copilot Business and Copilot Enterprise are not affected, and that content from private repositories at rest is excluded. The last distinction matters: Copilot still processes private repository code while you use it, and that interaction data can be used for training unless you opt out. An organisation has to know which plans its developers use and verify the setting account by account.
Private repositories are not private AI
GitHub's own wording separates code at rest from code in use. A repository can be private and still be sent to a model when someone opens Copilot chat, runs a code review, or assigns the cloud agent. GitHub offers controls: disable Copilot for an organisation, exclude content, restrict models, or use the data residency Copilot policy. Those are real controls, but they are settings that need an owner and an audit. CodeTrunk's position is simpler: there is no Copilot, no model endpoint, and no setting that decides whether repository content reaches an AI service.
What actually leaves when you leave GitHub
Git is portable, and GitHub's API lets you export issues, pull requests, comments, and releases. The surrounding product is where the work is: Actions workflows, Marketplace apps, Packages, Pages, Projects, Discussions, and wikis do not map one to one. Actions YAML is close enough to Forgejo Actions that a small pipeline ports in an afternoon, but every uses reference has to resolve, and secrets, environments, and permissions need rebuilding. Pages needs a new host. For a repository with ten years of history and a dozen integrations, the migration is a project, not a push.
GitHub Actions and Forgejo Actions are relatives, not twins
Both use YAML workflows, jobs, steps, matrices, services, and OIDC, and both can run shell commands or container actions. The difference is the ecosystem: a GitHub workflow can call any action in the Marketplace, while Forgejo resolves actions against data.forgejo.org or a full URL. Popular actions such as checkout and setup-node exist; long-tail vendor actions may not. GitHub-hosted runners are also a service, while Forgejo runners are yours to register. A pilot with your three most important workflows tells you more than a feature table.
When GitHub is still the right answer
If your organisation depends on the Marketplace, GitHub Advanced Security, Codespaces, or a large Copilot deployment, replacing GitHub with a smaller Git host is not a fair comparison. GitHub Enterprise Server also remains a legitimate self-hosted option. The case for CodeTrunk is narrower: you want managed Git in the EU without an enterprise contract, you do not want AI features in the repository path, and you value a fully open-source platform over the ecosystem. If the ecosystem is the point, stay with GitHub.
How to migrate from GitHub
It's the same Git protocol. Most repositories move in minutes.
$ git remote set-url origin https://repos.codetrunk.eu/you/your-app.git
$ git push -u origin main
# Done. Issues and PRs: use Forgejo's built-in migration.
$ _
1. Create your account
Sign up and verify your email. A Forgejo workspace is provisioned automatically.
2. Move your code
Point your remote at CodeTrunk and push, or use Forgejo's migration tool to import a repository straight from GitHub.
3. Bring your history
Issues, pull requests, and releases can be imported with Forgejo's built-in migration tools. Full Git history comes along either way.
Frequently asked questions
Common questions about switching from GitHub to CodeTrunk.
Is CodeTrunk a full GitHub alternative?
For the core workflow (Git hosting, private repositories, issues, pull requests, and code review), yes. CodeTrunk runs on Forgejo, a fully open-source Git platform with the same Git protocol. GitHub-specific extras like the Marketplace or GitHub Actions are not 1:1 compatible, but Forgejo Actions covers common CI needs.
Can I migrate my repositories from GitHub?
Yes. Change your Git remote URL and push, that is all it takes for the code. Issues, pull requests, and releases can be imported using Forgejo's built-in migration tools directly from GitHub.
Does GitHub store data in the EU?
Only with GitHub Enterprise Cloud with data residency, or with self-hosted GitHub Enterprise Server. GitHub.com stores data in the United States by default. The EU residency option requires Enterprise Cloud and has exceptions, including Copilot data outside the region unless the in-region Copilot policy is enabled.
Does GitHub train AI models on my code?
That depends on the plan and the setting. Since 24 April 2026, GitHub may use interaction data from Copilot Free, Pro, Pro+, and Max for model training unless the user opts out. Copilot Business and Copilot Enterprise are excluded, and private repository content at rest is excluded, but code processed while using Copilot is interaction data.
Can I move GitHub Actions workflows to CodeTrunk?
Yes, with edits. Forgejo Actions uses a GitHub-style YAML format, so jobs, steps, matrices, and services usually port. Marketplace actions referenced with uses need to resolve against data.forgejo.org or a full URL. Most small build-test-deploy workflows move in an afternoon; large pipelines with custom runners and deployment approvals take longer.
How much does it cost compared to GitHub?
The Free plan includes one private repository with 500 MB of storage, free forever. Paid plans start at €8/mo with unlimited private repositories. No credit card required to sign up.
Is my code used to train AI models?
No. We do not train AI models on your data, private or public. Your private repositories are never accessed for AI training by anyone. This is a contractual and technical prohibition: we have no data-sharing relationships with AI companies, no model ingestion pipelines, and no arrangements that allow training on your content.
Sources and further reading
Competitor claims on this page link to the vendor's own documentation, last checked 20 October 2026. Product terms change; check the source before you decide.
-
GitHub Enterprise Cloud with data residency
GitHub Docs · Default US storage and the available residency regions
-
About storage of your data with data residency
GitHub Docs · What stays in-region and what does not
-
Updates to GitHub Copilot interaction data usage policy
GitHub Blog · Published 25 March 2026, effective 24 April 2026
-
Managing GitHub Copilot policies
GitHub Docs · Plan differences and the training opt-out
-
About GitHub Enterprise Server
GitHub Docs · The self-hosted deployment option
-
GitHub Actions
GitHub Docs · Workflow and runner model
-
GitHub plans
GitHub Docs · Free and paid plan limits
Keep the workflow. Lose the trade-offs.
Create your account in seconds. A Forgejo workspace is provisioned automatically when you verify your email.
Start Building