GitHub Alternatives 2026: GitLab, Bitbucket, Gitea, Codeberg, Azure DevOps, SourceHut and AWS CodeCommit

GitLab is the strongest broad replacement for GitHub; Gitea is the first shortlist entry when you want to run the platform yourself. These 7 GitHub alternatives split into managed services and self-hosted software, but the decision turns on what must move with your code: reviews, issues, CI/CD and access controls.

Verified against the makers' live pages on 5 November 2026. This is a documentation and pricing comparison, not a hands-on migration test. Availability means the maker currently offers signup, purchase or installation; it does not mean an account was created or a contract approved.

GitHub alternatives at a glance

Choose the operating model before the vendor. A managed service runs the code-hosting platform for you. Self-hosted software puts its installation, backups and recovery under your control. A self-hosted CI runner, the machine executing build jobs, does not by itself make a cloud code host self-hosted.

The prices above are entry points, not equivalent packages. The linked pricing lines in each section identify the maker's terms. A free software license does not pay for your server, and a repository subscription does not necessarily include an AI assistant, an issue tracker or unlimited build capacity.

Before moving for cost alone, compare the alternative against GitHub's current pricing page and our GitHub pricing breakdown. Write down which capability is forcing the move. Otherwise, a lower seat price can conceal a larger migration and maintenance bill.

Managed alternatives to GitHub

Managed hosting is the sensible default when nobody on your staff owns the availability of development infrastructure. Your engineers can still control repository permissions and run private build machines; the provider maintains the hosting application. Within this group, the important split is between broad development platforms and services designed around a particular community or cloud.

GitLab: the strongest broad replacement

GitLab is a development platform that combines repositories, issue tracking, merge requests and CI/CD, the automation that builds, tests and delivers software. It is the best first evaluation for a company that wants its code review and delivery process to remain together after leaving GitHub. A product team with application code, a backlog and a release pipeline can evaluate the whole working loop in one destination. The wall is that this is still a platform migration: familiar concepts do not make permissions, automation or historical discussions identical.

Best for: Engineering leads replacing several connected GitHub workflows.
Standout: A GitHub importer that handles collaboration metadata as well as repository data.
Pricing: Free $0; Premium starts at $29/user/month, billed annually, on the GitLab pricing page.
Free trial: The maker offers a paid-plan trial alongside the ongoing Free plan.

CI/CD, issues and reviews: All are part of the platform. Merge requests are GitLab's equivalent of pull requests: proposed changes that reviewers discuss before merging. GitLab.com Free lists a 5-user top-level group limit and 400 compute minutes per month. A top-level group is the organizational container holding projects and members. Do not apply those hosted allowances to a self-managed installation or assume they buy dedicated computing capacity.

AI coding assistant: GitLab Duo is the maker's AI offering, with assistance in IDE extensions and the GitLab interface, plus agents and automated workflows. An IDE is the editor environment where developers write and debug code. Availability and usage depend on the plan, deployment and GitLab Credits; a Free hosting account is not a promise of free access to every Duo feature. The Duo documentation also describes hosting supported models and an AI gateway, which requires its own deployment evaluation.

Import from GitHub: The GitHub importer documentation supports repository data, issues, pull requests, comments and other project metadata. It does not migrate GitHub organizations or groups as organizations or groups. Markdown attachments are optional imports, so deleting the source too early can break historical links. That distinction matters when an old incident ticket contains the only screenshot explaining a production failure.

GitLab vs GitHub: the decision that changes the answer

Choose GitLab when consolidating delivery and collaboration is worth changing the operating workflow. Stay with GitHub if the main complaint can be fixed through access policy or billing controls and your release process depends heavily on existing integrations. Moving because an assistant is unpopular, without checking whether Duo will also be enabled, does not resolve the underlying policy decision.

For the pilot, choose a repository with enough history to reveal problems: a closed review with comments, an issue attachment and an active release process. A nearly empty repository proves very little. Have a developer and the person who approves releases inspect the result together; they notice different failures.

1. 1

   Prepare a destination and limited import access

   Create the destination group and confirm the importing user has the required Maintainer or Owner role. Enable the GitHub import source if you operate GitLab yourself. Use an approved OAuth connection or the documented token method, scoped to the migration.

2. 2

   Run the GitHub importer

   Select Create new, then New project/repository, Import project and GitHub. Authorize access, choose the repository and review the destination namespace and optional attachment settings before starting.

3. 3

   Accept the collaboration history separately

   Compare branches, tags, issues, review comments and attachments with the source. Verify identities and access deliberately. Keep GitHub available while you resolve discrepancies; a completed import is not evidence that every historical link works.

4. 4

   Rebuild the release path before cutover

   Configure the destination pipeline, credentials and release approvals. Rehearse a release and a rollback. Then designate the new canonical repository and remove temporary migration access. GitLab's repository mirroring does not synchronize subsequent GitHub pull-request changes.

Bitbucket Cloud: choose it when Jira already organizes the work

Bitbucket Cloud is Atlassian's managed repository and review service, with Pipelines for builds and deployments. It fits a company whose developers already plan work in Jira and want repository activity tied to those work items. The practical benefit is keeping a change connected to the task that justified it. The wall is issue tracking: Bitbucket's native Issues and Wikis have been retired, so it is no longer a sensible choice for someone specifically seeking a small standalone tracker beside each repository.

Best for: Teams with an established Jira workflow.
Standout: Repository and pipeline activity connected to work tracking.
Pricing: Free for up to 5 users; Standard starts at $3.65/user/month on the Bitbucket pricing page.
Free trial: Standard and Premium trials are offered.

CI/CD, issues and reviews: Pipelines is integrated; the Free plan lists 50 build minutes per month. Pull requests and reviewers are supported, while enforced merge checks are a paid-tier consideration. For issues, plan around Jira or another tracker. Atlassian's Issues and Wikis retirement notice confirms removal on 20 August 2026.

AI coding assistant: Atlassian's offering is Rovo Dev, including coding assistance and code review, but its packaging is changing. The Rovo Dev transition notice says the standalone product is heading toward end of life, Code Reviewer is moving into eligible Jira and Teamwork Collection subscriptions, and the CLI is evolving into Rovo CLI. The final standalone end-of-life date was not confirmed on the page checked. Ask for the entitlement that applies to your organization; do not budget as though a Bitbucket seat automatically includes an unchanged standalone assistant.

Import from GitHub: Use Create, Repository, then Import repository with the GitHub repository URL and authentication where required. Atlassian documents a repository importer, not a complete transfer of GitHub issues, reviews and organization policy. Treat those as separate workstreams.

For a team already using Jira, mapping GitHub issues into the existing project may be a reasonable cleanup exercise. For a small company using only GitHub Issues, it can instead create a new system to administer. Decide who will maintain issue links and historical references before treating the seat price as a saving.

Verdict: Bitbucket earns its place through the Atlassian workflow. If you do not want Jira, that advantage weakens substantially.

Azure DevOps Services: strong for work planning and Microsoft-oriented delivery

Azure DevOps Services is Microsoft's hosted suite of Repos, Boards and Pipelines. It is a good fit when work items, release processes and organizational administration matter more than matching GitHub's social experience. A business building internal applications can keep the task, code change and deployment discussion within the suite. Its wall is scope: moving to Azure Repos does not preserve every GitHub-specific feature, including every feature carrying the Copilot name.

Best for: Organizations that want planning and delivery infrastructure together.
Standout: Work items in Boards linked to repository and pipeline work.
Pricing: Basic includes the first 5 users free, then $6/additional user/month, on the Azure DevOps pricing page.
Free trial: The Basic free allowance is ongoing; it is not the separate Test Plans trial.

CI/CD, issues and reviews: Azure Pipelines provides CI/CD, Boards tracks work items, and Repos provides pull requests. The advertised free hosted pipeline allowance includes one parallel job with 1,800 minutes per month. A parallel job is capacity to run a job at a time, not a promise that all queued builds start together. Current parallel-job documentation says linking a valid Azure subscription enables the free grant for private projects.

AI coding assistant: GitHub Copilot code review for Azure Repos is in public preview, with organization and repository controls and billing through a linked Azure subscription. It can comment on changed code before human review. However, the separate Azure Boards handoff that asks Copilot to implement a work item still requires a GitHub repository. Microsoft's Azure Repos review documentation and Boards coding integration requirements describe different integrations. Neither a blanket “Copilot works” nor “Copilot is unavailable” is precise enough for this buying decision.

Import from GitHub: Use the repository import flow with the source Git URL and the required authentication. Microsoft's Git import guide covers importing into a new or empty destination repository. Large File Storage, or LFS, keeps large binaries outside ordinary Git objects: its pointers can arrive with the repository while the underlying files still need transferring. Plan GitHub issues and pull-request history separately.

The useful pilot is an existing service with a build artifact and a deployment approval, not just a source-only library. Ask the release owner to trace a proposed change from its Boards work item to a finished deployment. If that path is clearer than the one you have, the suite is doing useful work. If developers now need to update multiple trackers manually, the migration has introduced a coordination problem.

Codeberg: excellent for free software, unsuitable for a private product company

Codeberg is a nonprofit hosted forge, a service for code and collaboration, built on Forgejo. It is a strong choice for a public library or community project whose contributors want free-software governance. Its wall is eligibility: it is not a general commercial hosting service for your private SaaS code. The service's mission and resource rules are part of the product decision, not small print to handle after migrating.

Best for: Free and open-source projects aligned with the nonprofit's mission.
Standout: Community-oriented hosting with an explicit stance on AI training.
Pricing: $0 for eligible use, funded by optional donations and membership, according to the Codeberg FAQ.
Free trial: Eligible hosting is ongoing; there is no commercial trial-to-upgrade path.

CI/CD, issues and reviews: Issues and pull requests are available. Woodpecker CI requires an access request and manual approval. Forgejo Actions can use self-hosted runners, with a limited hosted service in open alpha. The CI documentation makes those conditions explicit. “CI available” does not mean every new project immediately receives a managed runner fleet.

AI coding assistant: No first-party coding assistant is advertised in the product pages checked. Codeberg says it will not use hosted project or user data to train generative AI and restricts heavily LLM-generated projects. Its published policy explanation also distinguishes active established communities and occasional generated contributions from projects created or maintained heavily by agents. Do not flatten that into a claim that any historical AI contribution automatically disqualifies a project.

Import from GitHub: Choose the plus menu, New Migration and GitHub, then provide the required access token and select the metadata to transfer. Codeberg's migration guide covers issues, labels, releases, milestones and other supported metadata. Choosing the generic Git source transfers repository content without that extra metadata. Revoke the migration token once the transfer is accepted.

For a public dependency maintained by volunteers, a new contributor's first experience matters as much as the import. Publish the new contribution instructions, explain where reviews happen and make the canonical project location unmistakable. Moving the repository without moving the community's habits leaves maintainers monitoring two places.

Codeberg runs most services on its own hardware in Berlin, but its FAQ describes other locations and providers for some tasks. Treat that as useful infrastructure information, not a contractual promise that every data copy remains in Germany. For a proprietary business with strict location requirements, evaluate your own hosted deployment instead of trying to turn a donation into an exception.

SourceHut: choose the email workflow and the AI policy deliberately

SourceHut is an open-source development suite centered on Git, mailing lists, ticket tracking and builds. It fits maintainers who want patches reviewed through email, with supporting web tools, rather than reproducing GitHub's pull-request experience. A project already discussing contributions on a mailing list has a clear reason to evaluate it. Its walls are the workflow change, its public-alpha status and a hosted AI policy that excludes many current coding practices.

Best for: Projects that actively prefer email-based patch review.
Standout: Development collaboration built around mailing-list workflows.
Pricing: Hosting subscriptions start at $4/month before applicable taxes; all paid tiers have the same service access, on the SourceHut pricing page.
Free trial: Many services currently have optional payment during alpha, but builds require payment; contributors need not pay merely to participate.

CI/CD, issues and reviews: The suite includes builds.sr.ht for CI, todo.sr.ht for tickets and mailing-list patch review with web tooling. A patch is a proposed code change sent for review; maintainers discuss it and apply an accepted revision. Delivery automation must still be configured for your project. Do not interpret the subscription as a prebuilt release system.

AI coding assistant: SourceHut explicitly advertises no AI features. Its AI policy change went further for new projects from 10 September 2026: original content written or assisted by generative AI, and software facilitating generative AI, is prohibited on the hosted service, subject to its stated interpretation and exceptions. The explanation allows private analysis or review when you then author the original material yourself. A team routinely submitting assistant-written code should not choose this hosted service.

Import from GitHub: The Git service manual describes bringing externally hosted source over by cloning it and adding it to git.sr.ht. That supplies a Git transfer path. It is not evidence that GitHub pull-request discussions will become equivalent mailing-list threads, or that issues will map automatically into the ticket tracker. Inventory those separately and decide what must remain readable as an archive.

Before switching a company project, have a newcomer follow the proposed contribution instructions. Can they submit a patch, respond to feedback and find the accepted revision? A workflow that feels clean to an experienced maintainer may still impose onboarding work on everyone else. That can be worthwhile, but it needs to be a conscious operating choice.

The software can also be self-hosted. Keep that separate from eligibility for SourceHut's hosted service: running the software on infrastructure you administer is a different deployment and responsibility model.

AWS CodeCommit: available again, but a narrower replacement

AWS CodeCommit is a managed private Git repository service for organizations that want repository access inside their AWS operating model. It belongs on the shortlist when AWS identity permissions and network boundaries are central requirements. AWS's reopening announcement explicitly says it accepts new customers again. Some older AWS page banners still say otherwise; the reopening announcement and current documentation history supersede that closure notice.

Best for: AWS-centered organizations with a specific repository-boundary requirement.
Standout: Repository access integrated with AWS identity and infrastructure services.
Pricing: A free allowance is available; paid usage is $1/active user/month plus applicable overages, per the CodeCommit pricing FAQ.
Free trial: The maker publishes an ongoing allowance, not a timed full-platform trial.

CI/CD, issues and reviews: CodeCommit supports pull requests and review collaboration. Build and delivery automation comes through separate services such as AWS CodeBuild and AWS CodePipeline. Plan an issue tracker separately. This is a composition of services, so compare the resulting workflow and bills rather than treating repository hosting as an all-in-one development subscription.

AI coding assistant: AWS offers Amazon Q Developer for coding assistance. It is a separate offering, not evidence that buying CodeCommit automatically adds a native assistant to every repository or review. Keep the repository decision and the assistant entitlement distinct.

Import from GitHub: AWS documents a Git repository migration: obtain the existing Git repository, create the CodeCommit destination and transfer the code. Do not mistake that for importing GitHub Issues, pull-request conversations or Actions workflows. Those are separate systems to replace or preserve.

The right pilot proves access and delivery within the intended AWS setup. Can the expected developer identity fetch the repository? Can the build identity access only the necessary source? Can the release proceed with the intended permissions? Those questions explain why a team might choose CodeCommit even when another forge offers a more unified interface.

Verdict: Include it when AWS integration is the reason for moving. For a founder simply seeking a familiar GitHub replacement, evaluate GitLab or Gitea first.

Self-hosted software: Gitea, GitLab and the operating work

Self-hosting is the strongest fit when you need to choose the infrastructure, administer the application and control its recovery. It also gives you an outage to own. The deciding question is whether someone can restore the service when a disk, database or upgrade fails, not whether installation looks easy.

Gitea: the first self-hosted shortlist entry

Gitea is an open-source forge for repositories, issues, pull requests and automation. It is the best starting point for a small engineering organization that wants to operate its own code platform without adopting a broader suite by default. An internal tooling team can keep reviews and tasks beside its repositories while choosing where the service runs. Its wall is operational ownership: the free license does not supply backups, monitoring, runner isolation or a recovery operator.

Best for: Teams that want a self-managed forge and can own its operation.
Standout: Repositories, issues, pull requests and Actions in the open-source product.
Pricing: Open Source is $0 under the MIT license; hosting and administration are extra, per the Gitea pricing page.
Free trial: Open-source use is ongoing; the vendor separately offers commercial trials.

CI/CD, issues and reviews: Gitea includes issues and pull requests, with Gitea Actions for CI/CD. Its Actions documentation says it is mostly compatible with GitHub Actions and uses a separate runner program. “Mostly” matters. A familiar workflow file is a migration advantage, not proof that every action, permission assumption and integration will behave identically.

AI coding assistant: No first-party coding assistant is advertised on the maker's product and pricing pages checked. That is a narrower statement than an AI ban. If you use a separate editor assistant or review bot, assess its repository access, data handling and integration support independently.

Import from GitHub: The Gitea migration documentation describes its built-in GitHub migration form, including items such as issues and pull requests when the required account details are supplied. Run the import against a representative project, then inspect discussions and identities. Treat Actions configuration and secrets as another acceptance test.

For example, a private internal application might have a straightforward test workflow but a release job that assumes a particular hosted identity provider. Reusing the test job does not validate the release job. Your pilot should reach the deployment environment and demonstrate recovery before you announce the migration as complete.

Gitea also sells managed Cloud and Enterprise options, so the product is not exclusively self-hosted. This recommendation concerns the Open Source deployment you administer. Enterprise controls such as SAML single sign-on, which connects login to your organization's identity system, should be checked against the edition instead of assumed to exist in the free installation.

Gitea vs GitLab: choose the operating scope you need

Choose Gitea when a focused forge covers your work and you can operate it. Choose GitLab Self-Managed when the broader GitLab workflow is the reason for moving and you accept the administration it requires. Do not choose either solely because its software can be downloaded without a hosting invoice. The operating cost includes the person who investigates a failed backup and the time developers lose during an outage.

Codeberg is the managed service; Forgejo is the software it runs. Self-hosting Forgejo is a separate option from getting a Codeberg account. SourceHut's software can also be installed on your infrastructure. Those distinctions prevent a common shortlist error: confusing an open-source hosted service with a promise that the provider will run your private installation.

Bitbucket's self-managed story needs a separate eligibility check. Atlassian's Hybrid License page says that offer is for existing Bitbucket or Bamboo Server/Data Center customers. It is not a greenfield self-hosting route for a company starting from GitHub. Equally, the general Data Center retirement announcement should not be read as a blanket statement that Bitbucket's self-managed product is disappearing.

Best GitHub alternatives for your team

If cost is the main problem, compare the complete working setup before moving. Start with the hosted free allowances for a small company. Include build capacity, issue tracking, required identity controls and assistant access. Switch only when the saving or control benefit survives the work of reproducing your release process.

If infrastructure control is mandatory, start with Gitea and GitLab Self-Managed. The choice flips toward GitLab when the wider platform removes enough separate tooling to justify its operating scope. It flips toward Gitea when repositories, issues, reviews and a suitable CI arrangement are the job.

If ecosystem integration is the priority, follow where work is already coordinated. Bitbucket fits Jira-based planning. Azure DevOps fits a Boards and Pipelines workflow. CodeCommit fits a specific AWS repository requirement. Adopting another ecosystem merely to avoid one bill can create more administrative work than it removes.

If the project is public and community-led, make contributor fit the deciding factor. Codeberg is the clearer choice for a free-software project wanting a familiar forge. SourceHut is for maintainers who actively choose its patch-review workflow and can comply with its AI rules. Neither should be selected only because a headline calls it free.

GitHub Actions alternatives: test the release job first

GitLab CI/CD, Bitbucket Pipelines, Azure Pipelines, Gitea Actions, Codeberg's CI options and SourceHut builds cover different operating models. CodeCommit connects to a separate AWS delivery stack. That makes the migration unit the working pipeline, not its configuration file.

Inventory the steps that depend on the current host: checkout, caches, package access, deployment credentials, approval gates and notifications. Test the most constrained release job early. If it cannot run safely in the destination, a successful repository import has not removed the blocker. Gitea's compatibility may reduce rewriting, but it should not remove this test.

GitHub Copilot alternatives: separate the assistant from the host

Changing the Git remote does not decide which assistant a developer may use or where that assistant sends context. GitLab offers Duo; Atlassian offers the transitioning Rovo developer tooling; Microsoft's Azure Repos review integration uses GitHub Copilot; AWS offers Amazon Q Developer separately. Gitea's inspected pages do not advertise a native equivalent, while Codeberg and SourceHut make policy choices that require attention beyond assistant selection.

Write the requirement precisely: no training on submitted code, no external processing, no generated contributions, or no dependency on a particular supplier. Those are different policies. A platform can satisfy one and fail another. Use our GitHub Copilot pricing guide to assess the assistant bill separately from repository hosting.

Data residency: follow the code beyond its repository

A repository's location is only part of the data-location decision. A build runner can receive source code, a log can contain sensitive output, and an AI service can receive snippets independently of where Git objects are stored. For an engineering lead responding to a customer requirement, the useful deliverable is a map of those transfers and the contracts covering them.

Microsoft's Azure DevOps data-location documentation describes selectable geographies, including Europe and Canada, and limited exceptions to customer-data location. Codeberg describes its infrastructure locations but is not a substitute for a private commercial hosting contract. Self-hosting gives you choices about deployment; it does not automatically constrain an external assistant or build service.

Ask where repositories, databases, backups and logs reside; where support can access them; and which subprocessors receive code. Then run the same check on CI and AI. If the requirement is “no code leaves this environment,” enforce it at the relevant connections instead of treating a regional hosting selection as the whole answer.

What you give up when you leave GitHub

You give up some of GitHub's network convenience: potential contributors already have accounts, know the review interface and can discover a project through familiar profiles and repositories. You also lose the assumption that an Actions marketplace component will work unchanged, with the same permissions and integrations, on the destination. Open-source discovery becomes more of your own job, even when the alternative has a capable community. These costs matter more to a public developer tool recruiting contributors than to a private internal application. A public mirror may preserve visibility, but it needs unmistakable contribution instructions and a clear canonical home; otherwise you create duplicate issues and reviews for maintainers to watch.

How these were picked

The selection favors complete decision evidence over feature-count rankings. Each option was checked for current availability, hosting model, CI/CD, issues and reviews, the maker's stated AI offering, GitHub import path and published entry price. GitLab, Bitbucket, Azure DevOps and Gitea displayed signup, purchase, trial or download routes; Codeberg and SourceHut displayed registration routes; AWS explicitly confirmed reopened signup.

The comparison was verified on 5 November 2026 against primary product, pricing and documentation pages. No performance measurements, support-response tests or trial migrations were performed. The recommendations are judgments about workflow fit based on that evidence. A favorable description does not override a project's eligibility rules or your need to test its actual release process.

The ones to avoid

Avoid Codeberg for a private proprietary product company. Its mission is a reason to choose it for free software and a reason to exclude it for ordinary private commercial hosting. Optional donations do not purchase a different acceptable-use policy.

Avoid hosted SourceHut if your normal contribution process depends on generated code or your product facilitates generative AI. Its current policy is a substantive compatibility issue, not an optional assistant setting. Also avoid it if your contributors need a GitHub-like review experience and nobody has budgeted for workflow training.

Avoid treating Bitbucket Hybrid as a new self-hosted purchase path. The eligibility page is explicit about existing customers. Evaluate the Cloud offer in this list, or choose software you can deploy yourself.

Avoid CodeCommit as a default all-in-one replacement. It can be the right AWS repository service, but the surrounding issue and delivery workflow still has to be designed. Its old signup closure is no longer a valid reason to reject it.

Avoid any migration whose only proof is a successful clone. If reviewers cannot find the decisions behind the code, or the destination cannot release it, the platform move is unfinished.

Your migration acceptance checklist

Accept a migration in separate layers so that a clean repository transfer cannot hide a broken workflow. The checklist below is an evaluation framework, not a claim that every importer transfers every layer.

1. 1

   Prove the repository is complete

   Compare the expected branches and tags, inspect representative commits and confirm large files can be retrieved. Keep an independent backup and retain the source until the migration is accepted.

2. 2

   Prove the decisions remain readable

   Inspect an issue, a closed review, an attachment and a release note. Decide which missing history will be imported, archived or linked. Give someone responsibility for resolving broken references.

3. 3

   Prove the destination can ship

   Configure credentials, artifact access and deployment approvals deliberately. Run the release process against a safe target, then rehearse recovery. Revoke temporary import credentials after acceptance.

4. 4

   Prove access and cutover ownership

   Check a developer, reviewer, build identity and departing user's access. Schedule the final synchronization, announce where new contributions belong and name the person authorized to roll back the move.

Your next working session should produce a pilot result, not a longer shortlist: choose the destination that meets the mandatory constraint, migrate a representative repository and have its release owner accept the workflow. Expand only after that evidence exists.

Frequently asked questions

What is the best alternative for GitHub?

GitLab is the strongest broad replacement when you want repositories, issues, reviews and CI/CD together. Gitea is the first self-hosted option to evaluate when a focused forge covers the work and you can operate it. Jira dependence, community policy or an AWS boundary can change that recommendation.

Which is better, TFS or Git?

They are different kinds of tool. Team Foundation Server, the predecessor to Azure DevOps Server, is a development platform. Git is a distributed version-control system. If you mean Git versus Team Foundation Version Control, Microsoft's TFVC overview explains the centralized alternative. You do not need to abandon Git to change repository hosts.

Does NASA use Git?

Yes. NASA describes using GitHub to publish open-source software in its open-source development overview. That establishes real use of Git repositories, not a universal rule for every NASA system.

Is GitHub still open source?

GitHub's hosted platform is proprietary. Git, the underlying version-control tool, is open source, and GitHub hosts many open-source projects. These are different things: choosing an open-source project does not mean choosing an open-source hosting platform.

Why are people boycotting GitHub?

Reasons vary, including objections to proprietary hosting, supplier dependence and AI use. Codeberg and SourceHut publish explicit positions on AI and software governance, discussed above. For your organization, translate the concern into a requirement you can verify rather than assuming every alternative shares the same policies.

What is GitHub for idiots?

GitHub is a shared workspace for code. It stores the history of changes, lets people propose and review updates, and supports issue tracking and automation. The alternatives differ in how much of that workspace they provide and who operates it.

Is GitHub risky?

The useful question is which risk you need to control: account access, exposed credentials, repository permissions, third-party automation or data transfers. Moving providers does not remove those responsibilities. Self-hosting also makes patching, backups and recovery your responsibility.

Is GitHub 100% owned by Microsoft?

Yes. Microsoft completed its acquisition of GitHub in 2018, as recorded in its acquisition announcement. Moving to Azure DevOps changes the platform while keeping Microsoft as the supplier.

Does the US government use GitHub?

Yes. NASA's published use is one documented federal example. That does not establish that GitHub, or any alternative, is approved for every government project or class of information.

Before changing the development stack, get the AI Business Workflow Audit Checklist to map what the new workflow must preserve.