The things people ask first.

In storage you already own and control. You give Caryvane credentials for an Amazon S3 bucket, an Azure Blob container, an SFTP server, an SMB share or a NAS, and the backups are written there. Caryvane keeps no copy of your data and sells you no storage, so you can read your backups without us.

Yes. Caryvane runs an MCP server for Claude and VS Code Copilot, and exposes a Custom GPT Action for ChatGPT. Each user issues their own key and can revoke it, and the key carries one of four permission tiers: read-only, read plus start and cancel runs, plus create and edit jobs, or full including deletes. An assistant can be given exactly as much as you want it to have and no more.

Yes. A cloud-to-cloud job reads from any supported storage and writes to any other — an Azure Blob container into Amazon S3, an S3 bucket to SFTP, a SharePoint library onto a NAS. It can copy a whole container or a single prefix within one. You choose per job whether it runs on one of your own machines, so the data passes through hardware you control, or on a hosted worker so nothing of yours has to be switched on.

Windows 11 and Windows Server; macOS 26 and later on both Apple silicon and Intel; and Linux on x86-64 and arm64, packaged as .deb and .rpm. The same agent and the same console cover all three.

Yes. Mail, OneDrive and SharePoint are copied out to storage you hold. Runs are incremental by change token rather than a full sweep each time, older mail can be archived out of the mailbox, and individual items or whole mailboxes can be restored.

Yes. Gmail, Drive, Calendar, Contacts and Shared Drives are copied out to storage you hold. It connects once for the whole domain with a service account rather than needing each user to consent, runs incrementally rather than a full sweep each time, can archive older mail and Drive files out to a set you keep, and can restore mail and Drive files back to the user.

Yes. Each Xero organisation is copied every night into storage you hold: invoices, bills, payments, bank transactions, manual journals, contacts, the chart of accounts and their attachments, plus payroll (UK), fixed assets, projects and Xero Files where they are used. Every change is kept as a version, so you can browse the books as at any date, and Xero's own trial balance is captured every day. Nothing is installed; it runs on a hosted worker.

Like every Xero backup, it can only capture what Xero's API gives to apps, and Xero lets no app write back its journal or general ledger, so no product can roll an organisation back to an earlier date. Contacts, accounts, invoices, bills and credit notes can be exported in Xero's import format and brought back through Xero's own import screens; the rest is kept as a dated record for your accountant. Xero backup in full.

Because Xero charges us that way. Xero charges apps for the data they download from it, so our Xero backup is billed on its own line, never from cloud credits: a monthly fee for each organisation, and Xero data. Each organisation has 1 GB of data transfer a month, pooled across all your organisations, and its first backup includes 5 GB of data transfer free on top; only the total above the allowance is charged per GB. Storage is not on our invoice, because the backup sits in storage you already hold. Xero backup in full.

Yes. Hyper-V virtual machines are captured application-consistently while they run — the guest is asked to settle before the copy is taken — and on Server 2016 and later, follow-up backups move only the blocks that changed while still leaving a complete disk image in your storage each time. SQL Server databases are captured copy-only, so your own log backups and point-in-time restores carry on undisturbed, and Active Directory can be captured on a domain controller. Same storage, schedules and retention as every other job.

It mounts object storage as an ordinary drive, so files appear in Explorer or Finder and open in any application. Content is fetched on demand rather than synced wholesale, which means a drive can hold far more than the disk it appears on. Writes queue and upload in the background.

Either. Version history is kept according to your retention policy, and you can restore a single file from a chosen point in time, or a whole set, to the original location or somewhere else.

It is built for managing many machines rather than one. Agents enroll with a deployment token so a machine can be set up without anyone in front of it, then check in, take their jobs, report results and update themselves.

No. Installation is unattended on every platform — an MSI with silent install on Windows, a signed and notarised .pkg on macOS, and .deb or .rpm packages with a systemd service on Linux.