Frequently Asked Questions

Short answers, and honest ones. Where this page and a sales conversation disagree, this page wins.

What Git.eu is right now

What is Git.eu?

A software forge hosted in France and run by a European company — a Git forge, and more than one. You push code to it, review it, track issues, and nobody outside Europe can be compelled to hand it over. That is the whole idea.

What can I actually do with it today?

Host as many repositories as you like, public or private, within the storage your plan includes. Open issues, open pull requests, review code, keep a wiki. Import your existing repositories with their history.

What you cannot do in September is give anyone else access — not a collaborator, not a client, not even to read. Invitations arrive in October, organisations in November.

Is this a finished product?

No, and we would rather say so on the way in than have you find out on the way through. Git.eu is in open beta until 31 December 2026. Things are missing, and the list of what is missing is on this page rather than hidden behind a demo request.

What is coming, and when?

• April 2026: closed beta on crash-test server
• September 2026: open beta on first production server
• October 2026: guest account — read and comment.
• November 2026: organisations and team accounts.
• 1 January 2027: pay subscriptions open, and the API and webhooks ship the same day. CI/CD is planned and not dated — when we can name a month, it will appear on the pricing page before it appears anywhere else.

These are the months we are working towards. If one of them slips we will change the dates and say why. We would rather be seen moving a date than caught having moved it quietly.

What it does not do

Do you have CI/CD?

No. There is no pipeline runner on Git.eu, and we are not putting a month on it yet.

If your work depends on tests running next to your code, we are not the right home for you — not in September, and not in November either. We would rather tell you that here than after you have moved.

Do you have an API?

Not today. It ships 1 January 2027, with the commercial launch — same day, not "coming soon." Until then, everything happens through the web interface and through Git itself.

Git is the API for most of what matters in the meantime: clone, push, pull and fetch all work exactly as they do anywhere else, with any client you already use. What you cannot do until January is script the things around your code — creating repositories, opening issues, reading pull requests.

Do you have webhooks?

Not today — same date as the API, 1 January 2027, with the commercial launch. Until then, no external system finds out that you have pushed: you cannot wire Git.eu into a CI service you already pay for, and you cannot trigger a deployment from a push.

I need one of these now — what can I do?

Write to us with what you need most, and we will follow up for details and add it to the roadmap. Roadmap priorities are shaped in part by that feedback, so do not hesitate to reach out.

So what is Git.eu good for right now?

Code you want kept somewhere under European jurisdiction, where automation is not the point: new projects, repositories you have never wired up to anything, infrastructure and configuration, documentation, internal tooling, and the work of people who bill clients rather than run pipelines.

If that describes some of your repositories but not all of them, move some of them. A forge is not a monogamous commitment.

Can I self-host Git.eu?

Not today. If you need a dedicated or on-premise deployment, write to us at support@git.eu — we are building the 2027 roadmap and we would rather hear from you now than guess.

What it costs

How much is it?

Every plan and its price, monthly or annual, is on the pricing page: git.eu/pricing.html. One published price list, the same for everyone, no negotiated rate.

How much do I actually pay, with tax?

A business with a VAT number pays the price excluding VAT. An individual pays the VAT rate of their EU country on top. The pricing page shows prices with and without VAT — git.eu/pricing.html — and you see the exact number before you enter a card, not after.

Is there a free plan?

Only for students. Everyone else pays.

Why is there no free plan?

A free plan is always paid for by someone. On the large platforms it is paid for by the paying customers, by advertising, or by the data itself — including what that data is worth as training material. We have chosen none of those.

That leaves one way to fund infrastructure: the people who use it pay for it. It is a harder commercial position and it is the only one consistent with everything else we tell you.

I run an open source project. Is there anything for me?

Not beyond the student plan. If your project is open source and you are looking for a free European home, Codeberg does excellent work. We mean that.

How does the student plan work?

Free, permanently, with the full product. Sign up with an email address at a higher-education institution — a university, a grande école, or an equivalent body. We verify the address itself: no card, no document, nothing to upload. We ask again at the start of each academic year. Secondary schools are outside the scheme. Available from 1 January 2027.

What is the beta founder rate?

Any account created during the open beta gets a discount on its first annual subscription. Applied automatically at checkout, no code to enter. The discount and the dates it applies to are on the pricing page: git.eu/pricing.html. After the first year you move to the published rate.

Closed-beta users who trusted us early: open a ticket and we will give you a better offer.

Do I need a card to join the beta?

No. We do not ask for payment details until you choose to subscribe, on or after 1 January 2027.

Can I switch from monthly to annual later?

Yes, at any time.

The beta, and what happens on 1 January

What does the beta actually mean for me?

It is free, it is open to anyone, and it runs until 31 December 2026. Your repositories are real and so is your data — beta describes the feature set, not the reliability.

Will I be charged automatically when it ends?

No. Nothing happens to your card, because we do not have it. You will never be moved onto a paid plan without saying so yourself.

So what does happen on 1 January?

If you subscribe, nothing changes. If you do not, your account switches to read-only: you keep full access to read, clone, pull, download and export, and you cannot push new commits or open pull requests. Your data is intact and it is yours.

Can I subscribe later?

Yes, any time before 28 February 2027. Everything comes back exactly as it was.

And on 28 February 2027?

Accounts without a subscription, and their data, are deleted permanently. We will have emailed you three times before then — 30 days, 7 days and 24 hours ahead.

Storage

How much do I get, and what counts?

The storage your plan includes — see git.eu/pricing.html — and everything you store counts towards that one number. No separate allowance for large files, no second counter that runs out first, no line item you discover on an invoice. There is nothing else to read.

Large files (Git LFS)?

Git LFS is supported on every repository. Each LFS object has a size ceiling set per instance; the default is in the Git LFS guide.

What if I need more?

Extra storage is sold per month, for as long as you need it. Same price for everyone, published on the pricing page like the rest: git.eu/pricing.html.

What happens if I go over?

Your account switches to read-only and we tell you — at 80% and again at 100%, before you cross the line rather than after. Nothing is charged.

If you would rather keep working and pay for the extra storage, you can turn that on yourself and set the monthly ceiling. It is off until you turn it on. We will never take a payment you have not authorised.

What will you never charge me for?

• Adding a repository
• Getting your data out
• A copy of your invoices, your DPA or our security documentation
• Talking to a human when something breaks

Your code, and who can reach it

Where is my code physically stored?

In Paris, on infrastructure operated by Scaleway — a French company, part of the Iliad group. Your code does not leave the European Union.

Can I choose where my code is hosted?

Yes — that is the shape of the product. Git.eu runs one instance per country, and you choose which one your account and your repositories live on. Today there is one, in France. As others open, choosing an instance is choosing the jurisdiction your code answers to, and nothing moves you from one to another without you asking.

So you do not run your own datacentre?

No, and we would rather say so. Production runs on dedicated servers, rented from a French company, in a European datacentre in Paris. We do not own the hardware or the building — owning either would cost more, break more often, and make your code less safe, not more. Backups are the exception: they sit on hardware we own, in our own premises, which is why no other company ever holds a copy of your code.

What matters is not who owns the building. It is who can compel access to what is inside it — and the answer is: European courts, under European law.

Who else processes data for you?

Five companies, and here they all are. Scaleway (France) hosts your repositories. Mollie (Netherlands) handles card payments. Wise Europe (Belgium) handles bank transfers. Infomaniak (Switzerland) sends our email. Billit (Belgium) issues our invoices.

None of the five is subject to US law, and none of them can read your source code. Your backups are not on that list, because we hold them ourselves.

One of them is Swiss, not EU. Does that matter?

It is a fair question, so here is the precise answer. Infomaniak sends our email — notifications, receipts, the messages we send you. Switzerland sits outside the European Union, but the European Commission has recognised its data protection regime as adequate since 2000, renewed in January 2024. Three of our four providers are in the European Union; the fourth is in a country the Commission has formally judged to protect your data to European standards.

Do you train models on my code?

No. Never, ours or anyone else's. That commitment is contractual, not editorial.

Is there a data processing agreement?

Yes, included at no extra cost, and you can read it before you subscribe: git.eu/legal/dpa.html.

Who can compel you to hand over my code?

A European court, following European procedure. We are a European company, our infrastructure is European, and every company that processes data for us is European. There is no US parent, no US subsidiary and no US subprocessor in the chain — which means there is nothing for a foreign order to attach to.

What happens to my code if Git.eu is bought?

You already have it. Every clone is a complete repository — full history, every branch, every tag — sitting on a machine we do not control. That is a property of Git, not a favour from us, and no change of ownership can reach it.

What we hold that Git does not — issues, pull requests, settings — you can export at any time, in an open format, free, without telling us why. That is true today and it stays true whoever owns the company.

We are not going to tell you that Git.eu can never be bought, or that a future owner would be bound forever by this page. Nobody can promise that, and a company that does is selling you something it cannot deliver. What we can promise is the part that does not depend on who owns us: leaving takes an afternoon, costs nothing, and is documented before you need it rather than after.

One thing does outlive us. The commitment that your code is never used to train a model is in your contract, not on this page — and a contract survives a change of ownership.

Coming and going

Can I bring my repositories over?

Yes, from any Git repository — GitHub, GitLab, a self-hosted server, anything with a URL — with your full history, branches and tags. What does not come across is what does not live in Git: issues, pull requests, reviews and settings. If those matter to you, keep the original repository until you are sure.

Can I get everything back out?

Yes. It is Git — clone it and you have it. We also provide an export of everything Git does not hold — issues, pull requests and settings — in an open format, at no charge and without asking why. (Exact export scope still to confirm.)

Leaving should be as easy as arriving. A promise about independence is not worth much if the way out is not documented on the page that asks you for money.

Do you back my code up?

Yes. Everything we hold is backed up daily — your repositories, and the issues, pull requests and settings that Git does not carry. The copies leave our Paris site for a second location in France, on hardware we own and run ourselves: no other company ever holds a copy of your code. They are encrypted, and the keys are kept away from the machines that hold them. The backup cycle overwrites them after 30 days.

That is us not losing your data. It is not the same thing as you getting back a branch you deleted yourself — for that, the clone on your own machine is still the fastest answer we can give you. There is no self-service restore: if you do need something recovered from a backup, ask us and we will do it.

What if Git.eu stops existing?

You still have every repository, because you have a clone of each one on your own machine — that is how Git works, and it is the honest answer to a question every small provider should be asked. The export covers everything Git does not: issues, pull requests, settings.

Teams, clients and collaborators

Can I show a private repository to my client?

Not in September — in October. Invitations are the next thing we ship: your client gets access to read, clone and comment, they cannot push, and they cost you nothing however many of them there are.

Can I use Git.eu with my team?

In November. Today an account is one person and repositories are not shared. Organisations arrive in November, with the Team and Business plans listed on git.eu/pricing.html.

Leave us your address and we will write to you the day it exists. One email, not a newsletter.

When teams arrive, who do I pay for?

The people who write code. A team account has three roles: developers, who push and approve merge requests, and are the only ones you pay for; managers, who administer the organisation without writing code; and observers, who read without paying. (Role and pricing table still to confirm with Renaud.)

If I subscribe in September, do I pay more when all this arrives?

No. Every feature on the roadmap is included in the Personal plan, and there is no version of it that costs more because it does more. When a feature ships, it ships to everyone paying. Team and Business are for groups — organisations, teams and companies — not a higher tier for one person: git.eu/pricing.html.

Buying, invoicing and paperwork

How can I pay?

Card, or SEPA bank transfer. Invoices carry a VAT number and are downloadable at any time. Intra-EU reverse charge applies to VAT-registered businesses. Annual invoicing and purchase orders are available on annual plans.

I am not in the European Union. Can I still use Git.eu?

Yes. We take international payments and invoice accordingly. Hosting in the EU is a promise about where your code sits, not a restriction on who you are — for some people, it is precisely the reason to come here.

I work for a public body or a regulated organisation. Is this for me?

Not yet, honestly. If you have requirements around dedicated instances, certification or on-premise deployment, write to us at support@git.eu — we are building the 2027 roadmap and we would rather hear from you now than guess.

Getting help

Something is broken. Who do I talk to?

A person, at support@git.eu. Talking to a human when something breaks is not something we will ever charge for.