A private AI assistant becomes useful because it accumulates state: conversations, settings, installed skills, automations, workspace files, and local context.
That state is what makes the assistant personal — and losing it after a reset, re-flash, or SSD replacement is painful.
We built ClawKeep for ClawBox to protect that state. It creates OpenClaw backups, encrypts them on the device before upload, uses short-lived scoped storage credentials, and reports backup status back to the ClawBox portal.
Why backup matters for AI hardware
Most backup tools are built around files: photos, documents, databases, source code. A local AI assistant is different. It runs workflows and stores operational context:
- OpenClaw configuration
- installed skills and connected-tool settings
- workspace files and automation projects
- assistant state and memory
- device state needed after a reset, SSD replacement, or re-flash
A personal AI computer should be safe to customize. Users should be able to install skills, test providers, automate real work, and experiment without feeling like one broken setup means starting from zero.
Encryption before upload
ClawKeep encrypts the backup on the device before upload. The passphrase stays on the ClawBox. The cloud bucket stores encrypted backup files, not readable OpenClaw state.
That tradeoff is intentional: if you lose the passphrase, the backup cannot be decrypted. For a private AI device, the operator should not be able to recover your assistant state without your secret.
Portal-managed recovery
ClawKeep uses the ClawBox portal for normal product workflows:
- pair the device with your account
- set a backup passphrase
- run backups manually or on schedule
- see backup status and cloud usage
- download or restore when needed
No S3 console, no hand-built bucket policy, no guessing whether the last backup worked.
Full article / canonical version:
Happy building 🤖
Top comments (0)