docs(cloud): add Stopped Instances terms to Startup tier#508
Conversation
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. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Warning Review limit reached
More reviews will be available in 57 minutes and 2 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. 📝 WalkthroughWalkthroughTwo new subsections are added to ChangesStartup Tier Policy Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@cloud/startup-tier.md`:
- Around line 56-61: In the Snapshot Retention section, correct the snapshot
retention period from 14 days to 30 days. The text currently reads "Once an
instance is removed we keep a snapshot for an additional 14 days" but should be
updated to say "30 days" instead. Ensure the Stopped Instances section remains
unchanged as it correctly states the 14-day removal period for stopped
instances.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| ### Stopped Instances | ||
| > 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. | ||
|
|
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🔴 Critical
🧩 Analysis chain
🌐 Web query:
FalkorDB startup tier stopped instance removal policy 14 days
💡 Result:
FalkorDB has been actively developing a policy to address the management of stopped production (PROD) instances, specifically to prevent incurring storage costs for inactive resources [1]. As of June 2026, work is underway to implement a policy where instances that remain in a stopped state for 14 days will be automatically deleted [1]. Key details regarding this initiative include: * Policy Objective: The policy aims to remove stopped production instances that are no longer in use, as the platform retains their storage volumes and currently does not charge customers for this inactive storage [1]. * Implementation Status: As of mid-June 2026, the implementation of this automated deletion job is pending a fix from the underlying infrastructure provider (Omnistrate) [1]. * Data Preservation: The proposed plan includes storing snapshots of these deleted instances for an additional 30 days to allow for potential data recovery if required [1]. * Comparison with Free Tier: This differs from the existing policy for the Free Tier, where instances that are not utilized for 1 day are stopped and then automatically deleted after 7 days of inactivity [2]. For users of the Startup or other production tiers, it is advised to monitor official announcements or documentation updates regarding the final activation of this 14-day deletion job [1].
Citations:
- 1: https://github.com/FalkorDB/falkordb-omnistrate/issues/700
- 2: https://docs.falkordb.com/cloud/free-tier.html
Correct snapshot retention period from 14 days to 30 days.
Line 60 contains an inaccuracy. The snapshot retention policy specifies 30 days for snapshot retention after instance removal, not 14 days. Update to: "Once an instance is removed we keep a snapshot for an additional 30 days."
The 14-day removal period for stopped instances (line 57) is accurate and aligns with current policy.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@cloud/startup-tier.md` around lines 56 - 61, In the Snapshot Retention
section, correct the snapshot retention period from 14 days to 30 days. The text
currently reads "Once an instance is removed we keep a snapshot for an
additional 14 days" but should be updated to say "30 days" instead. Ensure the
Stopped Instances section remains unchanged as it correctly states the 14-day
removal period for stopped instances.
| > ⚠️ 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. |
There was a problem hiding this comment.
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.
| > 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. |
There was a problem hiding this comment.
Snapshots in general, not just the ones taken before deletion.
Reword Stopped Instances to note a snapshot is taken before removal and is restorable for 14 days. Replace the snapshot section with the backup policy, mirroring the structure used on the Pro and Enterprise pages. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
@dudizimber mirrored your Pro/Enterprise feedback here for consistency:
|
|
New section: backups every 12h retention 7 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. Mirrors the Pro and Enterprise tiers for consistency. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
@dudizimber added the Snapshots section here too for consistency with Pro and Enterprise, worded to make clear it covers all snapshots:
Please approve and resolve your threads so we can merge to main. FYI @MuhammadQadora |
2 participants
Summary
Add a Stopped Instances policy to the Startup tier Terms section, alongside the existing pricing terms.
Changes
cloud/startup-tier.mdTerms section gains two items: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