Cloudback Reviews & Product Details

The clean, single dashboard that shows every repository’s last backup state, schedule and storage location at a glance. Being able to mix daily 02:00 UTC jobs with higher-frequency (every 6-hour) runs for critical services, and to point different repos at AWS S3, Azure Blob or Google Cloud without leaving the UI, is extremely practical. The restore wizard and the fact that backups include full history plus metadata (issues, PRs, LFS) give us confidence we can recover quickly. Review collected by and hosted on G2.com.

When a backup fails because a storage quota is exceeded (we have seen this on a Google Cloud destination), the alert is clear but the remediation steps could be a little more guided inside the UI. Also, bulk editing of schedules across many repositories is functional but not as fast as we would like for large estates. Review collected by and hosted on G2.com.

Reliability and simplicity. Once connected, Cloudback quietly handles daily backups of repositories, all associated metadata, and LFS objects, then lets us restore or download archives whenever needed. Being able to point storage at our preferred providers (S3, Azure, GCS, etc.) while keeping encryption and immutability options is a big plus. The dashboard and notification channels keep the team informed without adding overhead. Review collected by and hosted on G2.com.

Documentation is solid, yet a few more real-world restore walkthroughs or example retention strategies for mixed GitHub + Azure DevOps environments would accelerate onboarding for new team members. Feature parity across platforms continues to improve; keeping that momentum will make the product even stronger. Review collected by and hosted on G2.com.

Backups run without someone remembering to clone repos or maintain a fragile script. That sounds basic until you have lived with “we’ll set that up properly later.” Having Git history and related project data land automatically in storage we control is the part I value most. Review collected by and hosted on G2.com.

You still need some light, ongoing hygiene: be clear on who’s covered, what retention rules apply, and whether restores have actually been tested. The product can automate the copying, but the day-to-day operating habits still sit with the team. Review collected by and hosted on G2.com.

When leadership asks how we’d recover Git history after a bad day, I want the answer to be a process—not a shrug. With scheduled backups into our own storage, we’re not relying on a single host or a scattered pile of laptop clones, and we can actually point to a clear path for getting history back when something goes wrong. Review collected by and hosted on G2.com.

Restore confidence still comes from practice. Green job logs help, but until you’ve restored a repo once, the plan stays theoretical. That’s on the team as much as the tool. Review collected by and hosted on G2.com.

The most impressive structural feature is their decentralized storage flexibility and the absolute separation of data control. Instead of locking our proprietary source code inside a secondary multi-tenant black box, Cloudback allows our security team to map backup destinations directly to our own corporate storage environments via secure AWS IAM roles and private S3 buckets.Furthermore, it captures the entire development ecosystem rather than just the raw Git history. It systematically packages and archives deep repository metadata—including developer wiki pages, issues, pull request threads, deployment releases, and project milestone logs—and preserves our Git Large File Storage (LFS) assets without any data corruption. This complete backup capability provides our compliance team with an ironclad, auditable archive that satisfies our annual SOC2 and ISO 27001 data-retention reviews perfectly. Review collected by and hosted on G2.com.

The backup automation engine operates with exceptional reliability, but their administrative workspace notification filtering framework needs better granular refinement for large-scale operations. Currently, if a minor, low-priority test repository or a sandbox environment encounters a transient API rate-limit threshold error from the host platform, Cloudback triggers an immediate high-urgency system alert to our primary Slack and email integrations.We would highly appreciate a dashboard feature that allows us to set up conditional routing rules, enabling us to bundle low-priority warnings into a single daily digest while reserving instantaneous, real-time alerts strictly for mission-critical production repository failures. This would significantly reduce notification fatigue for our on-call infrastructure teams. Review collected by and hosted on G2.com.

The “Bring Your Own Storage” (BYOS) architecture has been an absolute game-changer for meeting our infrastructure compliance requirements. We can seamlessly route our encrypted backup data directly into our own private Amazon S3 buckets, while still managing our own encryption keys through their RSA Lockbox feature. I also find the pricing structure incredibly fair, since they charge strictly per repository rather than by administrative seat licenses. That approach lets us give dashboard visibility to our entire auditing and management team without taking on massive, unnecessary subscription costs. Review collected by and hosted on G2.com.

The platform is exceptionally reliable overall, but the automated email notification system can feel a bit noisy when we’re managing bulk repository configurations. For example, if a single minor repository sync hits a temporary API rate-limit hiccup, it immediately triggers a warning notification. We’d love to see more granular notification grouping options in the dashboard so we can consolidate these alerts into a single daily summary email, instead of receiving separate, real-time messages for each small issue. Review collected by and hosted on G2.com.

What I like most is the simplicity of configuration combined with the dependability of automation, because setting up policies is straightforward, the interface is clean and intuitive, and monitoring backup jobs is easy enough that even non-technical team members can understand what’s happening, which makes the entire process feel less like a chore and more like a seamless part of our infrastructure. Review collected by and hosted on G2.com.

Overall, my experience has been very positive, but if I had to mention one area for improvement it would be the reporting features, because having more exportable and customizable reports would make it easier to share backup status with stakeholders and provide additional visibility into long-term trends. Review collected by and hosted on G2.com.

When leadership asks “what happens if the Git host is down or the account is locked,” the answer is no longer vague. Backups run on a schedule into storage we control, and the process is documented enough that recovery is a real plan, not a hope that someone still has a laptop clone. Review collected by and hosted on G2.com.

You still have to own retention hygiene. Old or archived repos can keep policies longer than they should if nobody reviews the list once in a while. Review collected by and hosted on G2.com.

When something goes wrong with a repo, I want a straight path back—not a scavenger hunt across old laptops and half-finished mirrors. Cloudback keeps scheduled copies in our own storage so recovery is a defined step, not a guess. Review collected by and hosted on G2.com.

Policy cleanup for old or archived repos needs a bit of attention so you’re not paying to protect things nobody uses. A periodic review keeps it tidy. Review collected by and hosted on G2.com.

It does the unglamorous job well: backups run, they land in storage we control, and I’m not maintaining a pile of brittle scripts. I mostly forget it’s there until I need the confidence that something important is actually protected. Review collected by and hosted on G2.com.

It’s easy to set and forget—and that’s also the risk. If nobody ever tests a restore, you only find out the process is rusty when you’re already under pressure. Review collected by and hosted on G2.com.