Managed Forgejo Hosting — production-ready from $15 a month
Community-led lightweight Git hosting platform with EU governance. Deployed on your own dedicated instance in AWS, Azure, or GCP, kept patched, backed up, and monitored by ManageStacks — standard Forgejo, no lock-in.
Forgejo is a community-led fork of Gitea providing lightweight, self-hosted Git hosting with issue tracking, pull requests, CI/CD, and package registries. ManageStacks deploys Forgejo with PostgreSQL, SSH access, and managed TLS pre-configured.
What does Forgejo do, and why do teams deploy it?
Forgejo is a community-governed fork of Gitea, maintained under Codeberg e.V. with EU-based governance. It provides a lightweight, fast Git hosting platform with built-in issue tracking, pull requests, code review, CI/CD via Forgejo Actions (GitHub Actions-compatible), container and package registries, and a wiki — all in a single binary that runs on minimal resources.
Forgejo is designed for teams and organizations that want GitHub-like functionality without vendor lock-in or the resource overhead of GitLab. It supports repository mirroring, branch protection, webhooks, OAuth2/OIDC authentication, and fine-grained permissions. The Forgejo Actions runner is compatible with GitHub Actions workflows, making migration straightforward.
ManageStacks deploys Forgejo with PostgreSQL for the database backend, SSH access for Git operations, managed TLS, and automated backups of repositories and metadata. Get a production-grade code hosting platform without provisioning servers or managing database maintenance.
- Git hosting with pull requests, code review, and branch protection
- Forgejo Actions CI/CD compatible with GitHub Actions workflows
- Built-in container and package registries
- Issue tracking with labels, milestones, and project boards
- OAuth2 and OIDC authentication with fine-grained permissions
- Repository mirroring and migration from GitHub, GitLab, and Bitbucket
Community-led lightweight Git hosting platform with EU governance
Forgejo as a self-hosted alternative to GitHub and GitLab
Instead of paying per-seat fees to a SaaS vendor, teams self-host Forgejo to keep full control of their data and infrastructure. ManageStacks removes the operational overhead — you get the cost and privacy benefits of open source with the reliability of a managed platform.
What does managed Forgejo hosting cost?
Flat per-app pricing, in your chosen AWS, Azure, or GCP region. No per-user pricing — a busy deployment costs the same as a quiet one.
Starter
Staging and internal tools. Dedicated instance, TLS, daily backups, managed upgrades.
Standard
Production workloads. Adds monitoring, staging environment, region choice, priority support.
Business
High-traffic and compliance workloads. Adds a high-availability replica and same-day support.
24×7 SRE retainer
Round-the-clock on-call across every hosted application, for teams that need a pager answered at 3am.
When is self-hosting Forgejo the right answer instead?
“Managed hosting is not always the correct call.”
Self-host when a platform team already runs the infrastructure and on-call rotation to operate Forgejo at genuinely low marginal cost. Self-host when compliance requires an air-gapped or on-premises deployment that no hosted option can satisfy. And self-host when the deployment depends on heavy customisation with a fast internal build-deploy loop, because an internal release process will beat any managed change process.
For everyone else — teams whose engineers have better things to do than shepherd upgrades — managed hosting is cheaper than the hours it replaces.
Which cloud should Forgejo run on — AWS, Azure or GCP?
For most workloads, the choice of cloud matters less than proximity: run Forgejo in the same cloud and region as the applications and data it talks to, because every request between them adds a round trip. The underlying compute performs equivalently across AWS, Azure, and GCP.
In practice, an existing cloud footprint decides it. All plans support all three clouds, and moving regions later is a scheduled migration, not a rebuild.
Deepest managed-service catalog, default when there's no existing footprint
Best fit for teams already on Microsoft 365 or Entra ID
Strongest for data/analytics-adjacent workloads
Every plan supports AWS, Azure, and GCP — region choice included.
Common questions about Forgejo on ManageStacks
What is Forgejo on ManageStacks used for?
Forgejo is a self-hosted Git hosting platform for source code, issues, pull requests, and CI/CD. ManageStacks deploys and maintains it so your development team gets GitHub-like features on your own infrastructure.
How is Forgejo different from Gitea?
Forgejo is a community-led hard fork of Gitea with EU-based governance under Codeberg e.V. It guarantees the project stays open-source and community-driven, with no single corporate owner. Functionality is largely compatible, with Forgejo adding its own features over time.
Can I migrate from GitHub to Forgejo on ManageStacks?
Yes. Forgejo includes built-in migration tools that import repositories, issues, pull requests, and labels from GitHub, GitLab, and Bitbucket. Forgejo Actions is compatible with GitHub Actions workflows, reducing CI/CD migration effort.
Does Forgejo support CI/CD on ManageStacks?
Yes. Forgejo Actions provides CI/CD directly in the platform, compatible with GitHub Actions workflow syntax. ManageStacks configures the runner infrastructure so your pipelines execute without separate CI server management.
Is Forgejo suitable for organizations with compliance requirements?
Yes. Forgejo runs entirely on your own cloud, giving you full control over source code residency. It supports branch protection rules, audit logs, OAuth2/OIDC SSO, and fine-grained repository permissions.
Other devtools tools on ManageStacks
Run Forgejo without carrying the pager
Subscribe through your AWS, Azure, or GCP marketplace. We handle provisioning, SSL, monitoring, backups, updates, and security. From $15/mo.