# PHP hosting with SSH access

Source: https://www.fortrabbit.com/php-hosting/with-ssh-access
Published: 2026-10-01
Reviewed: 2026-10-01

> SSH and SFTP on every fortrabbit environment, included in each PHP plan from €1 a month. Run artisan, Composer and rsync; no root, no package installs.


fortrabbit is managed PHP hosting with SSH access on every plan. Each environment has its own SSH and SFTP login, authenticated by public key; the smallest PHP plan costs €1 a month and SSH is part of it. The shell runs in the same container as the website, so `php artisan`, `php craft`, `composer install`, `wp` and `mysqldump` work against the live files and the booked MySQL component. rsync moves uploads up and down, and the same SSH connection tunnels a local database client to MySQL. The shell is jailed: no root, no sudo, no package manager. Software beyond PHP, such as Node, FFmpeg or image optimizers, cannot be installed; the operating system and the PHP runtime are patched by fortrabbit. Regions are Ireland and Virginia, and the SSH host name carries the region. Code is deployed with git push; SSH covers the work between deploys, such as a one-off import or a look at the logs.

## What runs over SSH

- Framework and CMS consoles: `php artisan`, `php craft`, `php bin/console`, `wp`. The `php` prefix is required.
- Composer, when a build needs a manual `composer install`. Deploys run it on their own.
- `mysqldump` and `mysql` against the environment's database, and an SSH tunnel for a desktop client.
- rsync and SFTP for uploads, transforms and other runtime data that does not belong in Git. The [SSH and SFTP feature page](/features/ssh-sftp) has the sync patterns.
- Reading logs and deployed files in place.

## What the SSH shell does not do

- Install or remove system packages. No Node toolchain, no FFmpeg, no `apt`.
- Run long-lived processes. Workers and cron jobs run in the [jobs component](https://docs.fortrabbit.com/platform/components/jobs), managed from the dashboard, with their own memory.
- Heavy lifting. The shell shares memory and CPU with the web runtime, so a large import competes with visitors.

## Personal SSH keys

SSH keys are uploaded to a personal account, not to a shared hosting login. Each developer connects with their own key, so onboarding and offboarding means adding or removing a key rather than rotating a password everyone knew. Deploy keys cover services such as GitHub Actions. The [SSH key setup guide](https://docs.fortrabbit.com/dev/learn/ssh-key-setup) walks through generating and uploading a key.

## FAQ

### Is there root access?

**No** — The shell is jailed. Commands run as the environment's own user, with no sudo and no package manager. fortrabbit patches the operating system and the PHP runtime; the developer owns the code on top.

### Can a database client connect over SSH?

**Yes** — The MySQL component is not exposed to the internet. Sequel Ace, TablePlus, MySQL Workbench and the mysql CLI connect through an SSH tunnel to the environment, with the credentials from the dashboard.

### Do SSH logins cost extra?

**No** — SSH and SFTP come with every PHP plan, from the €1 XS plan up. Access is per account, by public key. Every team member brings their own key, and a deploy key can be issued for a CI service.

---

- [SSH and SFTP](/features/ssh-sftp)
- [SSH key authentication](/features/ssh-key-authentication)
- [Code access](/platform/code-access)