We offer the most comprehensive backup on the market. Cloudback lets you store all the information you need to restore the entire repository in the event of a disaster. Back up the GitHub repository code, issues, labels, comments, milestones, etc.
You can set up a flexible schedule for each repository. Cloudback then automatically backs up the repositories according to the schedule. You can also manually trigger a backup at any time.
Reduce storage costs while using your own storage. Learn more
Learn more about Cloudback features in our documentation
Simplicity and user-friendliness, from the UX to the backup archive.
1) Pricing policy - per repository, not per seats. 2) User-friendly backup archives. End user can take an archive and restore even manually. 3) Easy to use, the simplified UI and UX, without heavy enterprise-focused routines (but still all features are in place).
It is Azure-hosted .NET core application, built with security in mind.
If you were using GitHub Desktop, then the file should be in the recycle bin. See this SO answer for more details. You can also try using git restore command. Finally, you can use backup tools like Cloudback to protect your repositories in the future. This will not help you to restore the local changes from your computer, but still can be useful in case of any wrong changes done to your repository. Source: about 1 year ago
Do you know an article comparing Cloudback.it to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Cloudback.it. You can review and discuss the product here. The primary details have been verified within the last quarter. So they could be considered up to date. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.