Cloudback for Linear - Automated backup and restore for Linear workspaces
by•
Cloudback runs automated, snapshot-based backups for Linear workspaces, GitHub, GitLab, and Azure DevOps. Linear capture covers 23 data categories: issues, projects, cycles, documents, comments, attachments, embedded files, and the workspace structure itself. Restore in dependency order from any backup, into a new target workspace. AES-256 with optional customer-managed keys (RSA Lockbox). SOC 2 Type II compliant. 1.7k+ customers, 14k+ repositories, 4M+ backups.
Replies
Hi PH 👋, I'm one of the makers of Cloudback. Today I'm bringing our Linear backup support to PH, because Linear is now where a lot of teams keep their full product context - issues, project decisions, cycle history, planning docs. Losing that overnight is a real risk, and Linear's native export only covers the issues table.
Here's what Cloudback does for a Linear workspace:
- Captures 23 data categories per workspace, including issues, projects, cycles, documents, custom views, initiatives, templates, comments, attachments, embedded files, workflow states, labels, teams, members, and the workspace structure itself.
- Restores the full workspace, not just a data dump - issues, projects, comments, and the structure all come back in the right order.
- Snapshot-based backup. Pick any backup, point it at an empty Linear workspace, confirm.
👥 Who it is built for:
- Engineering and product teams running their whole roadmap in Linear.
- Security and compliance teams that need backup evidence for SOC 2 audits.
- Founders who'd lose months of context if a workspace got wiped.
🔒 Security:
- AES-256 archives, customer-managed encryption keys via RSA Lockbox.
- SOC 2 Type II compliant.
- Cloudback Managed Storage in five regions, or bring your own storage across Amazon S3, Azure Blob, Google Cloud, OneDrive, Wasabi, Alibaba OSS, and OpenStack Swift.
- Audit log, Vanta integration, and many more.
Every plan starts with a free trial, so you can run a full backup and a restore drill before paying anything.
💬 Happy to answer any questions!
@zhen_han for getting context from Linear, you can use Linear MCP, it's better for operating Linear via LLM.
@zhen_han Good question - it's snapshot-based, not real-time. Backups run on a schedule (daily by default, or weekly/monthly/custom, and you pick the time and time zone). You can also take an on-demand backup anytime - it's literally one click - so right before a risky migration you can grab a fresh snapshot. Your recovery point is your most recent scheduled or manual backup.
@hex_miller_bakewell Good question! It's one backup of the whole workspace, not per user - member count just scales it with how much is in there (issues, projects, docs, comments). Example: a 10-member workspace works out to 30 units - the first 5 members are 2 units each, the next 5 are 4 each. Every plan starts with a free trial, so you can connect the workspace and see your exact units and price before paying.
I like the focus on recovery, not just backup. Most teams only think about repo protection after something goes wrong, so having automated snapshots and a fast restore path gives a lot more peace of mind.
@jostin_trunerg Glad it resonated! Restore is the half most teams skip until they need it. Snapshots are easy to set and forget - the real value is bringing the whole workspace back fast and in order when something breaks.
Backup-and-restore is one of those things nobody values until the day they desperately do, which is exactly why it's a hard sell and an easy thing to under-price. The critique above about pricing clarity is the real one.
From a product-team angle: the question I'd want answered on the page isn't "do you back up Linear," it's "how fast and how granular is restore." If someone fat-fingers a bulk archive, can I recover one project to a point in time, or is it all-or-nothing? Recovery granularity is the actual product, the backup is just the prerequisite. Worth leading with that, because it's also what justifies the price.
@vimal_ajit You're right on all counts. To answer directly: today restore is whole-workspace into an empty target - you restore from any snapshot, but it's not yet per-project or selective. Granular restore - pulling back a single project or item - is on our roadmap.
@elv1s42 That makes sense, and honestly whole-workspace-into-empty is the right v1 — it covers the actual disaster scenario (losing everything) even if it can't do the precision recovery yet. The per-project/selective restore is where it gets genuinely sticky for product teams, because the everyday fear isn't "I lost my workspace," it's "I bulk-archived the wrong thing and need just that back." Sounds like you already know that's the unlock. Good luck with the rest of the launch.
@vimal_ajit Totally agree, thank you!
the restore into a new target workspace capability is interesting for a use case that isn't immediately obvious: workspace cloning for onboarding. if you're a consultant setting up Linear for a new client with the same structure as an existing engagement, or an agency that wants to give new clients a starting template with real workflow data, restore to a new workspace becomes a setup tool not just a disaster recovery tool. is that a use case you've seen emerge from your existing customers
@ansari_adin We built restore-into-a-new-workspace for disaster recovery, but you're right that the same mechanism doubles as a setup tool - point a backup at an empty workspace and you've effectively cloned the structure and workflow data. One nuance: it restores the workspace as it was, real data included, so for a clean client template you'd either scrub the source first or keep a purpose-built "template" workspace to back up.
The restore-in-dependency-order detail is useful. Linear holds roadmap context beyond issues, so a dry-run restore before paying is a smart trust step. Can teams preview how projects, cycles, docs, and comments map before restoring into a new workspace?
@xuanlin Totally get wanting to see it first. We don't have a preview yet, but the trial period of any paid plan basically lets you test the whole thing: spin up an empty workspace, restore into it, and check how everything came across.
Great to see this live! Congrats! Which use case are you seeing the most demand for?
@borrellbr Appreciate it! Honestly, the biggest driver is just not wanting to lose it - Linear has become where teams keep their whole product brain, and a deleted project or bad import is a real risk. Compliance is the other one that comes up a lot.
Linear backups are one of those things teams only realize they need after something goes wrong. The dependency-order restore sounds especially important. Can teams restore selectively, like a project or document set, without cloning the whole workspace?
@sarveshsea Thank you. The selective restore is not yet available, but we have it planned!
Congratulations!!!
@thamibenjelloun Thank you!