Backup and export

Your data is yours, and Cobblr makes it easy to take a full copy out.

Backups

A backup captures a workspace completely: its items, fields, views, and settings. Restoring one brings the workspace back as it was, with the same records intact, so a backup is a real safety net and a way to move between instances.

Where backups go

On a self-hosted install, everything lives in bind-mounted folders under ./data, so copying that directory is already a complete backup (see Self-hosting -> Backups). You can also schedule backups to an off-box destination: any S3-compatible bucket (AWS, Cloudflare R2, Backblaze, MinIO), or Google Drive (shown once the operator has registered a Google OAuth app for the instance).

Each destination has a View backups button that lists what is actually sitting in it right now, with each backup's date, time, and size, so you can confirm the copies exist without opening the bucket or the Drive folder yourself. Once Google Drive is connected, its button reads Reconnect Google Drive, which is only needed if the authorization expires.

Export

Beyond full backups, you can export your data in portable form to work with it elsewhere or keep an archive. No lock-in: what you put into Cobblr, you can get back out.

Blueprint vs backup

They answer different questions. A blueprint is the configuration half: the modules, instances, bundles and your overrides, custom fields, wires, views, and nav, with no records in it. Install a blueprint and you stamp a new workspace shaped like the old one. A backup is everything, data included, and a restore preserves record ids, so QR labels and links keep resolving after the restore.