Every Belov Cloud account can have its own private Git hosting at git.belov.cloud — repositories, branches, pull requests and issues, on our servers, with no GitHub account needed. You sign in with your Belov Cloud account, your team gets the access it already has here, pushes deploy your apps, and every repository is backed up automatically.
1
Turn it on
Open Git in the panel's sidebar and choose Turn on Belov Git (owners and admins). Pick your organization name — it becomes part of every repository address, like git@git.belov.cloud:acme/website.git, and can't be changed later.
2
Sign in
Click Open Belov Git, then Sign in with Belov Cloud. There's no new password: you're signed in as yourself, and your email address must be confirmed. Teammates sign in the same way with their own accounts.
3
Add your SSH key
In Belov Git open Settings → SSH / GPG keys → Add key and paste your public key (the line in ~/.ssh/id_ed25519.pub). No key yet? Create one with the first command below. Add one key per computer you push from.
4
Create or import a repository
On the panel's Git page, create an empty repository or import one from GitHub, GitLab or Bitbucket — or use + New repository inside Belov Git. Repositories are private to your team.
5
Push your code
Point your project at Belov Git and push. From then on it's ordinary Git — clone, branch, pull requests, tags.
On your computer
ssh-keygen -t ed25519 -C "you@example.com" # only if you don't have a key yet
cat ~/.ssh/id_ed25519.pub # copy this into Belov Git → Settings → SSH keys
cd my-project
git remote add origin git@git.belov.cloud:your-org/my-project.git
git push -u origin main
git clone git@git.belov.cloud:your-org/my-project.git # on another computer
HTTPS instead of SSH
Prefer HTTPS (or a tool that doesn't speak SSH)? In Belov Git open Settings → Applications → Generate new token, give it Read and write access to repositories, and use https://git.belov.cloud/your-org/my-project.git. When Git asks, the username is your Belov Git username (top-right menu) and the password is the token.
Who can see what
Access follows your team in Belov Cloud automatically. Owners and admins manage everything; developers can push to every repository; a developer limited to certain sites only gets the repositories those apps deploy from. Remove someone from the team and their Git access ends at the same moment.
Belov Git is included with every plan — there's no separate Git pricing and no limit on private repositories. Backups follow your hosting plan: weekly on Front, daily on Pro and Full-stack, and daily with 30 days of history on Scale. See Git backups for the details and how to restore.
Deploy an app straight from a Belov Git repository — every push ships.