> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mirurobotics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

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](https://docs.mirurobotics.com/data-uploads/concepts/buckets.md).

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](https://docs.mirurobotics.com/admin/backups/set-up.md).

## 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](https://docs.mirurobotics.com/references/platform-api/latest/endpoints) version into a single zip archive (see [archive format](https://docs.mirurobotics.com/admin/backups/archive-format.md#archive-contents)).
3. Using the credentials from your [bucket connection](https://docs.mirurobotics.com/data-uploads/concepts/buckets.md),
   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](https://docs.mirurobotics.com/admin/backups/set-up.md#configure-retention) to the bucket.

## What's included

An archive contains all resources from the latest [Platform API](https://docs.mirurobotics.com/references/platform-api/latest/endpoints) version. As of writing, the latest version is [2026-11-04.everglades](https://docs.mirurobotics.com/references/platform-api/2026-11-04), which contains:

* [Devices](https://docs.mirurobotics.com/concepts/devices/overview.md)
* [Groups](https://docs.mirurobotics.com/concepts/groups/overview.md)
* [Releases](https://docs.mirurobotics.com/concepts/releases.md)
* Git commits
* [Deployments](https://docs.mirurobotics.com/concepts/deployments/overview.md)
* [Config types](https://docs.mirurobotics.com/cfg-mgmt/concepts/config-types.md)
* [Config schemas](https://docs.mirurobotics.com/cfg-mgmt/concepts/schemas/overview.md)
* Config schema git commits
* [Config instances](https://docs.mirurobotics.com/cfg-mgmt/concepts/config-instances.md) (including their contents)
* [Calibrations](https://docs.mirurobotics.com/cfg-mgmt/concepts/calibrations.md) (including their contents)
* [API keys](https://docs.mirurobotics.com/admin/apikeys.md)
* [Users](https://docs.mirurobotics.com/admin/users/overview.md)

Any resource additions, modifications, or deletions to the latest platform API are reflected in the currently backed up archive.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.