Restorely self-serve docs

Restorely's first supported source is Linear. Hosted snapshots capture the supported Linear work graph: issues, comments, documents, projects, cycles, workspace/team references, user references, and attachment metadata that Linear exposes through API-accessible fields.

Attachment files are not downloaded. Restorely stores attachment titles, subtitles, URLs, and timestamps so the restore report can explain what was observed.

Restorely does not back up original Linear-generated issue numbers, Linear URLs, activity history, notification feeds, Linear AI or Asks, authentication identities, sessions, SCIM/SAML, security settings, OAuth grants, webhook secrets, external sync state, or attachment file bytes.

Restore expects existing Linear users and permissions where Linear requires them. Unsupported or inaccessible objects are skipped and counted in the restore report.

Defaults are part of the product surface. Customers do not tune snapshot cadence, retention, encryption, or digest cadence in a separate customer settings pane; the plan controls snapshot and retention behavior.

Alert webhook settings only route failure alerts to a customer-owned endpoint. They do not change snapshot cadence, retention, encryption, or any future digest cadence.

Snapshot availability follows the retention window for your current plan. Cancellation begins deletion processing described in the privacy page.

Pick a successful snapshot in the dashboard, enter the target Linear workspace ID, confirm, and Restorely queues the restore. The worker recreates supported containers first, then supported work artifacts, then writes a report with restored, skipped, and failed counts plus ID maps where available.

Restore is best treated as a recovery operation into a workspace you control. Review the report after the job finishes before you make business decisions from the restored workspace.

Cross-team restore can restore a snapshot into a different Linear team within the same organization, which helps with moving work between teams, sandbox testing, or recovery into a fresh team you control. Restorely remaps supported team IDs and project IDs to target-team objects; it does not preserve original Linear-generated identifiers, original Linear URLs, or per-issue activity timestamps.

A dry-run checks whether Restorely can read and decrypt a snapshot and produce the same report-shaped plan without creating Linear objects. It is used to verify backup health before a real restore.

If a dry-run result is available for your workspace, read it like a restore report: successful checks mean the snapshot is usable for supported entities, while skipped or failed items show scope or API limits to account for before relying on that snapshot.

If Linear OAuth expires, is revoked, or loses required access, Restorely cannot take new snapshots and cannot restore through that token. Existing encrypted snapshots remain stored according to the product retention and billing state for your plan, but new Linear API work stops until OAuth is connected again.

Start Linear sign-in again from the dashboard or the OAuth error page. Reconnecting creates a fresh token for the same workspace when Linear returns the same organization identity.

Paid workspaces use Stripe Checkout and the Stripe billing portal. In the dashboard, use Manage billing to change payment details or cancel the subscription. A canceled subscription stops paid hosted backup behavior according to the current product state.

To stop account access, revoke Restorely's Linear app authorization in Linear and sign out of Restorely. To request account or backup deletion, email hello@restorely.io from the workspace contact email. Restorely may verify workspace control before deleting data.

After cancellation, retained snapshots remain visible for the retention window described in the privacy policy. Restore and new hosted snapshot behavior require an active or trialing paid subscription.

1. Confirm the latest hosted snapshot succeeded in the dashboard.
2. Check the status page for recent snapshot and restore health.
3. Use a non-production Linear workspace as the restore target when testing a real restore.
4. After the job finishes, compare the restore report against the supported scope and skipped list.

Encrypted snapshots, plain restore reports, and narrow data scope. Restorely does not claim SOC 2 certification, does not provide procurement documents, and does not support regulated data. Snapshot payloads are encrypted with AES-256-GCM envelope encryption using per-tenant data encryption keys before object storage. Restorely stores the narrow Linear data needed for the supported backup and restore scope.

Restorely depends on Linear, Cloudflare R2, Neon, Vercel, Stripe, and Resend. Keep Linear permissions tight, keep billing access limited, and revoke OAuth when a workspace should no longer be backed up.

Restorely is not for regulated workloads, enterprise procurement, or compliance-driven buying. It does not offer enterprise tier, custom contracts, procurement documents, SSO or SAML commitments, BAA or HIPAA support, GDPR expansion claims, EU beta customers, or regulated-data support.

Do not put PHI, PCI data, ITAR data, children's data, or EU resident personal data into Restorely. Restorely does not support HIPAA workloads and does not claim GDPR readiness. If your buying process requires BAA, SOC 2 evidence, SSO/SAML commitments, custom contracts, procurement forms, or onboarding calls, Restorely is the wrong product.