Servers that can't be held hostage
Most hosting quietly locks you in. HostSSH inverts that — every server captures itself into one encrypted image you can restore, clone, or relocate anywhere.
There's a quiet assumption baked into most hosting: that moving is supposed to be painful. Snapshots stay trapped in one provider's console. "Backups" are database dumps with none of the wiring around them. The day you want to leave is the day you discover how much you were locked in.
HostSSH starts from the opposite premise. Your server should be portable by default — and the day you leave should be as easy as the day you arrived.
What "portable by default" actually means
Every HostSSH-managed server captures itself — not just a database, but the whole living system:
- the Coolify/Docker brain (apps, services, config-as-code)
- every database (with exact point-in-time fidelity)
- object storage and volumes
- OS-level customizations and secrets custody
…into a single encrypted .hsi image. That image is yours. Download it, push it to your own bucket, carry it to another provider, and restore it on a fresh box. No middleman ever holds plaintext.
Why this is different from a backup
A backup answers "can I get my data back?" Portability answers a bigger question: "can I get my whole system running somewhere else, fast, with the IP rewritten and TLS reissued — without a weekend of manual work?"
That's the line HostSSH draws. Three ways to move:
- Offline / download — capture, download the
.hsi, restore anywhere. Air-gapped, cross-provider, zero trust in any third party. - Peer transfer — generate a one-time transfer key on the source, paste it on the target, and the image streams directly between them, encrypted, in one click.
- Managed migration — point the panel at a fresh VPS; HostSSH provisions it, restores everything, rewrites the IP, brings up sidecars, reissues TLS, and flips DNS while you watch.
The house rule: a backup you haven't restored isn't a backup
So HostSSH runs restore-drills — monthly, automatic, on a throwaway target — and proves your image actually comes back (row counts match, domains return 200, TLS is valid). Recoverability you can see in a dashboard beats recoverability you're hoping for.
Hosting shouldn't be a hostage situation. Your data, your bucket, your exit — always.