Linear backup

Linear backup you can actually restore.

Back up issues, comments, documents, projects, and Linear-hosted files - then restore the core work graph with a clear report of anything Linear's API cannot recreate exactly.

See exactly what we restore →
  • Daily encrypted snapshots
  • Restore report on every recovery
  • Dogfooded daily on our own workspace

Restore Report

Daily snapshot 2026-05-24

2026-05-24 01:04:17 UTC

82

entries reconstructed

100%

hash match

103 KB

encrypted

0

errors

47 comments

57%

32 issues

39%

2 projects

2%

1 viewer

1%

Hash matches: 82

Hash mismatches: 0

Decrypt failures: 0

Full snapshot · AES-256-GCM · R2 Standard storageDOGFOODED DAILY

Linear had a real January 2024 data-loss incident. Even excellent SaaS vendors should not be the only recoverable copy of the work your engineering team runs on.

Scope

What gets backed up

Backed up

  • Issues + descriptions + identifiers
  • Comments + threads
  • Projects + initiatives + roadmaps
  • Cycles
  • Teams + workflow states + labels
  • Documents (current version)
  • Custom views
  • Attachment metadata
  • Linear-hosted attachment file bytes

Backed up with caveats

  • User metadata (no identity / SCIM / SAML / sessions / roles)
  • Integration references (no OAuth grants / webhook secrets / external sync state)

Restore

How restore works

1

Recreate reference data

Teams, workflow states, labels, projects, dependency-aware.

2

Restore work artifacts

Issues, comments, documents, cycles, attachments in dependency order.

3

Produce a restore report

Every entity counted, every mapped user noted, every skipped field listed. No silent gaps.

See a real restore report →

Limits

What we don't restore

We'd rather lose a sale than create restore expectations we can't meet.

Bit-exact restoration of the original workspace
Original Linear-generated issue numbers, URLs, or activity history
Audit logs, notification feeds, document revision history
Linear AI / Asks / notification feeds
Linear users, authentication identities, SCIM/SAML, sessions, roles, security config (we map to existing users where permissions allow)
Third-party integrations, OAuth grants, webhook secrets, external sync state
Jira-style custom fields unless Linear exposes a stable API-accessible field surface
External file contents behind Slack, GitHub, Zendesk, Salesforce URLs (unless those systems are separately authorized)

Security

Security & storage

Encrypted at rest with AES-256-GCM envelope encryption (per-tenant keys) before any object lands in storage
Cloudflare R2 Standard storage by default ($0 restore egress)
SOC 2: Type I planned after the first 5 paying workspaces. Type II observation starts after Type I controls stabilize.
Open-source restore verifier (CLI) planned for public launch - verify snapshot hashes without our hosted app.

Pricing

Pricing

Pro

Pro

$299 / Linear workspace / month

  • Daily backups
  • Daily incremental snapshots
  • Unlimited self-serve restore dry runs
  • Encrypted at rest (AES-256-GCM, R2 Standard)
  • Restore reports on every recovery
  • Email alerts on snapshot failure
  • Standard support

Annual or monthly, no per-seat fees. Self-serve checkout at launch.

Business

$599 / Linear workspace / month

  • Everything in Pro
  • Unlimited self-serve production restores
  • Priority restore queue
  • Vendor security questionnaire support

Self-serve checkout at launch.

No free tier. Backup is bought as risk transfer, not feature trial.

Restore report

Sample from daily dogfood

The actual report from our own daily snapshot — same artifact every customer receives after a restore.

See the full scope page →

Restore Report

Daily snapshot 2026-05-24

2026-05-24 01:04:17 UTC

82

entries reconstructed

100%

hash match

103 KB

encrypted

0

errors

47 comments

57%

32 issues

39%

2 projects

2%

1 viewer

1%

Hash matches: 82

Hash mismatches: 0

Decrypt failures: 0

Full snapshot · AES-256-GCM · R2 Standard storageDOGFOODED DAILY

Platform roadmap

Linear is wedge #1 on a reusable backup platform. Storage, encryption, scheduling, restore orchestration, billing, audit, and dashboard are shared. Future connectors plug in via a typed interface - same security guarantees, same restore report shape. Target: 80%+ shared code by wedge #2.

FAQ

FAQ

Can you restore exact issue numbers?

No. Linear assigns identifiers on issue creation; restore produces new ones. The restore report maps old → new explicitly.

Do you back up attachments?

Yes - Linear-hosted attachment metadata and file bytes. External file URLs (Slack, GitHub, etc.) require separate authorization.

Do you restore integrations?

No automatic restore. Integration references are backed up; you reauthorize OAuth grants and webhook secrets manually after restore.

Can we restore to a different workspace?

Yes. Restore engine takes a target workspace; users map to whoever's available there.

How long does restore take?

No published SLA until we measure a seeded 10K-issue restore. We will publish real numbers, not aspirational ones.

Can I see exactly what gets backed up before I sign up?

Yes - that's what /scope is for. Full entity-by-entity inventory, no marketing fluff.

Linear backup you can actually restore.

Read the Linear restore scope →