Skip to content

docs(cloud): add Stopped Instances terms to Startup tier #508

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dudizimber merged 3 commits into from
Jun 29, 2026
+9 −0
Merged

docs(cloud): add Stopped Instances terms to Startup tier #508

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
334193d
docs(cloud): add Stopped Instances terms to Startup tier
dragnot Jun 24, 2026
4da50eb
docs(cloud): apply review feedback to Startup tier terms
dragnot Jun 24, 2026
e78a371
docs(cloud): add Snapshots section to Startup tier terms
dragnot Jun 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions cloud/startup-tier.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,15 @@ The Startup Tier includes essential features like **TLS** and **Automated Backup
>
> ⚠️ Prices are subject to change

### Stopped Instances
> An instance that is stopped will be removed after 14 days. Before removal, a snapshot will be taken containing its data, allowing it to be restored for the next 14 days.

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

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

Comment on lines +56 to +64

@coderabbitai coderabbitai Bot Jun 24, 2026

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.

📐 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:

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.

## Getting Started

<a href="https://www.youtube.com/watch?v=z0XO4pb2t5Y" target="_blank">
Expand Down