SiteShift
HOSTING INTEGRATIONS

Your host, connected once.

SiteShift pushes and pulls over plain SSH, so it works with any host that gives you a shell. For these hosts the app also knows the details — ports, users, webroots, sometimes the whole site list — so linking a site takes minutes instead of a support ticket.

Hostinger · TransIP · SiteGround · Hostnet · DigitalOcean · any SSH host

Hosts SiteShift knows

ANY SSH HOST

No integration needed. SSH is the integration.

Every push and pull is SSH plus SFTP: an archive of the files goes over SFTP, tar unpacks it on the other side, mysqldump and mysql handle the database. If your host gives you a shell with those five tools, SiteShift can deploy to it — no plugin, no agent, no account with us.

The named integrations above only save typing: they know the port, the user, the webroot layout, and for Hostinger, TransIP and DigitalOcean they can list your servers so you pick instead of paste.

See what a push does, step by step

Integration questions

If you can SSH in and the server has tar, mysqldump and mysql, yes. Add it as a manual SSH connection on the site's Sync card and press Test connection.

WP Engine and Flywheel run sandboxed SSH gateways that don't expose everything the sync needs, so they're not supported. Kinsta gives you a normal SSH login, so it works as a manual SSH connection; there's no API integration for it yet.

In SiteShift's encrypted vault on your machine (libsodium, key under ~/.siteshift). They never leave your machine; SiteShift has no cloud component besides licence validation.

The data model already allows it and a connection switcher in the app is on the roadmap. Today you edit the connection to point at a different host — which is exactly how a migration works.

Connect your host once. Pull, work, push.

Get SiteShift — €9/mo