HostSSH is one control plane for every machine you run — cloud VPS, bare metal, office hardware, GPU rental. Files, DB, Workers and Storage form the current platform; signed portable packs, unattended full-server relocation, and inference over your capacity remain private-beta release tracks.
One agent joins the fleet — whether the machine is a Hostinger VPS, bare metal, a dual-boot office PC behind NAT, or a rented GPU. Egress-only control plane traffic; Cloudflare Tunnel when you have no public IP. Roles tag capacity as general, inference, or automation without forking the product.
HostSSH currently captures supported Postgres data and named Docker volume bytes into encrypted restic snapshots. Broader database adapters, sidecar recreation, and the signed self-describing .hsi pack remain gated private-beta work.
The engine has restore, clone, transfer, and deterministic IP-rewrite paths. Production moves remain operator-verified until failure propagation, sandbox data checks, route/TLS verification, and paid provider rehearsals all pass.
A backup you've never restored is a rumour. HostSSH runs scheduled integrity drills: it verifies the backup repository is readable and restorable (restic check) and rolls health into the fleet view — so you get alerted when a backup stops being trustworthy.
Full throwaway-sandbox restores with row-by-row database verify are on the roadmap. Until then, the engine proof (capture → restore across our own fleet) and integrity drills keep recovery honest.
Push a repo and HostSSH takes it to a live, TLS-terminated URL. HostPack inspects the code and builds a lean OCI image — no Dockerfile, no Nix. Docker runs it as a supervised container with health checks, secret injection and zero-downtime rollouts.
Traefik binds your domain, issues and renews Let's Encrypt certificates, and load-balances traffic. Routes are declarative, so a relocated box re-binds them automatically — the deploy layer and the disaster-recovery layer are the same layer.
Need a target box? Queue one. HostSSH has durable provider drivers for Hostinger, Hetzner, DigitalOcean, Vultr, and AWS-compatible flows, with bring-your-own machines always supported. Unattended production provisioning stays private beta until each selected provider passes a paid live rehearsal.
The queue tracks each provision through to a healthy, reachable server, retries transient provider failures, and surfaces the result in the same fleet view as everything else.
Apps should not hardcode Vast, OpenAI, or a desk GPU IP. HostSSH's AI Gateway accepts sealed keys and model names, then routes to CPU fleet nodes, office hardware, or GPU rentals. Swap supply without changing app code.
Model runtimes deploy as HostSSH Apps (e.g. llama.cpp on CPU). Long media jobs use async job endpoints so edge timeouts don't break renders. Fleet Copilot + MCP operate the box today; gateway + dashboard keys/routes are in product with live completion proof on the path.
HostSSH ships a Model Context Protocol server so an AI agent can operate the fleet in plain language: deploy a service, provision a box, kick off a backup, run a restore-drill, or migrate a server — all through the same authenticated, license-gated actions a human uses.
Because the MCP rides the real control-plane API, agents inherit the same RBAC and audit trail. No shadow path, no extra blast radius.
One click provisions a database engine beside your apps — Postgres with pgvector, MariaDB (MySQL-compatible), or Redis. Credentials are generated and sealed; apps reach them on the internal network.
Postgres is included in the current recovery path. MariaDB and Redis backup adapters, per-database schedules, point-in-time restore, and the signed .hsi pack remain release-gated work.
Named Docker volumes survive redeploys. When you capture, HostSSH snapshots the bytes inside those volumes — uploads, images, video, PDFs, SQLite, WordPress wp-content, MinIO object dirs — binary-safe, not MIME-filtered. Declare --volume name:/path so stateful apps stay in scope.
Background workers use the same HostPack → Docker path as web apps: pass a --command, skip the public proxy, keep Slot caps and sealed secrets. On-demand workers also spin from MCP (hostssh_spin_worker).
Backup storage is yours: point HostSSH at R2, S3, B2, Wasabi, MinIO, SFTP or local disk. Encrypted restic snapshots land in your bucket. The signed portable pack and independently proven expired-license emergency restore remain release gates.
Need app object storage? Deploy the one-click MinIO template beside your apps. Dashboard Connections create/test is still shipping — wire the bucket via CLI today and the control plane will catch up.
Fleet Copilot diagnoses live state and proposes human-gated actions (redeploy, harden, restore). The MCP server lets agents drive the same authenticated control plane.
Hosted inference — llama.cpp, whisper, embeddings, TTS on the fleet plus ComfyUI / LTX-2 / Wan2GP on external GPU — is planned as HostSSH Apps behind an OpenAI-compatible gateway. It ships after the Coolify exit; we won't market model serving until it's real.
Features unlock per tier through ed25519 license tokens the agent verifies locally — so capabilities are enforced even offline, and an expired license never blocks an emergency restore.
The control plane keeps every agent and server in one fleet view — health, backups, deploys and drills — regardless of which provider each box lives on. One pane of glass for a multi-cloud fleet.
The signed public installer mirror is in its final activation gate. Request onboarding for the verified operator path while public live proof is completed.
! Signed installer activation pending · Request onboarding →