Glonce

Pushin launches EU-based Git hosting that blocks AI training on code

productsThe Glonce editorsHacker News🔥47Glonce rating47Impact35Novelty47Relevance76Surprise40Players12Credibility56

A new Git hosting service, presented under the domain pushin.eu, positions itself as an alternative to GitHub built around five stated commitments rather than AI features. First, repositories, public and private, stay hosted entirely within the EU, which the platform says removes exposure to US CLOUD Act subpoenas and to a foreign vendor able to lock a team out overnight; only GDPR and what it calls a privacy-first approach apply. Second, it blocks what it calls slop: low-effort, often AI-generated contributions that reputation hunters spray across popular open-source packages to get their name on a contributor list, which the platform frames as a driver of maintainer burnout. Third, it says it is built for developers rather than bots, with no AI buttons added to every surface. Fourth, it puts availability first, engineering for uptime so a team can ship at any hour. Fifth, it states plainly that it does not use customer code to train models, does not let partners do so either, and allows no exceptions, fine print, or hidden opt-out in its terms. Migration from GitHub runs through a command-line tool called pun: running 'pun import' with no arguments lists the user's GitHub repositories to choose from, and a GitHub import carries over the full git history along with labels, issues, and closed or merged pull requests including their conversation comments, preserving the original numbers, timestamps, and author attribution. The import runs on the user's own machine, so the GitHub token used never reaches the platform. Any other git remote can also be imported, but arrives as a git-only import, since there is no API to pull the surrounding metadata from. The platform exposes a REST API at /api/v1 whose endpoints match the shapes GitHub's API uses, so the site says most scripts written against GitHub need only a new base URL to work, though the API covers a good part of GitHub's surface rather than all of it. A companion pun CLI also drives repositories, pull requests, reviews, and comments from the terminal, and accounts can be secured with TOTP or a passkey. On getting data back out, the site says a plain git clone returns every repository in full, with its complete history, and that issues, pull requests, and their comments can be read through the REST API, but there is no one-click export archive yet; that is described as still on the platform's list of planned features. The page's own FAQ lists the question 'What does it cost?' but the retrieved text does not carry an answer to it, and the page gives no company name, founders, funding information, launch date, user count, or repository count beyond describing itself as EU-hosted.

Key facts

  • pushin.eu hosts public and private Git repositories entirely within the EU, which it says avoids US CLOUD Act subpoenas and keeps only GDPR in play.
  • The platform blocks low-effort, reputation-farming contributions ('slop') instead of enabling them, and states it never uses customer code to train AI models, with no exceptions for partners.
  • A CLI tool called pun handles GitHub migration, importing full git history plus issues, labels, and pull requests with original timestamps and authorship intact, running locally so the GitHub token stays with the user.
  • Its REST API at /api/v1 mirrors GitHub's endpoint shapes, so existing GitHub-facing scripts need only a new base URL, though the API does not cover all of GitHub's surface.
  • There is no one-click export archive yet (data must be pulled out via git clone plus the REST API), and the page states no pricing, company name, or user and repository counts.

Why it matters

The pitch is data sovereignty plus a stance against AI. Keeping repositories inside the EU is framed as protection from US CLOUD Act subpoenas and from a distant vendor that could lock a team out overnight, an argument aimed squarely at developers uneasy about US-based platforms. The second pillar, refusing to train models on customer code and blocking low-effort automated contributions, targets two separate frustrations that have grown around GitHub specifically: AI features layered onto the product, and a rise in low-quality, often AI-generated pull requests aimed at padding contributor profiles rather than fixing anything.

Who it affects

Developers and teams concerned about US jurisdiction over their code, and open-source maintainers worn down by low-effort contributions from reputation hunters, are the platform's stated audience. Anyone already scripting against GitHub's API is also a target, since the site says its own API mirrors GitHub's endpoint shapes closely enough that most such scripts need only a new base URL.

How to use it

Moving from GitHub runs through a CLI tool called pun: 'pun import' with no arguments lists the user's own GitHub repositories to choose from, and a GitHub import brings across the full git history along with labels, issues, and closed or merged pull requests with their comments, keeping the original numbers, timestamps, and author attribution. It runs locally, so the GitHub token never leaves the user's machine. Any other git remote can be imported too, but arrives as a git-only import, without the surrounding metadata, since there is no API to read it from for other hosts. Accounts can be secured with TOTP or a passkey, and the pun CLI also drives repositories, pull requests, reviews, and comments from the terminal. The page does not state what the service costs.

How solid is it

The story rests entirely on the platform's own marketing and FAQ page; nothing here is independently verified. Discussion of it on Hacker News was minimal, four points and one comment. The page names no company, no founders, no funding, no launch date, and gives no user or repository counts, and it describes the slop-blocking mechanism only as something that happens, without saying how contributions are actually screened.

Risks and caveats

There is no one-click export archive yet: getting data back out means combining a git clone for repository history with separate REST API calls for issues, pull requests, and comments. The platform gives no detail on how it detects and blocks 'slop' contributions, which leaves open the possibility of false positives against genuine low-effort-looking but legitimate contributions. Its API is stated to cover only a good part of GitHub's surface rather than all of it, which could matter for teams porting larger integrations. With no pricing, adoption figures, or company background disclosed, none of the platform's promises, EU-only hosting, no AI training, or high availability, can be checked against a track record.

“Public and private Git repos, hosted 100% in the EU, on a platform built for humans, not AI. We block slop, never use your code to train models, and focus on availability, not shiny AI features.”

— pushin.eu