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. gitbuild.dev 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.
| gitbuild.dev | 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 |
Why developers switch
Three reasons teams move their repositories to gitbuild.dev.
A host that cannot be shelved
AWS froze CodeCommit for sixteen months and told customers to migrate elsewhere before reversing course in November 2025. gitbuild.dev 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 gitbuild.dev 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.
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://git.gitbuild.dev/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 gitbuild.dev, 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 gitbuild.dev.
Is gitbuild.dev 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 gitbuild.dev, 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.
Is my code used to train AI models?
Never. Your source code is not used for LLM training, model ingestion, or any form of automated analysis beyond what is required to operate the service. This prohibition is contractual and technical — we have no data-sharing relationships with AI companies.
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