Skip to content

docs(cloud): add Stopped Instances terms to Pro tier#509

Open
dragnot wants to merge 3 commits into
mainfrom
docs/pro-stopped-instances-terms
Open

docs(cloud): add Stopped Instances terms to Pro tier#509
dragnot wants to merge 3 commits into
mainfrom
docs/pro-stopped-instances-terms

Conversation

@dragnot

@dragnot dragnot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Summary

Add a Stopped Instances policy to the Pro tier Terms section, alongside the existing pricing terms.

Changes

  • cloud/pro-tier.md Terms section gains two items:
    • Stopped Instances: a stopped instance is removed after 14 days. Resume within 14 days to keep it.
    • Snapshot Retention: after removal a snapshot is kept for an additional 14 days, with a footnote recommending frequent database backups.

Testing

Docs-only change. Follows existing Terms subsection structure.

Memory / Performance Impact

N/A (docs-only).

Related Issues

N/A


Approver: @dudizimber
FYI: @MuhammadQadora

Summary by CodeRabbit

  • Documentation
    • Expanded Pro pricing/usage details with new sections for Stopped Instances, including a 14-day removal window and snapshot-based restore for the next 14 days.
    • Added Snapshots retention guidance, including auto-deletion after 14 days (including pre-removal snapshots).
    • Added Backups details, including automatic backups every 12 hours with 7-day retention.

Add Stopped Instances and Snapshot Retention items to the Terms section.
A stopped instance is removed after 14 days. After removal a snapshot is
kept for an additional 14 days. Adds a footnote recommending frequent
database backups.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@dragnot dragnot requested a review from dudizimber June 24, 2026 00:36
@coderabbitai

coderabbitai Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0495a06c-4a93-4a61-acc1-177baf0cc2c2

📥 Commits

Reviewing files that changed from the base of the PR and between f737bd9 and ce2d9ca.

📒 Files selected for processing (1)
  • cloud/pro-tier.md
✅ Files skipped from review due to trivial changes (1)
  • cloud/pro-tier.md

📝 Walkthrough

Walkthrough

cloud/pro-tier.md adds three Replicated subsections describing stopped instance removal, snapshot retention, and automatic backup cadence and retention.

Changes

Pro Tier Documentation

Layer / File(s) Summary
Stopped Instances, Snapshots, and Backups
cloud/pro-tier.md
Adds subsections for stopped instance removal after 14 days with a restore snapshot, snapshot auto-deletion after 14 days, and backups every 12 hours retained for 7 days.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • dudizimber

Possibly related PRs

  • FalkorDB/docs#507: Touches the same cloud documentation area and discusses tier-specific persistence and recovery limits.

Poem

🐇 I nibble docs with tidy cheer,
Three fresh notes now nestle here.
Snapshots fade, backups endure,
Stopped instances get rules made sure.
Hop-hop, the cloud pages sing anew!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches a real, central part of the docs change by adding Stopped Instances terms to the Pro tier.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/pro-stopped-instances-terms

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Comment thread cloud/pro-tier.md Outdated
> ⚠️ Prices are subject to change

### Stopped Instances
> An instance that is stopped will be removed after 14 days. Resume it within 14 days to keep it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will be removed after 14 days. Before removal, a snapshot will be taken containing it's data, allowing it to be restored for the next 14 days.

Comment thread cloud/pro-tier.md Outdated
> An instance that is stopped will be removed after 14 days. Resume it within 14 days to keep it.

### Snapshot Retention
> Once an instance is removed we keep a snapshot for an additional 14 days.\*

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Snapshots in general, not just the ones taken before deletion.

Comment thread cloud/pro-tier.md Outdated
### Snapshot Retention
> Once an instance is removed we keep a snapshot for an additional 14 days.\*
>
> \* We recommend backing up your database on a frequent basis.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Backups are taken automatically every 12h and retained for 7 days.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dudizimber this is different i recommend customers to backup their data regardless to them own sytem, i want to keep this sentence

Reword Stopped Instances to note a snapshot is taken before removal and
is restorable for 14 days. Replace the snapshot recommendation with the
actual backup policy: automatic backups every 12h retained for 7 days.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@dragnot dragnot requested a review from dudizimber June 24, 2026 14:17
@dragnot

dragnot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

@dudizimber applied your feedback:

  • Stopped Instances now says a snapshot is taken before removal and is restorable for 14 days.
  • Replaced the snapshot section with Backups: automatic backups every 12h retained for 7 days.

Re-requesting your review. FYI @MuhammadQadora

Comment thread cloud/pro-tier.md
Comment on lines +92 to +93
### Backups
> Backups are taken automatically every 12h and retained for 7 days.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New section:
Snapshots:
Snapshots are automatically deleted after 14 days.

Add a Snapshots section clarifying that all snapshots are automatically
deleted after 14 days, including the one taken before a stopped instance
is removed. Addresses review feedback.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@dragnot

dragnot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor Author

@dudizimber added the Snapshots section per your comment, worded so it is clear it covers all snapshots, not only the pre-removal one:

All snapshots are automatically deleted after 14 days. This applies to every snapshot, including the one taken before a stopped instance is removed.

Please approve and resolve your threads so we can merge to main. FYI @MuhammadQadora

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