Export and backups for Hosted vaults

KB-1 gives Hosted organizations two separate ways to protect their vault data:

Export data creates a portable ZIP you can download and keep.
Hosted backups create automatic recovery archives that KB-1 can use during a service recovery.

Both start from the organization’s hosted vault engine. The live Hosted volume remains the source of truth; a backup archive is not used as a second live copy of the vault.

Download an organization export

Organization owners and administrators can download all organization vault data. Other members can ask an administrator to create the export:

Sign in to KB-1 Cloud.
Open Settings.
Select Export data.
Find the Hosted organization you want to export.
Select Download ZIP and save the file somewhere private.

KB-1 first finishes any pending vault writes, then streams the ZIP to your browser. The requested export is not saved as another Cloud copy. If the Hosted vault engine is temporarily unavailable or still getting ready, wait briefly and try the download again.

What the ZIP contains

The ZIP is a portable snapshot of the organization’s daemon-owned data. It includes:

every vault folder, including Markdown files and attachments;
portable .kb1 vault metadata;
recoverable trash; and
kb1-snapshot.json plus kb1-snapshot.complete, which describe and mark the completed snapshot.

It does not include KB-1 Cloud account records, organization memberships, billing records, daemon secrets, caches, temporary runtime files, or local Git file history.

Keep the whole ZIP intact. After downloading it, confirm that it opens and contains both snapshot marker files. Store valuable exports in a private, encrypted location you control.

Some filenames cannot be safely extracted on every operating system. Newer archives keep their bytes under a safe name and record the exact original path in the manifest. Keep this manifest with the ZIP; the daemon’s restore command uses it to recover original names and links on a compatible filesystem.

How automatic Hosted backups work

For eligible, active Hosted organizations, KB-1 checks for due backups every hour and creates a recovery archive about once every 24 hours. KB-1 keeps the 30 most recent successful archives for each organization.

Each archive is stored separately for its organization in Cloudflare R2. KB-1 treats its contents as opaque bytes and records a SHA-256 checksum so the archive can be verified before recovery. If a backup attempt fails, the last successful archive remains in place and KB-1 retries the failed organization.

Automatic Hosted backups are operated by KB-1. They are not visible in the app and are not a replacement for exports you retain yourself.

Recovery is support-assisted

Hosted backup restoration is a manual incident-recovery process. There is no self-service Restore button and KB-1 does not automatically roll a live organization back to an older archive.

If a Hosted organization needs recovery, email support@metatheory.gg before changing or deleting the organization. The recovery process verifies the archive and restores it in an isolated environment before any separately approved change to the live Hosted volume.

Self-hosted organizations

For a self-hosted organization, the Download ZIP action is unavailable because the vault data already lives on the daemon filesystem you operate. Follow Back up and restore a self-hosted vault to create and test backups from that machine.