Gitea, without the server.
Managed for you, in the EU.
The Gitea workflow you already like. Someone else does the ops.
gitbuild.dev runs on Forgejo — a community-governed fork of Gitea — so the interface, API, and workflow are nearly identical. The difference is who runs it: no VPS, no upgrades, no backups, no mail server. Just managed Git hosting in the EU.
Side by side
The differences that matter when you choose a home for your code.
| gitbuild.dev | Gitea | |
|---|---|---|
| Platform | Forgejo — community-governed Gitea fork, fully open source | Gitea — fully open source |
| Who runs the server | We do — managed EU hosting | You do — VPS, Docker, or bare metal |
| Updates & security patches | Applied for you | Your job, on your schedule |
| Backups | Included, EU-based | You design and test them |
| Email notifications | Works out of the box | Configure your own SMTP |
| Data jurisdiction | European Union, GDPR-native | Wherever your VPS happens to be |
| Cost | Free plan, paid from €8/mo | Server costs + your time |
Why developers switch
Three reasons teams move their repositories to gitbuild.dev.
Same workflow, zero ops
Forgejo is a Gitea fork — your muscle memory, API scripts, and migration tools all carry over. What disappears is the server maintenance.
Ops done properly
Updates, security patches, backups, monitoring, and working email — handled as a service, not as your Sunday afternoon.
Still no lock-in
Because Forgejo is open source, you can export everything and go back to self-hosting Gitea or Forgejo whenever you want. Managed should mean convenient, not captive.
How to migrate from Gitea
Coming from self-hosted Gitea? This is the easiest migration there is.
$ 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
Change your Git remote URL and push — all branches, tags, and history included.
3. Import the rest
Issues, pull requests, and releases can be imported with Forgejo's migration tools from a Gitea instance. Then decommission the old server at your leisure.
Frequently asked questions
Common questions about switching from Gitea to gitbuild.dev.
Is Forgejo the same as Gitea?
Forgejo is a soft fork of Gitea, governed by the non-profit Codeberg e.V. It tracks Gitea closely and stays API-compatible, so clients, scripts, and migration tools that work with Gitea work with Forgejo. gitbuild.dev runs Forgejo.
Why pay for hosting when Gitea is free?
Gitea the software is free — running it is not. A VPS, backups, monitoring, email deliverability, and upgrade time all cost money or attention. gitbuild.dev starts with a free plan (one private repository, 500 MB), and paid plans start at €8/mo.
Can I move back to self-hosting later?
Yes — that is the point of building on open source. Export your repositories and metadata and run your own Gitea or Forgejo instance at any time. No lock-in.
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.
Keep the Gitea workflow. Drop the server.
Create your account in seconds. A Forgejo workspace is provisioned automatically when you verify your email.
Start Building