Cloudback

Backup setup usually starts with a form full of decisions nobody wants to make on day one. Cloudback picks reasonable ones for you: backups run daily, and a 30-day retention policy keeps them. That works for plenty of teams as-is. If it doesn't work for yours, you can change any part of it. Weekly. Monthly. Or a custom schedule down to specific hours, days, and months, so backups run when your systems are quiet. Set the time zone while you're there. A 2 AM schedule should mean 2 AM where your team actually works, not wherever the server happens to sit. And if you're looking after more than a handful of repositories, you don't have to click through them one by one. You can apply the same schedule across many repositories at once. #DevOps #GitHub #DisasterRecovery #Backup

Rolling your own repository backup script? There's one behavior worth building in before it goes to production: deduplication. A quiet repository still gets backed up every night. If the script uploads a full copy each time, you're paying storage for identical data over and over. Cloudback handles that case differently. Each new backup is compared against the previous one. If nothing changed, Cloudback stores a link to the existing backup instead of uploading a duplicate. The saving isn't buried in one aggregate number either. The space saved shows up per repository, so you can see which repos are producing new data and which ones have been sitting still. If you're scripting this yourself, the compare step is the part people skip. Uploading is easy to write. Deciding not to upload is what keeps the storage bill flat. #DevOps #GitHub #GitLab #Backup #PlatformEngineering

After Cloudback is installed, backups start on their own: a daily schedule, Cloudback Managed Storage, and 30-day retention. The first automated backup runs within 24 hours of setup. To run one on demand instead of waiting, use the Trigger button in the dashboard: 1. Go to app.cloudback.it and find the repository to back up. 2. Check the checkbox in the first column next to it. 3. Click the Trigger button in the top toolbar. The backup is queued immediately and starts as soon as a worker is available. Manual triggers are prioritized over scheduled backups. To watch progress, check the Backup and Last Run columns on the dashboard. A couple of details worth knowing: there's a 1-minute cooldown between manual triggers per repository, and if a backup is already running or queued for that repository, a new trigger is rejected. To back up a single repository without returning to the list, open its details page and click Backup now. So there are two paths to the same backup archive: the daily automated schedule that runs by default, and the Trigger button when a backup is needed right now - before a big change, a repository transfer, or a migration.

Most teams don't run one Git platform. Code sits in GitHub. A legacy service is still in Azure DevOps. A client project lives in GitLab. Planning happens in Linear. Each one has its own admin console, its own export quirks, and usually its own person who remembers how the backup script works. Cloudback runs automated backups across all four from a single dashboard: GitHub repositories, Azure DevOps repositories, GitLab projects, and Linear workspaces. Same schedule. Same retention policy. One place to confirm last night's backup actually ran. If answering "are the backups healthy?" takes logging into four different tools, that's worth fixing before the next audit - or the next incident. #DevOps #Backup #GitHub #GitLab #Linear

New: a free, source-available workflow that turns Cloudback MCP into an agentic backup reviewer. The team at Heym built "Cloudback MCP Backup Coverage Review" - an AI agent that checks your backup coverage through the Cloudback MCP server, flags backup definitions with disabled or failed backups, and posts a review to Slack before anything changes. The part worth calling out: it's human-in-the-loop by design. The agent runs reads, lists, and views on its own. But every write - update, delete, schedule, storage, account settings - stops and waits for a person to approve. An agent recommends; a human signs off. It's a real, working example of agentic automation built on top of Cloudback MCP, not a mockup. It reviews coverage across GitHub, GitLab, Azure DevOps, and Linear, launches the MCP server over Docker, and imports into Heym with one paste. Try the template: https://lnkd.in/eXdPmYXW #Cloudback #MCP #DevOps #Backups

Cloudback now backs up and restores Linear workspace, with encryption keys only your team holds. Linear joins GitHub, GitLab, and Azure DevOps in Cloudback - one place to back up the tools your team runs on. Trusted by 1.7k+ customers with 4M+ backups created. With RSA Lockbox enabled, only your team holds the private key - Cloudback never needs it to back up your workspace, and no one else can open an archive. Each archive is AES-256 encrypted with a unique per-archive password. Keep backups in Cloudback Managed Storage, or bring your own bucket: Amazon S3, Azure Blob, Google Cloud Storage, or Wasabi. Cloudback backs up 23 data categories: issues, projects, cycles, documents, comments, custom views, workflow states, templates, labels, attachments, and embedded files. Restore rebuilds the workspace into a new Linear environment in dependency order, so references between items stay intact. SOC 2 Type II certified. Snapshot-based backup and full restore. Connect a Linear workspace and run your first encrypted backup in under 5 minutes: https://lnkd.in/dN_jPCr7

Cloudback is live on Product Hunt today 🎉 Cloudback now backs up and restores Linear workspaces - alongside GitHub, GitLab, and Microsoft Azure DevOps. Teams keep more in Linear than they realize: issues, projects, cycles, documents, the whole planning history. Cloudback captures 23 data categories per workspace on an automatic schedule (plus one-click manual backups anytime), and restores the full workspace in dependency order when you need it. Snapshot-based backup, AES-256 encryption with optional customer-managed keys, SOC 2 Type II. If your team runs on Linear, we'd love your take - take a look and tell us what you think 👇 https://lnkd.in/dmdTaJQp

Your team's roadmap, issues, cycles, and documents all live in Linear workspace. Now you can keep an independent, encrypted backup of every bit of it. Cloudback now backs up and restores Linear workspaces 🚀 🤝 🙂 23 data categories are covered: issues, comments, projects, cycles, documents, initiatives, templates, custom views, workflow states, labels, attachments, and embedded files. A few things worth knowing: - Backups run on a daily schedule or on-demand, whenever you need them - Retention policy options: 30, 90, 180, or 360 days - Each backup archive is AES-256 encrypted with a unique per-archive password - Optional RSA Lockbox for customer-managed encryption - Cloudback never holds the private keys - Storage options: Cloudback Managed Storage or BYOS (Amazon S3, Azure Blob, Google Cloud Storage, Wasabi) Restore rebuilds the workspace into a new Linear environment, in dependency order. Cycles attach to the right projects, issues land under the right states, labels exist before anything references them. Setup takes under 5 minutes at https://app.cloudback.it/. Connect a Linear workspace, configure a backup definition, add subscription, and run the first backup. Cloudback now covers GitHub, GitLab, Azure DevOps, and Linear - trusted by 1.7k+ customers with 4M+ backups created.

We’re excited to announce that Cloudback now supports Azure DevOps platform!🚀😎😊 Teams using Azure DevOps can now protect their repositories and metadata with automated daily backups, instant restores, and flexible storage options — all integrated directly into their existing workflows. Cloudback is also officially listed on the Microsoft Azure Marketplace. By subscribing through the Marketplace, you can: - Add Cloudback directly from your Azure account - Use your existing Azure billing setup - Consolidate Cloudback costs into your standard Azure billing cycle - Simplify procurement and subscription management Start backing up your Azure DevOps projects today: https://lnkd.in/gekArbJB