Bring connections together
Add supported GitHub, GitLab, and Gitea servers to a single signed-in workspace.
Repository management, brought into focus
Your Git servers. One focused workspace.
Connect GitHub, GitLab, and Gitea, then search across repositories, filter by server or organization, and take the next repository action without tab-hopping.
GitHubGitLabGitea
Repository view
All connected servers
Focused
Servers
GitHub
12 repositories
GitLab
8 repositories
Gitea
4 repositories
Search repositories
New repository
branch-manager
Cyberstream Studios
gateway-service
Platform
release-tools
Infrastructure
Filter by server or organization
Designed for web, iOS, and Android.
Keep the same connected workspace close at hand across your devices.
Account-scoped connections
One lens for your repositories
Bring every connection into the same clear view.
Branch Manager keeps the useful parts of each connected server close together, while the provider remains the source of truth for your repositories.
Find a repository faster
Search one repository list and narrow it by the server or organization that matters now.
Create in the right place
Start a repository for your personal account or an available organization, based on your provider permissions.
Review before you act
Open repository details, recent commits, clone URLs, and supported settings without losing your place.
A deliberate workflow
Connect. Focus. Move work forward.
The workflow is intentionally simple: set up the connections you trust, choose the view you need, and take a provider-backed repository action.
- 01
Connect a server
Give your GitHub, GitLab, or Gitea connection a label and choose a credential with only the scope you need.
- 02
Choose a view
Browse every available repository or filter to one server or organization.
- 03
Manage the next action
Create a repository, inspect details, copy a clone URL, or open the provider when it is time to go deeper.
A clear security boundary
Your connection credentials are handled as credentials.
Personal access tokens are encrypted before persistence, stay scoped to your account, and are used only when Branch Manager needs to communicate with the Git host you selected.
Read security practices- Connections and API requests are scoped to the signed-in account.
- Personal access tokens are encrypted with authenticated AES-256-GCM before database persistence.
- The application does not return stored personal access tokens through its public API.
- Production Git connections require HTTPS and reject private or reserved network targets by default.
Ready when you are
Bring your repository landscape into focus.
Create an account, add the Git server you trust, and start from the one repository view that matters.