Skip to main content
floo keeps change history for managed Postgres and 30 days of object versions for managed Storage. Managed Redis is a cache with no backup. Your source code lives in GitHub, and resources you connect yourself are backed up by their own provider.

​
What floo can restore

Each environment has its own data, so a restore names the environment.

​
Restore a Storage object

For an object that was overwritten or deleted by mistake:
Add --env prod for the prod bucket. The restore copies the chosen version back to the live path and records an audit event. Versions cover object overwrites and deletes, not deleting the whole storage service. See floo storage.

​
Request a database restore

The CLI has no database restore command. Email team@getfloo.com with:
  • The app and org.
  • The environment: dev, prod, or a preview.
  • The resource: Postgres, or Storage if you cannot restore it yourself.
  • The table, schema, rows, or object path, if you know them.
  • The approximate time before the bad change.
  • Whether restoring into a copy instead of in place is acceptable.
floo confirms the restore window, the target, the expected impact, and how to verify the result before it changes any data.

​
Not covered yet

  • Database restore from the dashboard or CLI.
  • Redis restore.
  • Cross-region disaster recovery.
  • Recovering a deleted storage service.

​
Next steps

Postgres

Migrations, schema changes that survive rollback, and connection limits.

Storage

Buckets, signed URLs, and object versions.