Keep engineering running through any incident

Cloudback is an automated backup and restore service for GitHub, Azure DevOps, GitLab, and Linear. It backs up repositories, project metadata, and platform-specific data like issues, pull requests, and documents as encrypted ZIP archives. Backups run on a configurable schedule, and archives can be stored in your own cloud storage or in Cloudback's managed regional storage.

A unit is how Cloudback measures backup capacity. Each enabled backup consumes units from your subscription pool based on the platform: one unit per GitHub repository, one unit per Azure DevOps repository, and one unit per GitLab project. Linear is priced per workspace member using progressive tiers: each of the first 5 members costs 2 units, each of the next 20 members (6-25) costs 4 units, and each member beyond 25 costs 6 units. Tiers stack, so a 10-member workspace pays 5×2 + 5×4 = 30 units. Your subscription's units are shared across all connected accounts and platforms, so you can mix and match as needed.

Cloudback offers two storage options. You can use customer-managed storage (BYOS) where backups go directly to your own AWS S3, Azure Blob, Google Cloud, OneDrive, Wasabi, or other supported provider. Alternatively, Cloudback provides managed regional storage in the US, EU, UK, Sydney, and Singapore for teams that prefer a quick setup without configuring their own bucket.

Every backup archive is encrypted with AES-256 and protected with a unique password managed by Cloudback. For additional protection, backups stored in Amazon S3 can use Object Lock for immutable, write-once-read-many (WORM) retention. This prevents anyone, including account admins, from deleting or modifying backups during the retention period.

Yes. Cloudback supports flexible scheduling. You can set backups to run daily, weekly, monthly, or on a custom schedule that fits your workflow. Retention policies of 30, 90, 180, or 360 days control how long backup archives are kept. Both schedule and retention can be configured per backup definition in the dashboard or via Terraform.

Cloudback sends notifications when a backup fails. By default, you'll get an email alert. You can also set up real-time notifications through Slack, Microsoft Teams, or Discord webhooks. The dashboard shows backup status for every definition, and the audit log records all backup events with details for troubleshooting.

Yes. Cloudback holds SOC 2 Type II certification since October 2024. The platform includes audit logging with 50+ tracked event types, 180-day log retention, and Vanta integration for automated user access reviews. Backups are AES-256 encrypted, and customer-managed storage options support data residency requirements for GDPR and other regulations.

Yes. Cloudback has a Terraform provider (cloudback/cloudback on the Terraform Registry) that lets you manage backup definitions, schedules, storage, and retention policies as infrastructure-as-code. There's also a REST Operations API for programmatic backup management. Both options allow teams to version-control their backup configuration alongside other infrastructure.