The Gitea workflow,
without the server.
Everything you like about Gitea. Someone else does the ops.
CodeTrunk 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.
| CodeTrunk | 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 |
| Contracting entity | StennMedia, Netherlands (KvK 99876302) | Your own company (self-hosted) |
A Dutch company, not a US subsidiary
CodeTrunk is operated by StennMedia, registered with the Dutch Chamber of Commerce under KvK 99876302 and established in Breda. The contract is governed by Dutch law and VAT is paid in the Netherlands. When your legal team asks who is accountable for the data, the answer is a European company with no US parent in the chain.
- Legal entity
- StennMedia
- Registration
- KvK 99876302
- Governing law
- Netherlands
Why developers switch
Three reasons teams move their repositories to CodeTrunk.
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.
The details behind the table
The vendor decisions and dates that a comparison table cannot show.
Gitea and Forgejo: same codebase, different governance
Forgejo started in 2022 as a fork of Gitea, after a dispute over governance and the project trademark. The codebases still share most of their history, the UI is nearly identical, and the API stays compatible, which is why migration tools and scripts usually work on both. The difference is who governs the project: Forgejo is stewarded by the non-profit Codeberg e.V. and is fully open source, while Gitea follows its own governance and release process. For a team choosing a platform for the next decade, that difference matters more than a feature checklist.
What self-hosting Gitea really involves
Gitea is light enough to run on a small VPS, and that is genuinely one of its strengths. The server is the easy part. You also own the backups and, more importantly, the restore tests; the SMTP setup that makes notifications arrive; TLS certificates; storage growth; security patches; and a monitoring path that tells you when the forge is down. None of this is impossible. It is simply a service you now operate, and the person who understands it is usually the same person writing code.
Gitea Actions and Forgejo Actions
Both projects adopted a GitHub Actions-compatible workflow format, with YAML files, jobs, runners, and actions fetched from a configured source. That makes a small pipeline familiar to anyone coming from GitHub. The operational details still differ: which runner you register, where actions are resolved from, and how much of the GitHub ecosystem is available. A workflow that calls a public action may work unchanged; a workflow tied to a marketplace action may need a replacement. Test your three most important pipelines before you move the repository.
When self-hosted Gitea is the right choice
If you need full control over the machine, run an air-gapped environment, or have specific integrations that only make sense on your own network, self-hosted Gitea is a defensible choice. The same applies if you already have someone who enjoys running it. CodeTrunk is for the other case: you like the Gitea workflow and the Forgejo software, but you would rather not own the server, the patches, and the backup restore drill. Both are valid; they are different jobs.
How to migrate from Gitea
Coming from self-hosted Gitea? This is the easiest migration there is.
$ git remote set-url origin https://repos.codetrunk.eu/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 CodeTrunk.
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. CodeTrunk 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. CodeTrunk 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.
Do my Gitea Actions workflows work on CodeTrunk?
Usually, with small edits. Forgejo Actions uses a GitHub Actions-compatible workflow format, and Gitea Actions does the same. Jobs, steps, matrices, and services are familiar. Check the actions you reference: a public action may resolve, a marketplace-specific one may need a replacement.
Who governs Forgejo?
Forgejo is governed by the non-profit Codeberg e.V. and is fully open source. CodeTrunk runs Forgejo as a managed service but does not control the upstream project, which is exactly why the software cannot be re-licensed out from under you.
Is my code used to train AI models?
No. We do not train AI models on your data, private or public. Your private repositories are never accessed for AI training by anyone. This is a contractual and technical prohibition: we have no data-sharing relationships with AI companies, no model ingestion pipelines, and no arrangements that allow training on your content.
Sources and further reading
Competitor claims on this page link to the vendor's own documentation, last checked 20 October 2026. Product terms change; check the source before you decide.
-
Forgejo governance
Forgejo · Governance under Codeberg e.V.
-
Forgejo documentation
Forgejo · Installation, Actions, and migration
-
Gitea documentation
Gitea · The upstream project and its feature set
-
Gitea Actions overview
Gitea · Workflow compatibility and runner model
-
Gitea installation guide
Gitea · Self-hosting requirements
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