Why check developer access before buying
A developer's workflow usually assumes four things: shell access to run WP-CLI, a way to deploy code from Git, file transfer for large media, and the ability to schedule jobs. Managed hosts restrict some of these to keep the platform stable. Finding out after the move means a developer billing hours to rebuild their deploy pipeline.
For course sites, the common jobs are search-replace after a migration, bulk user imports, database exports too large for a browser, and cron setup. All of them are easiest with SSH and WP-CLI. Deploying a custom child theme or LMS add-on needs Git or at least SFTP.
Access table
Each cell comes from the host's own documentation or plan comparison. "Not stated" means the pages reviewed do not say.
| Host | SSH | WP-CLI | Git | SFTP | Root | Plan restrictions |
|---|---|---|---|---|---|---|
| Kinsta | All Managed WordPress plans; password or key; unique port per environment; optional IP allowlist | Installed on all sites | Git client available over SSH; no git push deploy; third-party deploy tools suggested | SFTP only, no plain FTP; extra SFTP users with read-only or folder limits, but they get no SSH | Not stated | npm only on Single 1.25M and higher or WP 60 and higher |
| WP Engine | SSH Gateway for users with environment access; 10-minute sidecar timeout; 5 connections per user | Yes, via SSH Gateway | GitPush (one-way, SSH clones only, some file types disallowed) or GitHub Action deploy over SSH Gateway | Separate SFTP at environment.sftp.wpengine.com on port 2222; one environment per credential | No root or sudo | Not stated on the pages reviewed |
| SiteGround | All shared and Cloud plans; key-based authentication; port 18765 | Included on all plans | Git over SSH for all; SG-Git Site Tools interface on GoGeek and higher | Available on all hosting solutions | Not covered on the page reviewed | SG-Git: GoGeek and higher; Staging + Git listed on GoGeek |
| Nexcess Managed WordPress (listed in Liquid Web's site header) | Per-site SSH users created with team members; password and keys | Not stated on the page reviewed | Not stated on the page reviewed | Not stated on the page reviewed | Team members cannot log in as the main site user | Not stated |
| Liquid Web managed VPS | Root access listed on every plan | Install yourself | Install yourself | Not stated; root access allows it | Yes | None stated |
| KnownHost WordPress hosting | Full SSH listed on all three plans | Listed on all three plans | Listed on all three plans | SFTP and FTPS listed on all three plans | Not stated | None stated |
| KnownHost managed VPS | Full SSH access on all plans | Install yourself | Install yourself | Not stated; root access allows it | Full root access on all plans | None stated |
| DigitalOcean Droplet (WordPress 1-Click) | Root SSH with your key; port 22 open | Installed in the 1-Click image | Install yourself on Ubuntu 24.04 | Not stated; root access allows it | Yes | None |
Host details that trip developers
WP Engine's SSH Gateway is not a full shell on the web server. Sessions time out after 10 minutes, new files can only be created under the site's directory, and scp on newer OpenSSH clients needs the -O flag to use the original protocol the gateway supports. Long-running imports belong in a background process or a WP-CLI command that finishes within the session. SFTP is a separate service on port 2222 with its own credentials.
Kinsta's Git page says plainly that it does not offer git push kinsta to deploy. The documented approach is a deploy script that SSHes in and pulls from GitHub, GitLab or Bitbucket, or a third-party service. Additional SFTP users are useful for contractors because they cannot open a shell.
SiteGround uses key-based SSH authentication instead of a plain username and password; developers generate or add a key in Site Tools > Devs > SSH Keys Manager and connect on port 18765 instead of 22. Git itself works over SSH on all plans; only the point-and-click SG-Git tool needs GoGeek.
On root-access servers (KnownHost and Liquid Web managed VPS, DigitalOcean Droplets), developers can install whatever they want. The trade-off is that the WordPress-specific conveniences, such as one-click staging, platform cron and Git integrations, are yours to build. DigitalOcean's 1-Click image gives a head start with WP-CLI preinstalled.
Matching a workflow to a host
Use the workflow your developer already has as the filter, not the other way round.
| Workflow | Works without changes | Needs adjustment |
|---|---|---|
| GitHub Actions deploy on merge | WP Engine (GitHub Action over SSH Gateway); root servers | Kinsta (write a deploy script that SSHes in and pulls); SiteGround (deploy over SSH with a key) |
| git push to a host remote | WP Engine GitPush; root servers with a bare repo | Kinsta (no push-to-deploy) |
| Long WP-CLI imports (tens of minutes) | Kinsta and SiteGround (no session timeout stated on the pages reviewed); root servers | WP Engine (10-minute gateway timeout; split the job) |
| Password-based SSH for a non-technical admin | Kinsta (password login can be enabled per environment); Nexcess Managed WordPress (per-user SSH passwords) | SiteGround (keys only) |
| Contractor file access without a shell | Kinsta additional SFTP users; WP Engine SFTP users per environment | Root servers (create a restricted user yourself) |
| Custom system packages or daemons | KnownHost and Liquid Web managed VPS, DigitalOcean | All managed WordPress hosts |
Questions to ask before you sign
If a plan page is silent on any of these, ask support in writing and keep the answer with your migration notes.
- Is SSH included on the exact plan and environment (production and staging) you will buy?
- Password, key or both? Which port?
- Is there a session timeout or connection limit?
- Is WP-CLI installed, and which version?
- How is Git deployment supported: push remote, CI action, or pull over SSH?
- Can you add restricted SFTP users for contractors?
- Can you add your own cron jobs, and at what minimum interval?
Questions before you decide
Does Kinsta support git push deployment?
No. Kinsta says it does not yet offer git push to deploy. Git is available over SSH, so you can pull from a hosted repository or use a deployment script or a third-party tool such as WP Pusher, Beanstalk or DeployHQ.
Why does my WP Engine SSH session disconnect?
WP Engine's SSH Gateway runs as a sidecar with a 10-minute timeout, and each user is limited to 5 connections. Split long jobs or run them so they finish within the session.
What port does SiteGround use for SSH?
SiteGround uses port 18765 instead of 22 and requires key-based authentication. Keys are managed in Site Tools under Devs > SSH Keys Manager.
Do I get root access on DigitalOcean?
Yes. The WordPress 1-Click Droplet is set up for SSH as root with your key, with port 22 open and WP-CLI preinstalled on Ubuntu 24.04.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Kinsta docs: connect to SSH Accessed 30 Oct 2026
- Kinsta docs: connecting with SFTP Accessed 30 Oct 2026
- Kinsta docs: Git Accessed 30 Oct 2026
- WP Engine: SSH Gateway Accessed 30 Oct 2026
- WP Engine: SFTP Accessed 30 Oct 2026
- WP Engine: Git version control (GitPush) Accessed 30 Oct 2026
- WP Engine: GitHub Action deploy Accessed 30 Oct 2026
- SiteGround KB: SSH access availability Accessed 30 Oct 2026
- SiteGround KB: log in via SSH on Linux Accessed 30 Oct 2026
- SiteGround KB: is SFTP access available Accessed 30 Oct 2026
- SiteGround KB: what is SG-Git Accessed 30 Oct 2026
- SiteGround: web hosting plans Accessed 30 Oct 2026
- Nexcess documentation (Liquid Web): SSH users Accessed 30 Oct 2026
- Liquid Web: managed VPS hosting Accessed 30 Oct 2026
- KnownHost: compare WordPress hosting plans Accessed 30 Oct 2026
- KnownHost: compare managed VPS plans Accessed 30 Oct 2026
- DigitalOcean docs: WordPress 1-Click App Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.