Syncing with other Git providers offers several conveniences, including:
Collaboration: Syncing with other Git providers allows you to collaborate with individuals or teams who are using different Git platforms. It enables cross-platform collaboration, allowing you to work together seamlessly regardless of the provider each party uses.
Flexibility: Syncing with other Git providers gives you the freedom to choose the provider that best suits your needs. It allows you to leverage the unique features, integrations, or pricing models offered by different providers, providing flexibility and customization options.
Migration: If you decide to switch Git providers, syncing can help facilitate a smooth transition. It allows you to migrate your repositories, commit history, branches, and other data from one provider to another, reducing the effort and time required for the migration process.
Backup and Redundancy: Syncing with multiple Git providers can serve as a backup and redundancy measure. By replicating your repositories across different providers, you ensure that your codebase remains safe even if one provider experiences technical issues, data loss, or downtime.
Access to Features: Different Git providers may offer unique features, extensions, or tools that can enhance your development workflow. Syncing with other providers enables you to take advantage of these additional features, expanding your toolkit and improving your overall development experience.
Integration Ecosystem: Syncing with other Git providers allows you to tap into a broader integration ecosystem. Each provider typically has its own set of integrations with project management tools, continuous integration/delivery systems, code review platforms, and more. By syncing with different providers, you can leverage a wider range of integrations to enhance your development workflow.
When creating your repository, you could choose where your repository located. Two-way synchronization is available on the Enterprise plan.
Choosing Any Git Platform
On the next step, enter the address of your remote repository and how to authenticate with it.
The Git repository is hosted on any of your specified git server which can be a popular platform such as Github, Gitlab, Bitbucket, Azure, AWS, Gitee, or even a self-hosted Git server with public access . APIGit employs a smart two-way synchronization with your remote repository, ensuring that all commits made on APIGit are automatically synchronized with your specified servers, and vice versa. Your designated Git repository acts as the authoritative source of truth, so pull requests and branch protection rules are managed through your Git provider. See Where to Host the Git Repository.

Edits in APIGit now stay as drafts across files. Review them together, choose what goes in, and commit them as one commit, with conflicts resolved line by line.
Commit events in the timeline, a file tree for the diff, update branch, a merge style dropdown and checks that recover from temporary failures.
Clone and push over SSH at git.apigit.com, give a server access to one repository with a deploy key, and use personal access tokens limited to repositories.
Create a free workspace, add an OpenAPI file and publish your first API document and mock server in minutes.