A private AI assistant becomes useful because it learns your world.
It knows your preferred tools. It has your automations. It has chat history, schedules, settings, installed skills, browser state, API connections, local projects, and little bits of context that make it feel like your assistant instead of a fresh chatbot.
That state is valuable.
So we built ClawKeep: encrypted backup for ClawBox and OpenClaw devices.
The Problem: Your AI Assistant Is More Than an App
Most backup tools are built around files: photos, documents, databases, source code. That matters, but an always-on AI assistant has a different kind of value.
A ClawBox does not just store files. It runs workflows:
- email summaries and drafted replies
- scheduled reminders and follow-ups
- browser automations
- smart-home routines
- installed OpenClaw skills
- local workspace projects
- portal/device configuration
- chat and assistant state
If that device is reset, reflashed, or moved to a new SSD, you do not want to rebuild all of that by hand.
ClawKeep is the safety net for that state.
What ClawKeep Backs Up
ClawKeep uses the OpenClaw backup system to create a timestamped archive of the important parts of the device, including OpenClaw state, configuration, credentials, workspaces, and installed assistant context.
Then ClawKeep uploads that archive to your ClawBox account storage so it can be recovered later from the portal.
In practice, this protects the pieces that make the assistant personal:
- conversations and assistant memory/state
- OpenClaw configuration
- connected-account and skill configuration
- workspace files and automation projects
- device state needed after a reset, SSD replacement, or re-flash
The goal is simple: experiment freely, knowing your AI workstation has a recovery path.
Encryption Happens Before Upload
Backups should not create a new privacy problem.
ClawKeep encrypts the backup on the device before upload. The passphrase is stored locally on the ClawBox with device-only permissions and is used for encryption before the archive leaves the machine.
Under the hood, ClawKeep encrypts with OpenSSL AES-256-CBC using PBKDF2 with 600,000 iterations. The backup is uploaded only after encryption succeeds, and the plaintext archive is wiped/unlinked before the upload step continues.
That means the cloud bucket stores encrypted backup files, not readable OpenClaw state.
Important tradeoff: if you lose the passphrase, the backup cannot be decrypted. That is the right failure mode for a private AI device. The operator should not be able to recover your private assistant state without your secret.
Portal-Managed, Device-Scoped Access
ClawKeep does not leave long-lived cloud credentials lying around on the device.
When a backup starts, the ClawBox device asks the OpenClaw Hardware portal for short-lived, scoped storage credentials. Those credentials are limited to that user's backup prefix. The device uploads the encrypted snapshot, reports status back to the portal, and the portal shows the latest backup state.
This gives customers a normal product experience without turning backup into a cloud-admin project:
- pair the device with your portal account
- set a backup passphrase
- run backups manually or on a schedule
- see backup status and cloud usage in the portal
- download or restore when needed
No S3 console. No hand-built bucket policy. No guessing whether the last backup worked.
Built for Real Recovery Moments
ClawKeep is designed for the moments that usually hurt:
- you reflash a ClawBox
- an SSD is replaced
- an update or experiment breaks your setup
- you want to move your OpenClaw state to a fresh device
- you need to recover after a factory reset
A personal AI computer is meant to be customized. People should be able to install skills, test workflows, change providers, and automate real work without feeling like every experiment risks the whole setup.
Backups make the product braver.
Plans and Storage
ClawKeep is integrated with the ClawBox portal plans:
- Free: 1 GB ClawKeep cloud backup quota
- Pro: 5 GB ClawKeep cloud backup quota
- Max: 50 GB ClawKeep cloud backup quota
Pro and Max also add higher ClawBox AI usage, more API tokens, and Remote Desktop access. Max is built for heavier users who want more automation, more model usage, and more room for assistant state.
Why This Matters for AI Hardware
The next generation of AI devices will not be stateless chat windows.
They will be personal systems: local files, automations, browser sessions, connected tools, schedules, memories, and workflows. That makes backup a core feature, not an afterthought.
ClawBox is built to be an always-on AI computer. ClawKeep is what lets that computer become personal while staying recoverable.
You own the device. You control the passphrase. Your backup is encrypted before it leaves the box.
That is the backup model we want for private AI.
Try ClawKeep
If you already have a ClawBox, update to the latest ClawBox OS and open the portal dashboard to check ClawKeep availability for your account.
If you are new to ClawBox, this is one of the reasons we think dedicated AI hardware matters: your assistant can run privately, automate real work, and now protect the state that makes it yours.
Get ClawBox or open the portal to manage your device.