A GitHub Enterprise alternative
with sovereignty built in.
Compliance-grade Git hosting under EU law, without per-seat pricing that scales against you.
GitHub Enterprise is the default for large engineering organisations, and it is priced and built like it: per-seat contracts, US jurisdiction, and AI features woven through the platform. CodeTrunk is EU-native Git hosting on open-source Forgejo, for organisations that answer to European regulators, works councils, or their own sovereignty requirements.
Side by side
The differences that matter when you choose a home for your code.
| CodeTrunk | GitHub Enterprise | |
|---|---|---|
| Hosting jurisdiction | European Union only | GitHub.com: US. Enterprise Cloud with data residency: optional EU. Enterprise Server: self-hosted |
| Pricing model | Flat team plans; Enterprise by agreement | Per-seat, every seat, every month |
| AI features | None: nothing to opt out of, no code processed for AI | Copilot woven through the platform |
| Platform source code | Fully open source (Forgejo) | Proprietary |
| Compliance story | EU law applies directly; DPA included | US-EU transfer frameworks and add-on agreements |
| Dedicated infrastructure | Available on the Enterprise plan | Enterprise Cloud is shared; Server is self-managed |
| Exit cost | Standard Git: a push away | Deep platform integration (Actions, Projects, marketplace) |
| 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.
Sovereignty that survives an audit
Repositories, issues, and metadata stay under EU jurisdiction, with EU data protection law applying directly and a DPA included. No transatlantic transfer frameworks to re-justify every year.
Costs that do not scale against you
Per-seat pricing is tolerable at twenty seats and painful at two thousand. CodeTrunk uses flat team plans, and the Enterprise tier is priced by agreement. Growth should not be a billing event.
No AI in the loop, at all
On GitHub Enterprise you manage Copilot policies and opt-outs. On CodeTrunk there is nothing to configure: no AI features process your code, and the prohibition on training is contractual, not a settings page.
The details behind the table
The vendor decisions and dates that a comparison table cannot show.
Three GitHub Enterprise shapes, three data paths
GitHub Enterprise is not one product. GitHub Enterprise Cloud is the shared SaaS on github.com, with data stored in the United States by default. GitHub Enterprise Cloud with data residency runs on a dedicated ghe.com subdomain and can store code and in-scope data in the EU, but requires Enterprise Cloud and managed user accounts, and still has documented exceptions. GitHub Enterprise Server is the self-hosted option, where you own the infrastructure and the upgrade work. A procurement conversation that does not name the shape is not really a comparison.
The Copilot policy at enterprise scale
GitHub says Copilot Business and Copilot Enterprise data is not used to train models, and that private repository content at rest is excluded from the training programme that started in April 2026 for individual plans. That is a meaningful protection, and it is stronger than the individual-plan default. It still leaves AI processing in the repository path: Copilot reads code when a developer invokes it, and enterprise administrators have to configure policies, content exclusions, and model restrictions. The question is not only whether training happens, but whether any model touches the code at all.
What per-seat pricing does at scale
GitHub Enterprise is priced per seat, with additional charges for Advanced Security, Copilot, Codespaces, and other products. At fifty developers the invoice is predictable. At two thousand it is a budget line that grows with every hire, and the renewal conversation is about volume, not fit. CodeTrunk uses flat team plans and prices Enterprise by agreement. That is not automatically cheaper for every organisation, but it changes the shape of the cost: headcount growth is not a billing event.
What a GitHub Enterprise exit actually involves
The Git repositories and their history move with a remote change and a push. GitHub's API can export issues, pull requests, comments, and releases, so the metadata is recoverable with work. The platform integrations are the real migration: Actions workflows, Marketplace apps, Packages, Pages, Projects, and Advanced Security results do not map one to one. An organisation that uses GitHub as its whole software delivery platform is not just moving a Git host; it is re-platforming. That is why the honest comparison is about scope, not a feature table.
When GitHub Enterprise is still the right answer
If you depend on Advanced Security, Codespaces, the Marketplace, or a global GitHub deployment with Copilot, replacing it with a smaller Git host is not a fair comparison. GitHub Enterprise Server also remains a legitimate option for organisations that need self-hosting and already have the operations team. The case for CodeTrunk is narrower and clearer: EU-hosted Git with a Dutch contracting entity, no AI features in the repository path, and a flat commercial model, for organisations that do not need the rest of the GitHub platform.
How to migrate from GitHub Enterprise
It is the same Git protocol, and Forgejo imports directly from GitHub.
$ 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. Talk to us
Enterprise migrations start with a conversation: seat counts, compliance requirements, and whether dedicated infrastructure fits.
2. Move your code
Point your remote at CodeTrunk and push, or use Forgejo's migration tool to import repositories 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 Enterprise to CodeTrunk.
Can CodeTrunk really replace GitHub Enterprise?
For the core workflow (Git hosting, private repositories, pull requests, code review, and CI via Forgejo Actions) yes, including organisation and team management. What it does not replicate is GitHub's marketplace ecosystem and ancillary products. Organisations with dedicated-infrastructure or compliance requirements can use the Enterprise plan.
Is there an Enterprise plan?
Yes. The Enterprise tier provides dedicated infrastructure for large organisations, priced by agreement. Business plans already include a DPA and unlimited organisation members; Enterprise adds isolation and a direct line for procurement.
How does pricing compare at scale?
GitHub Enterprise bills per seat, so the invoice grows with every hire. CodeTrunk uses flat plans (Pro and Business for individuals and teams, Enterprise by agreement), so headcount growth does not automatically raise your Git hosting bill.
Does GitHub Enterprise offer EU data residency?
Yes, on GitHub Enterprise Cloud with data residency, hosted on a dedicated ghe.com subdomain. It requires Enterprise Cloud and managed user accounts, and GitHub documents exceptions, including Copilot data outside the region unless the in-region Copilot policy is enabled. GitHub.com and ordinary Enterprise Cloud accounts store data in the US.
Who is the contracting entity?
CodeTrunk is operated by StennMedia, a Dutch company registered under KvK 99876302, with Dutch law governing the contract. GitHub contracts are with GitHub, Inc. or Microsoft Corporation, both US entities, even when data residency places the data in the EU.
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 · EU residency and the ghe.com deployment
-
About GitHub Enterprise Server
GitHub Docs · The self-hosted enterprise option
-
Updates to GitHub Copilot interaction data usage policy
GitHub Blog · Business and Enterprise exclusions
-
GitHub pricing
GitHub · Per-seat Enterprise and add-on pricing
-
GitHub Enterprise
GitHub · The enterprise product surface
Enterprise-grade Git. European jurisdiction.
Create your account in seconds. A Forgejo workspace is provisioned automatically when you verify your email.
Start Building