Clarify suspend volumes and capacity#2409
Merged
Merged
Conversation
The suspend/resume page didn't mention volumes or whether a suspended machine frees up regional capacity, both of which come up when people evaluate suspend. - Add a "Suspend and volumes" section: a volume isn't required for suspend, and volume data is unaffected by suspend, resume, and cold starts (the snapshot and the volume are separate things). - Add a note that a suspended machine releases host CPU and memory like a stopped machine, but still exists and uses storage. - Note the volume cost for a suspended machine in the Billing section.
The suspend/resume page didn't mention volumes or whether a suspended machine frees up regional capacity, both of which come up when people evaluate suspend. - Add a "Volume behavior with suspend" section: a volume isn't required for suspend, and volume data is unaffected by suspend, resume, and cold starts (the snapshot and the volume are separate things). - Add a note after Billing: suspending lowers cost (storage only) but doesn't free up room in a region, since a suspended machine still counts toward regional capacity. - Note the volume cost for a suspended machine in the Billing section.
Lucais11
force-pushed
the
clarify-suspend-volumes-and-capacity
branch
from
a7d60ac to
6a02934
Compare
Group the regional-capacity note inside the Billing section instead of floating it between horizontal rules, drop the circular link back to Billing and the duplicated cost wording, and fix the phrasing (a region's capacity is shared, not a per-customer quota).
kcmartin
requested changes
Jun 9, 2026
kcmartin
left a comment
kcmartin
left a comment
Contributor
There was a problem hiding this comment.
Thanks! I left some copy edit suggestions.
Co-authored-by: Kristin Martin <kcmartin@users.noreply.github.com>
Co-authored-by: Kristin Martin <kcmartin@users.noreply.github.com>
Co-authored-by: Kristin Martin <kcmartin@users.noreply.github.com>
Co-authored-by: Kristin Martin <kcmartin@users.noreply.github.com>
Co-authored-by: Kristin Martin <kcmartin@users.noreply.github.com>
kcmartin
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents two things the Machine suspend/resume page didn't cover, that also came from customer queries:
Volumes: A volume isn't required for suspend (memory state is saved to Fly-managed storage, not your volume), and volume data is unaffected by suspend, resume, and cold starts.
Regional capacity: Suspending lowers cost (storage only, no CPU/RAM) but doesn't free up room in a region; a suspended machine still counts toward regional capacity, so it can't be used to pack more machines into a constrained region.