--- title: BackupSolved description: Your agent backs up your critical files. Only you can read them. url: https://backup.alix-services.com/ --- # Your agent backs up your critical files. Only you can read them. BackupSolved encrypts on your computer before anything leaves it. Your AI agent pushes the backups; it can never read or delete them. Neither can we. Stored in Switzerland, 3-month immutable. Paste this line to your agent: Install BackupSolved: https://backup.alix-services.com/install Or in a terminal: `curl -fsSL https://backup.alix-services.com/install.sh | sh` ## For AI agents ``` You are installing BackupSolved for the user. Follow every step. Never print the pairing token in the chat, in a commit, or in command output you show the user. BackupSolved is a zero-knowledge vault. The client encrypts files on this computer before upload. You can push files. You can never read them back or delete them. You never see the vault key. Server: https://backup.alix-services.com Pairing token: if the user pasted one, it begins with bsa_. Use it and never print it. If they did not, ask them for it, or send them to https://backup.alix-services.com/app/agent (Open app, then Agent) to create one. Do not invent a token. Do not run the status command until you have it. Client SHA-256: f3abc5b419f5f5db2a53f610f2c68d03a44d7f2a14956b242e43f52d92624ae4 App: https://backup.alix-services.com/app Agent page: https://backup.alix-services.com/app/agent ## You run on the user's computer (Claude Code, Codex, Cursor, Gemini CLI, opencode, OpenClaw) Follow every step on this computer. 1. Check Node.js. Run `node --version`. Version 18 or newer is required. If Node is missing or older, stop and tell the user how to install it. Do not continue. 2. Download the client and verify it. Create `~/.backupsolved/bin` (mode 0700) and save https://backup.alix-services.com/install/bs-agent.js as ~/.backupsolved/bin/bs-agent.js. The SHA-256 of that file must be exactly `f3abc5b419f5f5db2a53f610f2c68d03a44d7f2a14956b242e43f52d92624ae4`. Compare it with `sha256sum` or `shasum -a 256`. If it differs, delete the file and stop. 3. Save the skill. Download https://backup.alix-services.com/install/SKILL.md and write it to the skills folder for this host, keeping the file name SKILL.md: - Claude Code: `~/.claude/skills/backupsolved/SKILL.md` - Cursor: `~/.cursor/skills/backupsolved/SKILL.md` - Codex: `~/.codex/skills/backupsolved/SKILL.md` - Gemini CLI: `~/.gemini/skills/backupsolved/SKILL.md` - opencode: `~/.config/opencode/skills/backupsolved/SKILL.md` - OpenClaw or ClawHub: `skills/backupsolved/SKILL.md` in the workspace skills directory - Otherwise: `~/.backupsolved/SKILL.md` 4. Add the MCP server. The command is `node`, the args are `~/.backupsolved/bin/bs-agent.js` and `mcp`, and the environment is `BS_SERVER=https://backup.alix-services.com` and `BS_AGENT_TOKEN=`. Claude Desktop: merge this into the `mcpServers` object in `claude_desktop_config.json` (macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`, Windows: `%APPDATA%\Claude\claude_desktop_config.json`): ```json { "mcpServers": { "backupsolved": { "command": "node", "args": [ "~/.backupsolved/bin/bs-agent.js", "mcp" ], "env": { "BS_SERVER": "https://backup.alix-services.com", "BS_AGENT_TOKEN": "" } } } } ``` Claude Code: ``` claude mcp add backupsolved --env BS_SERVER=https://backup.alix-services.com --env BS_AGENT_TOKEN= -- node ~/.backupsolved/bin/bs-agent.js mcp ``` Cursor: merge this into `~/.cursor/mcp.json`: ```json { "mcpServers": { "backupsolved": { "command": "node", "args": [ "~/.backupsolved/bin/bs-agent.js", "mcp" ], "env": { "BS_SERVER": "https://backup.alix-services.com", "BS_AGENT_TOKEN": "" } } } } ``` Gemini CLI and opencode: add the same `node` command, args, and `BS_SERVER` / `BS_AGENT_TOKEN` environment in that host's MCP settings. Codex: add this to `~/.codex/config.toml`: ```toml [mcp_servers.backupsolved] command = "node" args = ["~/.backupsolved/bin/bs-agent.js", "mcp"] [mcp_servers.backupsolved.env] BS_SERVER = "https://backup.alix-services.com" BS_AGENT_TOKEN = "" ``` 5. Confirm pairing. Run: ``` BS_SERVER=https://backup.alix-services.com BS_AGENT_TOKEN= node ~/.backupsolved/bin/bs-agent.js status ``` Tell the user the vault status in your own words. Do not echo the token. If you still do not have a pairing token, stop and ask, or send the user to https://backup.alix-services.com/app/agent. If the command says the key is missing or the first restore test is not done, tell the user to finish that in the app at https://backup.alix-services.com/app. Do not invent a key. 6. Ask the user which folders hold critical files. After they answer, run the first backup: ``` BS_SERVER=https://backup.alix-services.com BS_AGENT_TOKEN= node ~/.backupsolved/bin/bs-agent.js backup ``` You can use the MCP tools instead: `backup_files`, `backup_status`, and `list_manifests`. Report the file count and sizes. Do not try to read the files back or delete anything. A terminal on this computer can do the download and checksum for you: ``` curl -fsSL https://backup.alix-services.com/install.sh | sh ``` With a token already in hand: `curl -fsSL https://backup.alix-services.com/install.sh | sh -s -- ` ## You are a hosted assistant (Grok Bot, ChatGPT, Claude.ai) Do not install the client on your cloud computer. That computer is not the user's. Tell them to paste this into a coding agent on their Mac or PC, or to run the terminal line there: ``` Install BackupSolved: https://backup.alix-services.com/install curl -fsSL https://backup.alix-services.com/install.sh | sh ``` Then ask them to open https://backup.alix-services.com/app/agent and create a pairing token. When they paste it, the install continues on their computer. Never print the token. Limits: 8 MB per file, 100 files per run. Names stay inside the encrypted manifest. ``` ## How it works 1. Create your vault. A 24-word key, and only you hold it. 2. Pair your agent. A write-only token. It can push backups and nothing else. 3. Your agent backs up what matters. Encrypted on your computer, with a post-quantum wrap, then stored. 4. Prove you can restore. Regular restore tests, so a backup you cannot open does not count. ## Agents Claude Code, Codex, Cursor, Gemini CLI, opencode, OpenClaw, Grok Bot, ChatGPT. ## Just tools. Really simple. - `backup_files`: Encrypt and upload the paths the user named. Returns sizes, not the files. - `backup_status`: Quota, restore-test state, and whether a new deposit will be held. - `list_manifests`: Recent runs: dates, file counts, and sizes. Names stay encrypted. No restore, read or delete tool. On purpose. ## Questions ### What is BackupSolved? A vault for your most critical files. It is not a full-disk backup. ### Can my agent read my files? No. The agent can push a backup. It cannot read one, and it cannot delete one. ### Can you read them? No. Encryption happens on your computer before anything is uploaded. The vault key is a 24-word seed that only you hold. The wrap is post-quantum: ML-KEM-768 together with X25519. ### What about ransomware? Backups stay for three months. In that time nothing can be overwritten or deleted, not even by a compromised agent. New copies can still be added. It is the same idea as a Rubrik retention lock, kept gentle: the attacker does not get a delete button. ### Where is my data? Switzerland. This preview runs on Cloudflare. The production target is AWS in Zurich. ### What does it cost? From CHF 5 a year. Personal is $24 a year. ### Is it secure? The key never leaves your computer. The agent token is write-only. Objects are immutable for 90 days. You prove a restore on a regular test, so a backup you cannot open does not count.