An AWS CodeCommit alternative
with a steady roadmap.
Git hosting whose future does not depend on a cloud provider's quarterly review.
In July 2024, AWS closed CodeCommit to new customers and published guides for migrating away. The service returned to general availability in November 2025, but the episode made the point: a suite vendor can shelve your code host with a blog post. CodeTrunk is an independent, EU-hosted CodeCommit alternative powered by open-source Forgejo.
Side by side
The differences that matter when you choose a home for your code.
| CodeTrunk | AWS CodeCommit | |
|---|---|---|
| Product status | Git hosting is the whole product | De-emphasised for 16 months in 2024–25; AWS recommended leaving |
| Hosting jurisdiction | European Union only | US provider: your pick of AWS regions |
| GDPR & data protection | Native: EU law applies directly, DPA included | AWS data processing terms, US jurisdiction |
| Platform source code | Fully open source (Forgejo) | Proprietary, AWS-only |
| Access control | Organisations and teams in the UI | AWS IAM policies and credential helpers |
| CI | Forgejo Actions | Separate service (AWS CodeBuild) |
| Cost | Free plan, paid from €8/mo | Per-active-user AWS billing |
| Contracting entity | StennMedia, Netherlands (KvK 99876302) | Amazon Web Services EMEA SARL, Luxembourg |
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.
A host that cannot be shelved
AWS froze CodeCommit for sixteen months and told customers to migrate elsewhere before reversing course in November 2025. CodeTrunk runs on open-source Forgejo: even in the worst case, the platform itself lives on and you can self-host the exact same software.
No IAM degree required
Repository access on CodeCommit means IAM users, policies, and credential helpers. On CodeTrunk you create an organisation, invite your team, and push, access control designed for developers, not cloud auditors.
EU jurisdiction by default
Repositories, issues, and metadata stay in the European Union under EU law, no region picker, no transatlantic transfer frameworks, no data-residency addendum to negotiate.
The details behind the table
The vendor decisions and dates that a comparison table cannot show.
The 16-month closure, and the reversal
In July 2024 AWS stopped accepting new CodeCommit customers, paused feature development, and published guides for migrating to third-party Git providers. Sixteen months later, in November 2025, AWS reversed course and returned CodeCommit to general availability, reopening sign-ups and promising new investment. At the time of writing, some AWS pages still carried the old "no longer available to new customers" notice, which tells you how carefully the change was communicated. The episode is not a reason to mock AWS. It is a reason to ask how much a code host matters inside a much larger portfolio.
What CodeCommit is genuinely good at
CodeCommit is deeply integrated with AWS identity and networking. IAM policies control repository access, VPC endpoints keep traffic private, CloudTrail records API activity, and CodePipeline and CodeBuild connect without glue. For an organisation that already runs its compliance and deployment stack inside AWS, that integration is real value. It is also the reason the service survived the reversal: customers had built workflows around it, and ripping those out is expensive.
What the IAM model costs you
The same integration has a usability price. Repository access means IAM users, roles, policies, and a credential helper; there is no ordinary "invite a teammate to the organisation" flow. Pull request review is functional but sparse compared with a dedicated forge, and the CI service lives somewhere else. None of that is unworkable, but it shifts effort from writing code to administering cloud identity, and it makes the Git host feel like a component rather than a product.
Migrating without an importer
The code moves easily: create the repository on CodeTrunk, point the remote, and push every branch and tag. Metadata is the hard part. There is no CodeCommit importer, so pull requests, approval rules, and comments do not come along; teams push the branches behind open PRs and reopen the reviews that still matter. CodePipeline definitions become Forgejo Actions workflows or another CI system, and EventBridge or CodeBuild triggers become webhooks. A small repository is an afternoon; a heavily integrated AWS estate is a planned migration.
When CodeCommit is still the right answer
If your repositories, pipelines, identity, and audit trail all live in AWS, and your team is fluent in IAM, CodeCommit is a coherent choice. The same is true for regulated environments that need to keep source code inside an existing AWS boundary. CodeTrunk is for the team that wants a Git host to be a Git host: managed, EU-hosted, with a Dutch contracting entity, and without a cloud account as the price of admission.
How to migrate from AWS CodeCommit
Plain git push works, but there is no metadata importer, so plan for pull requests separately.
$ 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
Create the repository on CodeTrunk, point your Git remote at it, and push: all branches and tags included. Plain Git over HTTPS or SSH; no AWS credential helper needed.
3. Handle pull requests
Forgejo has no CodeCommit importer, so PRs do not carry over automatically. Push the branches behind open PRs and re-open them. Most teams finish in an afternoon.
Frequently asked questions
Common questions about switching from AWS CodeCommit to CodeTrunk.
Is CodeTrunk a full CodeCommit alternative?
For Git hosting, private repositories, pull requests, and code review: yes, and the review workflow is a genuine upgrade. If you wired CodeCommit deep into AWS (CodeBuild triggers, EventBridge rules, IAM federation), those integrations need rewiring as webhooks or Forgejo Actions pipelines.
How do I migrate from CodeCommit?
The code moves with plain Git: create the repository on CodeTrunk, change your remote URL, and push all branches and tags. Pull requests and approval rules do not carry over (there is no CodeCommit importer), so re-open active PRs from their branches.
Did AWS discontinue CodeCommit?
In July 2024 AWS closed CodeCommit to new customers, paused feature work, and recommended third-party Git providers. In November 2025 the service returned to general availability with a new roadmap. The whiplash is a fair data point about how much Git hosting matters inside a cloud portfolio: here, it is the entire product.
What is CodeCommit's status today?
AWS returned CodeCommit to general availability on 24 November 2025 and reopened sign-ups. At the time of writing, some AWS pages still showed the older notice that the service was closed to new customers, so confirm the current status in your account and region before you plan around it.
Can I keep AWS CodePipeline and CodeBuild?
You can keep them, but the integration changes: CodeCommit triggers become webhooks or polling, and build definitions move to Forgejo Actions or stay in CodeBuild. Teams that want to stay inside AWS often keep the CI there and use CodeTrunk only for Git hosting.
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.
-
The future of AWS CodeCommit
AWS DevOps Blog · Return to general availability, 24 November 2025
-
AWS CodeCommit
AWS · Product page and current availability notice
-
CodeCommit user guide history
AWS Docs · The July 2024 closure and November 2025 reopening
-
Migrate a CodeCommit repository
AWS DevOps Blog · AWS guidance for leaving
-
CodeCommit pricing
AWS · Active-user and storage billing
Move once. Stay because you want to.
Create your account in seconds. A Forgejo workspace is provisioned automatically when you verify your email.
Start Building