Skip to content

docs(terms): workspace backup add-on - #144

Merged
sre-helmcode merged 5 commits into
mainfrom
docs/workspace-backup-terms
Oct 4, 2026
Merged

sre-helmcode merged 5 commits into
mainfrom
docs/workspace-backup-terms

Conversation

@sre-helmcode

@sre-helmcode sre-helmcode commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

What

Terms of Service (EN src/pages/terms.astro + ES src/pages/es/terms.astro), under "Membership and payments", new paragraph #workspace-backups for the NaN community workspace backup add-on (#130):

  • Workspaces have no backups unless the add-on is active.
  • Daily snapshots, kept 7 days, crash-consistent (restoring = power cut at snapshot time; running databases recover as after a power cut).
  • Restoring a snapshot brings back everything on the disk at that time, including access the member configured themselves (SSH keys, SSH server settings); only the current NaN SSH key is re-applied.
  • Enabling charges the first payment right away (prorated to the renewal date on a slot subscription); turning it off removes it immediately with no refund for the current month.
  • Turning the add-on off or deleting the workspace deletes all snapshots permanently.
  • Owner decision 2026-10-02: if the slot ends or a free workspace loses the benefit, billing stops and the snapshots are kept until the workspace itself is deleted at the end of its grace period, then deleted permanently.

"Last updated" bumped to October 2, 2026. There is no workspace docs page on the site yet, so nothing to mirror.

Tests

  • New src/tests/legal/workspaceBackupTerms.test.ts pins every promise in both languages, the placement under the payments section, and that the slot-end clause never says snapshots are deleted at slot end.
  • npx vitest run: 1342 passed. npm run build: OK.

Deploy notes

No VERSION file in this repo. Merge whenever the add-on is about to be offered (the UI stays hidden until prices are configured).

🤖 Generated with Claude Code

barckcode and others added 5 commits October 2, 2026 22:36
Under Membership and payments (EN + ES): no backups unless the add-on
is active; daily crash-consistent snapshots kept 7 days; enabling
charges right away (prorated on a slot), turning it off gives no
partial refund; turning it off or deleting the workspace deletes all
snapshots; an ending slot or lost free-workspace benefit stops billing
and keeps snapshots until the workspace is deleted at the end of its
grace period. Pinned by tests.

Refs #130

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds the product decision: up to 3 restores per workspace in any 24h,
no on-demand backups; restores only while the add-on is active (during
grace: active slot or renewed membership, then turn the add-on on
again, billed again); when billing ends no new snapshots are taken and
existing ones are kept until the workspace is deleted; back in good
standing but not re-enabled within 14 days -> add-on ends, snapshots
deleted. EN + ES, each promise pinned by tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Kept snapshots are not pruned while the add-on is off; re-enabling it
resumes retention and the next daily snapshot removes every snapshot
older than 7 days (cloud-api #295). EN + ES, pinned by tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s on again

The previous wording ("so restore the one you need first") promised
something the API cannot do: restore is blocked while the add-on is off,
and after it is on again cloud-api #295 lists and restores only snapshots
within the 7-day retention; the next daily backup deletes older kept
snapshots. EN + ES updated, pinned by tests (including a negative assert
on the old promise).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sre-helmcode
sre-helmcode merged commit d248ac4 into main Oct 4, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants