G2

Wendy W.

GTM Strategy and Operations Advisor

Farming

Small-Business (50 or fewer emp.)

8/11/2026

"Exceptional Decoupled Storage and Auditable Snapshots for Compliance-Ready Archiving"

5/5

What do you like best about Cloudback?

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.

What do you dislike about Cloudback?

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.

What problems is Cloudback solving and how is that benefiting you?

Our engineering division was tasked with meeting a strict regulatory data governance mandate that required us to maintain cold, air-gapped backups of our intellectual property outside of our active GitHub and GitLab organizational accounts. Relying strictly on a single cloud version control host left us vulnerable to single-point system outages, malicious developer credential compromises, and accidental workspace deletions that could halt our entire product deployment pipeline.Cloudback completely solved this business continuity risk for our organization. By automating deeply nested, schedule-driven background snapshots across more than 150 critical active repositories, it ensures our full code tree and multi-branch commit histories are permanently backed up. This automated infrastructure frees our DevOps and site reliability engineers from wasting hours writing and debugging custom shell scripts or manual cron jobs, allowing our engineering sprints to stay 100% focused on shipping consumer-facing features. Review collected by and hosted on G2.com.