deniz.in

Markets

Weather

Loading weather

· via Hacker News – Front Page (native)

Pushin.eu launches EU-only Git hosting with free private repos and GitHub-compatible API

Pushin.eu hosts public and private Git repositories on bare-metal servers in Paris, pairs a GitHub-shaped API with a migration CLI, and rules out AI training on user code.

Pushin.eu launches EU-only Git hosting with free private repos and GitHub-compatible API

Git hosting under EU jurisdiction only

Pushin.eu, a newly launched code-hosting service whose announcement reached Hacker News's front page on 5 September 2026, offers public and private Git repositories built around one central commitment: code stays inside the European Union. According to the company, repositories run on bare-metal servers it operates at Scaleway in Paris — a French provider, in French data centres — with no failover to any US region. The argument is jurisdictional rather than technical: as long as no US territory or US-based vendor sits in the chain, there is no obvious lever for the American CLOUD Act, the law that lets US authorities compel data from providers under US jurisdiction. GDPR and European law are presented as the frameworks customers actually deal with, alongside a general promise of a privacy-first posture.

Deliberately free of AI features

The platform is also explicit about AI. Pushin.eu states that it does not train models on customer code, does not allow partners to do so either, and ships no AI features at all — no buried opt-outs or fine print. It positions itself around developer experience and uptime instead of AI surfaces. The company also says it filters mass-produced, low-effort contributions of the kind repeatedly sprayed at popular open-source projects to rack up contributor credibility, framing the filter as a way to spare maintainers from burnout.

Moving code over from GitHub

Migration is handled by pun, the platform's command-line tool. Running pun import lists a user's GitHub repositories and, for the ones selected, transfers full git history together with labels, issues, and closed and merged pull requests including their comment threads — preserving original numbering, timestamps and author attribution. The import runs on the user's own machine, so the GitHub token never leaves it. Repositories from other git remotes arrive as plain git history without that surrounding metadata, since no API exists to read it.

Teams not ready to commit can mirror instead: a one-way sync from GitHub into Pushin.eu, with the mirror kept read-only to direct pushes so the two cannot diverge, and the sync can be run on demand, paused or removed at any time. Day-to-day work happens over SSH or HTTPS with a personal access token, and a REST API at /api/v1 uses the same endpoint shapes as GitHub's, so many existing scripts need only a new base URL. The company cautions that API coverage is partial rather than complete, and worth reviewing before porting anything large. Accounts can be secured with TOTP or a passkey.

A candid list of what is missing

The FAQ is unusually frank about gaps. Open pull requests do not migrate — only closed and merged ones arrive as history — and a long list of features is not built yet: rebase merges, Git LFS, webhooks, status checks, releases, packages, CODEOWNERS routing, milestones, required reviewers, repo-scoped deploy keys, cross-references between issues and pull requests, discussions, organisation-wide search and tag protection. Self-hosted CI runners are available today, and managed runners based on Firecracker are on the way. Getting data back out means git clone for repositories plus the REST API for issues, pull requests and comments; a one-click export archive does not exist yet.

Costs and access

Sign-up is invite-only: each member receives a small number of invitation codes to hand out, though public repositories can be browsed without an account at all. Both public and private repositories are free during the beta. Paid plans are intended eventually, but the company says it has not settled on their shape or price and would rather not publish a number that later changes.

Why it matters

European organisations that treat source code as sensitive data have had few realistic alternatives to US-headquartered platforms, and instruments like the CLOUD Act turn the physical location of a repository into a compliance question rather than a technical detail. Pushin.eu's combination of EU-only infrastructure, private repositories, GitHub-compatible API shapes and a working migration tool lowers the practical cost of switching for exactly those buyers. The caveats are equally clear: the published feature gaps, the invite-only access and an availability record that is still unproven make this a beta worth evaluating rather than a drop-in replacement for an incumbent host.

  • #git
  • #data-sovereignty
  • #code-hosting
  • #eu
  • #developer-tools

Related posts