Azure DevOps is Microsoft's suite of Azure Repos, Boards, Pipelines and Artifacts, sold as a cloud service and as on-premises Azure DevOps Server; these pages cover moving to self-hosted GitLab, Gitea or Forgejo.
Compares Azure DevOps with self-managed GitLab, the closest single-platform replacement for Repos, Boards, Pipelines and Artifacts: issues and epics against work items, .gitlab-ci.yml against azure-pipelines.yml, package registries, and which GitLab tier covers what Azure DevOps teams use.
Compares Azure Repos and Pipelines with Gitea for teams that mainly need Git hosting, pull requests, package registries and GitHub Actions-style CI on their own server, and what Gitea lacks compared with Azure Boards and Test Plans.
Cost by component: Basic and Basic + Test Plans seats, parallel jobs, Artifacts storage and Advanced Security per committer, or Azure DevOps Server licensing, against servers, storage, upgrades, support and staff time for GitLab, Gitea or Forgejo.
What Azure DevOps Services keeps in its EU geography and what it does not, such as tokens and SSH keys stored in the US and macOS builds run in US GitHub datacenters, compared with Azure DevOps Server or a self-hosted GitLab, Gitea or Forgejo in an EU data center.
Comparing Azure DevOps with Forgejo, the GPL-licensed community fork of Gitea: repositories and pull requests, Forgejo Actions against Azure Pipelines, package registries, what has no Forgejo equivalent (Boards, Test Plans) and what each costs to run.
Moving Azure Repos to self-hosted Gitea: mirroring Git repositories (Gitea has no Azure DevOps importer, so pull requests stay behind), converting TFVC first, re-creating branch policies, and where Boards, Pipelines and Artifacts go when Gitea replaces only part of the suite.
Replacing Azure Boards work items, backlogs and sprints with self-hosted OpenProject, Plane or Redmine: how epics, features and user stories map, linking work items to commits in GitLab or Gitea, and exporting Boards data before the cut-over.
Azure Artifacts bills storage per GiB above a free 2 GiB. This page maps its NuGet, npm, Maven, Python and Universal Packages feeds and upstream sources to Pulp, Gitea or Forgejo package registries, and covers moving feeds without breaking builds.
What you can take out of Azure DevOps and how: Git repositories and TFVC history, work items through queries and the REST API within throughput limits, YAML versus classic pipeline definitions, secret variables that cannot be read back, and Artifacts feeds.
Azure DevOps Server 2022 has mainstream support until January 2028, and the next release moves to the Modern Lifecycle Policy that requires staying current. This page weighs upgrading on-premises, moving to Azure DevOps Services or replacing the server with self-hosted GitLab or Gitea.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.