Hosting a backup means lending part of your pool to a friend. Their folders arrive encrypted, use only the space you agree to, and give them no access to your server. Accepting takes about a minute.
HexOS does not email you about requests. When a buddy tells you they have sent one, open the Backups panel from the dashboard and click the Requests tile. The Pending requests dialog lists every request waiting for you.

You lend disk space. You choose how much. HexOS reserves that amount on the pool you pick, so the backup cannot grow past it and your own data cannot fill the space it needs.
You cannot read their data. Only encrypted folders can be sent to another account. The copies stay encrypted on your pool, and your connection view shows "Only {name} can view their backup data." instead of a folder list.
They cannot browse your server. Hosting gives your buddy no access to your files, folders, or Command Deck. The tunnel between the two servers carries only backup traffic.
You can remove it. It is your disk. Remove connection deletes everything they have stored with you, and they are notified.
Accepting reserves the space on your pool and starts provisioning automatically. Their first backup begins as soon as provisioning finishes. A large first run can take hours; later runs send only what changed.
Tip: Backups are compressed before they are stored, so the space your buddy actually uses is often less than the folder size they asked for. See Compression.
Decline refuses a request. Nothing is stored and nothing is deleted, because nothing was ever copied.
Your buddy can withdraw a request they sent before you respond. Either way, only an invitation is cancelled.
The connection appears under Hosting backups for in the Backups panel and in the Hosted backups table on the Backups page. Open it to see how much of the reservation is in use, the schedule, and your transfer speed.

From here you can:
Danger: Remove connection permanently deletes your buddy's backup and every restore point in it. Their own files on their own server are untouched, but the offsite copy is gone. Either side can do this. See Removing backups.
Before each run HexOS estimates the size of the next send. If it will not fit in the reservation, both you and your buddy get a notice explaining how much is needed. If the reservation cannot hold the next run at all, HexOS pauses the connection for space rather than failing every night, and resumes on its own when the reservation grows or the next run fits. If your own pool is full, the notice says so instead, because a bigger reservation would not help. See Backup troubleshooting.
Danger: Unclaiming or resetting a server that hosts backups removes the hosted copies. The unclaim dialog's "Pool data will not be affected" refers to the server's own files, not to backups you hold for others.
If you plan to unclaim, reset, rebuild, or sell a server that hosts backups:
Help: Not sure whether a connection is one you send or one you host? See Backup troubleshooting or ask in the HexOS Discord Community.
Contribute: to help to improve HexOS documentation join the #Docs channel on Discord today! Send feedback, suggestions or contribute a guide.