Fully Managed Forgejo
as a Service

Deploy Forgejo as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Forgejo is a self-hosted software forge — Git repositories, pull requests, issues, a package registry, and a wiki in one lightweight application. It is the GitHub-style platform you run yourself, governed by a German non-profit and licensed GPLv3+, so the code behind your code stays yours.

✓Free 7-day trial  ✓99.9% Uptime SLA  ✓No credit card  ✓Cancel anytime

✓Free 7-day trial  ✓99.9% Uptime SLA
✓No credit card  ✓Cancel anytime

Forgejo

Forgejo

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region — 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Forgejo Preview Image

ABOUT THE SOFTWARE

What is Forgejo

Forgejo is an open-source software forge for hosting Git repositories with code review, issue tracking, releases, and a built-in package registry. It runs as a single Go binary and started as a community fork of Gitea in December 2022.

Forgejo is licensed under the GNU GPLv3-or-later, a change made with version 9.0 in August 2024 to keep the project free software. It is developed under Codeberg e.V., a German non-profit registered in 2018, which holds the project's domains and trademarks and runs an elected governance model. The code lives at codeberg.org, the application is written in Go with a Vue.js front end, and it runs on Linux and ARM. A small instance idles below 200 MB of memory. The current long-term-support release, v15.0, shipped on 16 April 2026 as the 100th Forgejo release and is supported through 15 July 2027.

Forgejo is widely deployed. Codeberg, the largest public Forgejo instance, hosts more than 300,000 repositories and over 200,000 accounts as of November 2025. The Fedora project is migrating thousands of repositories to Forgejo across 2025 and 2026, with Fedora Release Engineering moving in November 2025. In April 2026 the Dutch government launched its own Forgejo platform, code.overheid.nl, run by the Ministry of the Interior's open-source office. These are organisations that chose a forge they could run and govern themselves.

FEATURES

What Forgejo does

Forgejo covers the full path from a push to a release. Repositories, review, issues, packages, and mirroring live in one application, so a small team does not stitch together five separate tools to ship software.

Git repository hosting

Public, private, and limited-visibility repositories with branch protection, signed commits, code search, and activity graphs, served from a single binary that idles below 200 MB of memory.

Pull requests and code review

Inline comments, required approvals, and code-owner-style routing, plus AGit-Flow for review by git push alone, with no fork or feature branch needed.

Issues and project boards

An issue tracker with labels, milestones, assignees, kanban-style boards, and templates. Version 13 added content reporting; version 15 added repository-scoped access tokens.

CI/CD engine

A built-in continuous-integration engine whose workflow files use GitHub-Actions-compatible syntax, so most existing .github/workflows files move across with minimal edits.

Package and container registry

One registry serving 23 ecosystems, including Docker and OCI images, npm, Maven, PyPI, Cargo, NuGet, Go modules, Debian, and Helm, with blob-level deduplication.

Wiki and releases

A per-repository wiki, tagged releases with downloadable artifacts, GPG-signed tags, and an attachment store that backs up cleanly with the built-in forgejo dump command.

Mirroring and migration

Built-in importers from GitHub, GitLab, Gitea, and other Forgejo instances, plus push-mirroring back to public forges and pull-mirroring from any Git URL on a schedule.

Single sign-on and access tokens

OAuth2, OpenID Connect, LDAP, and PAM login sources, instance-wide two-factor enforcement, and repository-scoped tokens that confine how far an API key reaches.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app on DANIAN ships with the same operational baseline. You do not choose a backup add-on or a monitoring tier. Hosting, patching, backups, SSL, and support are part of the €9, and they apply to Forgejo the same way they apply to everything else in the catalog.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers by email and ticket. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Forgejo

In December 2025, GitHub announced a per-minute fee for running CI on your own hardware, then paused it after pushback — but the direction was clear. The same year, GitHub's status page logged repeated multi-hour outages. More teams now want a forge they control.

Running Forgejo yourself is more than one docker run. Someone has to apply each security release, renew TLS before it expires, verify that last night's backup can actually restore, and pick a database that survives concurrent load. The Forgejo binary is small; the operational responsibility around it is not. That work does not show up until the week it goes wrong.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Forgejo on DANIAN

These three setups show who moves to managed Forgejo and why. Each is representative of a common migration pattern — the region, the configuration choices, and the integration points are the ones these teams ask us for most often.

8-PERSON SOFTWARE STUDIO

Leaving GitHub Team for flat cost and code custody

Around 60 private repositories with Git LFS for binary assets, hosted in a single region close to the team. They migrated off GitHub Team with the built-in importer — repositories, issues, pull requests, labels, and releases — then wired OpenID Connect single sign-on to their identity provider. We run PostgreSQL and nightly off-site backups.

DIGITAL AGENCY, 5 STAFF + CLIENT REVIEWERS

Hosting per-client code without paying per reviewer

One Forgejo organisation per client, repositories isolated with team-level permissions. Client reviewers cost nothing extra under flat pricing. A per-client container registry replaces a separate artifact store, and off-boarding hands the whole organisation to the client cleanly when an engagement ends.

OPEN-SOURCE PROJECT, CORE + CONTRIBUTORS

Moving off GitHub for governance and control

Public repositories with open registration gated against spam, plus a push-mirror that keeps a read-only GitHub copy so old links still resolve. Federated stars are enabled. The project follows the same path Fedora and the Dutch government took across 2025 and 2026 — a forge they govern, not one they rent.

COMPARISON

Four ways to run Forgejo

There are four common ways to get a Forgejo-style forge, or to avoid running one by paying for a proprietary alternative. Here is what each costs at one, five, and ten seats, and how much of your month each one takes.

Approach1 seat5 seats10 seatsYour ops time / month
Proprietary SaaSGitHub Team / GitLab Premium$4 / $29$20 / $145$40 / $290~0 (hosted)
Self-host on a VPS$24/mo production-class server~$44/mo~$44/mo~$44/mo1–2 h (€60–240)
Home servere.g. HP ProLiant ML30 Gen10 tower€210–667/mo*€210–667/mo*€210–667/mo*2–4 h
DANIAN managed Forgejoone instance, all your users€9/mo€9/mo€9/mo0

Only the proprietary row scales per seat — one Forgejo instance serves your whole team at a flat price. SaaS figures are list price per seat and exclude CI-minute overages, package and storage charges, and security add-ons; GitLab Premium is billed annually only. The VPS figure is a $24/mo production-class server plus off-site backup and monitoring — your time is on top. The home-server figure marked * amortises hardware over 36 months and includes power, business-grade internet, off-site backup, and operator time. Beyond cost, the deciding factors are who runs the box, whether the bill grows with every hire, and where the code sits — on DANIAN you choose the region and we do the operating.

BY INDUSTRY

Forgejo for specific industries

Some sectors put specific demands on a code forge: who may read source, how change is recorded, and where the data sits. These four sectors meet those demands differently, and the configuration we choose for each reflects that.

Government teams plan around the NIS2 Directive's supply-chain-integrity obligations, where custody of source and a record of every change matter as much as the code itself. We deploy in the region the body specifies, enforce instance-wide two-factor login through Forgejo's global two-factor requirement added in version 13, and connect single sign-on to the agency's existing identity provider. A typical workflow is publishing inspectable government source: public read access, signed releases, and recorded change history that a reviewer can follow. This is not theoretical — in April 2026 the Dutch government launched its own Forgejo platform, code.overheid.nl, and onboarded the national electoral council's vote-counting software within weeks of the soft launch.

Software companies now plan around the Cyber Resilience Act's duties to publish a software bill of materials and run coordinated vulnerability disclosure for the products they ship. We provision a PostgreSQL backend, require single sign-on, set protected branches with required approvals, and run encrypted off-site backups for the disaster-recovery question every reviewer asks. A common workflow keeps security advisories and the SBOM beside the source in the same forge, with every release tagged and signed, and the built-in registry standing in for a separate artifact server. The cost difference is concrete: a ten-developer team on a proprietary forge with its security add-on can pay over $1,200 per month, while the same team runs Forgejo here for a flat €9.

Agencies work under per-client confidentiality and least-privilege access to source, where one client must never see another's repositories. We set one Forgejo organisation per client, issue per-organisation access tokens, and enable OAuth2-provider mode so each client's own login can be connected. Onboarding a client means creating an organisation, inviting reviewers, and pushing the initial repositories; off-boarding transfers ownership of that organisation to the client and the agency steps away. The flat price changes the economics: inviting a client reviewer costs nothing, where a per-seat proprietary plan bills a full seat for every reviewer who has any project access — the reason many agencies simply stopped inviting clients to review at all.

Automotive teams follow the Automotive SPICE (ASPICE) software-construction process, which expects recorded review and a traceable change history for every line that ships in a vehicle. We enable AGit-Flow so engineers submit changes with git push origin HEAD:refs/for/main, opening a pull request with no fork and no feature branch. A typical workflow sees many small commits a day reach the main branch through AGit push, each gated by review before merge, with release branches cut as needed. Trunk-based development is a core practice of continuous integration, and automotive teams at FOSDEM 2025 named Forgejo's AGit support as the reason they chose it over the alternatives.

FAQ

Frequently asked questions

Three groups of questions: the technical detail of how we run Forgejo, how migration and onboarding work, and how billing, support, and the platform itself work.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

Forgejo was forked from Gitea in December 2022 after Gitea's trademarks and domains moved to a for-profit company without community approval. It lives under Codeberg e.V., a German non-profit, with elected governance. Forgejo became a hard fork in February 2024 and relicensed from MIT to GPLv3-or-later in August 2024 with v9.0. Migration from older Gitea is still straightforward.
Forgejo's setup wizard defaults to SQLite, which the project recommends only for low-to-moderate activity. We provision on PostgreSQL from day one. Switching databases on a live instance is not a trivial task, so starting on PostgreSQL means you never face a forklift migration when repository and review activity grows.
Forgejo's built-in registry serves 23 ecosystems, including Docker and OCI container images, npm, Maven, PyPI, Cargo, NuGet, Go modules, Debian, Helm, and RubyGems, with blob-level deduplication. One forge can replace a separate artifact server for most teams. Container packages can auto-link back to the repository that built them.
Partly. Federated repository stars are implemented, built on the ForgeFed extension of ActivityPub. Federated pull requests, issues, and user identities are on the roadmap but not yet shipped, and the Forgejo project treats federation as experimental and subject to breaking change. We enable what is stable and track the rest.
Yes. With AGit-Flow you push a change with git push origin HEAD:refs/for/main and Forgejo opens a pull request automatically — no fork or feature branch needed. You can pass a title and topic as push options. This suits trunk-based teams who want Gerrit-style review without branch sprawl.

02

Migration and onboarding

21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
Yes. Push-mirroring keeps a read-only copy on GitHub or GitLab so old links still resolve, and pull-mirroring syncs a remote repository on a schedule. Forgejo v15.0 fixed an authentication bug that previously made mirror credentials unreliable, so scheduled mirrors run cleanly on current instances.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on email and the ticket section in the client portal. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 email and ticket support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Forgejo for 7 days

No card. Cancel from the dashboard.