CodebahnCodebahn

What customers say. On their terms.

Named or anonymous, each customer's choice. Why they moved, what broke on the way, and how it worked out.

Last reviewed: 12 October 2026

“Since NIS2 we needed code residency in the EU. GitHub and GitLab offered more than we needed and were also more expensive. The combination of the price and the features made us pick Codebahn, and the support is really good too.”

An IT company in the Netherlands, on the Crew plan. Moved from GitHub in 2026.

Their first payment hit a bank error, and retries got flagged as fraud. They switched to iDEAL (which we added days later, along with PayPal and SEPA). They started the move by mirroring everything from GitHub. When 90 mirrors needed converting, they wrote a script against the API rather than doing it by hand. That script inspired the repo convert command that is now in the CLI.

“I was looking for a version control system that is GDPR compliant. There are not so many tools on the market, SaaS-based. Yours made the best impressions, and so far I am very satisfied.”

An AI agency owner in Germany, on the Solo plan. Moved from GitHub in 2026.

Alexander moved several repositories from GitHub. Midway through, he had a question and opened the site chat expecting a bot. He got a human instead, and an answer within minutes.

“I have nothing to hide in my source code but I object to the USA’s bully boy tactics of the Cloud Act. ... I am happy to pay for services like your excellent Codebahn. The pricing is perfect for me at this stage.”

An embedded engineer in the UK, on the Solo plan. Moved from GitLab in 2026.

They moved from GitLab with several binary-heavy repos and switched to LFS to keep large objects out of the git history. They also needed a way to organize many repos without GitLab-style groups. No equivalent exists yet, but that conversation shaped a feature: topic filtering shipped the same day, letting them tag and find repos by project.

Names are the customer's choice

Many of the people and companies here chose Codebahn to keep their work, and often themselves, private. Named or anonymous is entirely their call.

We publish stories because choosing a Git host means trusting a company you cannot see inside. What you can check is the detail: changes that match dated entries in the changelog, and the offer below to hear it from a customer directly.

How we quote customers

  • Word for word. Anything cut is marked with an ellipsis.
  • Named or anonymous. The customer's choice. Anonymous customers write their own description, or approve ours.
  • Consent covers the placement. A quote approved for this page appears nowhere else without asking again.
  • Never paid for. Not with money, not with discounts, not with features.
  • Only current customers. If someone leaves, or asks, their story comes down within a week.

Stories come from our conversations with customers. Every customer agreed to theirs in writing, and the same rules appear in the privacy policy.

Hear it directly

Want to hear it from a customer? Email Simon and we will ask if one of them is willing to talk to you.

14-day money-back guarantee.