Hosting for code crafters

No - The application is a standard PHP project. Deployment runs Composer and the build commands declared in the repository; there is no vendor SDK, no lock-in wrapper, and nothing to import. Moving the code elsewhere means pointing another host at the same Git repository.

Yes, over SSH - Every environment is reachable over SSH and SFTP with key authentication. Logs from PHP, Apache, and jobs can be tailed live, so a failing request is read at the source rather than guessed at from a dashboard summary.

All of it - Build commands run on every deploy — Composer install, asset compilation, migrations, cache warming. They are declared per environment and versioned with the code, so the build that runs in production is the one in the repository.

No - Every environment maps to a Git branch; pushing it runs Composer through the fortrabbit GitHub app and swaps the release. Hand-written or agent-written, the commit ships the same way — what differs is who authored it.

Pro-rated by the day - Every app starts on a seven-day free trial, no card required. After that, only the booked components are billed — PHP, storage, traffic, and MySQL when needed — pro-rated by the day and post-paid, so a plan change or a deleted environment settles the same day rather than the next month.

Anything Composer-based - Laravel, Symfony, Craft CMS, Statamic, and plain PHP all run the same way: a Composer project deployed with git push. There is no curated list to fit into — if it builds with Composer and speaks PHP, it belongs here.