Skip to main content
Managed Storage keeps deleted and overwritten object versions for 30 days. floo storage lists objects, reports usage, deletes objects, and restores versions. ls and usage require a READ-scoped API key. Executing rm, versions, and restore requires an ADMIN-scoped key; a customer-scope key returns 403. ls, usage, and rm require CLI v2026.09.27 or later. The local rm --preflight preview needs no credential.

​
ls

prefix filters object paths. --env selects dev or prod; the default is dev. --limit accepts 1 through 75 and defaults to 75. If the result is truncated, use a narrower prefix.

​
usage

Reports live object count and bytes for the selected bucket, scanning at most 100,000 objects. Retained versions and unfinished multipart uploads are excluded, so this is not the billable-storage total. See Storage pricing and limits.

​
rm

The preview makes no API calls and does not verify that the object exists. Removal asks for confirmation; --yes is required in JSON mode and scripts. The removed live generation remains restorable for 30 days with versions and restore. floo refuses with 409 if the bucket cannot guarantee recovery. Removal can also fail if the live object changes before the request completes; inspect it again before retrying.

​
versions

The output lists restorable generation IDs, not object contents.

​
restore

Restores are blocked when prepaid funds or monthly hard-limit headroom are exhausted, or when a spend-cap hard stop is active. Inspect floo billing balance and the storage billing restrictions before retrying.
--name and --env target a named service or the production bucket, with the same defaults as versions. Check the object path and generation with floo storage versions first. Restore copies the selected generation over the live object path and records the operation. See Storage for S3 clients, browser uploads, and pricing.