Skip to main content
Data backups keep a copy of your workspace’s data in a cloud storage bucket you own. Each night, Miru writes a full backup of your workspace to your buckets. Every backup is a single zip archive that holds a complete copy of your workspace’s resources. An archive contains the complete workspace state exactly as it was at that moment. By default, backups are off. To turn them on, see set up backups.

​
How it works

  1. Once a day, Miru reads your workspace at a single point in time, ensuring that all the resources in a backup are consistent with each other.
  2. Miru writes each resource as it appears in the latest Platform API version into a single zip archive (see archive format).
  3. Using the credentials from your bucket connection, Miru uploads the archive to your bucket.
A failed backup writes nothing. Miru only ever adds objects to your bucket. Deleting something in Miru never deletes anything in your bucket, and Miru never reads or deletes an archive once it’s written. To control how long archives are kept, add a lifecycle rule to the bucket.

​
What’s included

An archive contains all resources from the latest Platform API version. As of writing, the latest version is 2026-11-04.everglades, which contains: Any resource additions, modifications, or deletions to the latest platform API are reflected in the currently backed up archive.
Last modified on November 6, 2026