What PHP Applications Actually Need From a Server
Picking the best hosting for php starts with what your app actually does, not with a feature list. A simple custom PHP site or a small Laravel app needs a current PHP version, the right extensions (mbstring, openssl, curl, zip, gd and the database drivers), a MySQL or MariaDB database, and a way to run scheduled tasks. Composer should be available to install dependencies, and SSH access makes deployments and artisan commands far less painful.
The line that matters most is between request-driven apps and always-on processes. A contact form, a blog or an API that answers web requests runs happily on shared hosting. An app that needs background queue workers, WebSocket servers or scheduled daemons needs a VPS or a platform built for long-running processes. Knowing which side you are on saves you from buying the wrong product.
Hostinger Shared Hosting for PHP: The Stack That Matters
Hostinger’s shared stack covers the request-driven side well. hPanel includes a PHP version selector (Advanced, then PHP Configuration) so each website can run the PHP version it needs, covering the current 8.x versions that Laravel 11 and 12, Symfony and Joomla 6 require (checked 13 Oct 2026). SSH access is available on the higher shared plans, Composer is available over SSH, and cron jobs handle scheduled tasks such as Laravel’s scheduler.
Git deployment is also supported, so you can push code rather than dragging files through FTP. The Unlimited plan adds staging, daily backups, a CDN and Node.js support, which helps when your PHP app ships with a JavaScript-built frontend.
Setting Up Composer, SSH and Cron on hPanel
The practical workflow looks like this. First, set the PHP version for your domain in hPanel’s PHP Configuration and create the MySQL database. Then connect over SSH, where Composer is available, and run composer install with the production flags to pull in your dependencies. Point the domain’s document root at the public directory (for Laravel), and keep the .env file outside the web-accessible path.
For scheduled work, add a cron job that calls Laravel’s scheduler every minute, or your framework’s equivalent. This pattern covers queues on small apps too: use the database queue driver and let the scheduler dispatch jobs, which works fine at low volume. It is not a true worker daemon, but it is the standard shared-hosting compromise.
The Honest Ceiling: Queue Workers and Long-Running Processes
Here is the line shared hosting cannot cross: you cannot run persistent background processes. There is no way to keep a Laravel queue worker, a Horizon supervisor or a WebSocket server alive on shared hosting, because the platform kills long-running processes. For low-traffic apps the cron-driven scheduler is enough; for real queue volume, email digests or image pipelines, it is not.
Debugging gets harder too: you cannot install custom PHP extensions, tune PHP-FPM pools or inspect server logs the way you can with root access. Shared hosting is a managed apartment; a VPS is your own house. If your app has outgrown the apartment, the Hostinger KVM VPS gives you full root from KVM 1 upward for workers and supervisors.
Best Hosting for PHP When Shared Is Not Enough
If cron-driven queues are holding your app back, you have two honest upgrades. A Hostinger KVM VPS gives you root access for queue workers under Supervisor, Redis and full stack tuning, but you also own security and updates. It is the right call if you are comfortable with Linux.
The other path is a PHP-focused platform as a service. fortrabbit is a managed PHP platform running since 2012 that deploys via git push, runs Composer during the build, and supports Laravel, Symfony, Craft CMS and plain PHP, with SSH access and managed MySQL (checked 13 Oct 2026). Laravel's own Laravel Cloud hosts Laravel and Symfony apps from a small monthly base. Both cost more than shared but remove server management.
Renewal Reality: Budgeting Beyond the Introductory Price
The pattern is the same as with any budget host: a low first term, then a renewal several times higher. Industry reporting put Hostinger's renewal multiple at roughly 3.3 to 4.3 times the intro rate in 2026, so a PHP project planned for years should be budgeted at the renewal figure from day one. The 30-day money-back guarantee covers you if the stack does not suit your app.
Compare honestly: a VPS renews at steadier prices but adds your time as a cost, while a PHP platform bills monthly at a higher base. For a side project or client site, shared hosting renewed at a higher rate can still be cheapest; for a growing SaaS, the VPS or platform usually wins once your time is counted. See how Hostinger renewals work.
Who Should Choose Hostinger for PHP (and Who Should Not)
Hostinger shared is a strong fit for: custom PHP sites and small business apps, Laravel or Symfony projects in development or with modest traffic, agencies hosting several small client sites on Unlimited, and anyone wanting PHP 8.x, Composer and cron without managing a server. It is also a cheap staging ground: build on shared, move to a VPS when the app earns it.
Do not choose it when: your app needs persistent queue workers or WebSocket servers (take the VPS or a PHP platform), you need custom PHP extensions or server-level tuning, or your team wants git-push deploys with zero server care (fortrabbit or Laravel Cloud fit better). If your PHP app is really a content site in disguise, check our Laravel hosting guide.
| Feature | Hostinger Unlimited (shared) | Hostinger VPS KVM 2 | fortrabbit (PHP platform) |
|---|---|---|---|
| PHP versions | Per-site selector, current 8.x | Any version you install | Current PHP, per app |
| Composer | Available over SSH | Full control via SSH | Runs in git-push build |
| Background processes | Not allowed on shared | Full control, root access | Managed, no server admin |
| Root access | No | Yes, full root | No, managed platform |
| Scaling | Fixed plan resources | Upgrade the VPS anytime | Per-component scaling |
| Backups | Daily | Snapshots, paid backups optional | Backups included |
| Best for | Small PHP apps on a budget | Apps needing workers and root | PHP apps, zero server care |
VPS KVM 2
24-month plan, paid upfront
Renews at $14.99/mo
- 2 vCPU + 8 GB RAM
- 100 GB NVMe storage
- 8 TB bandwidth
- Full root access
- n8n one-click template available
FAQ
Yes, for typical Laravel apps. Set PHP 8.2 or newer in hPanel, create the MySQL database, install dependencies with Composer over SSH, and point the document root at the public folder. Use the cron-driven scheduler and the database queue driver for light background work; persistent workers need a VPS (checked 13 Oct 2026).
hPanel lets you choose the PHP version per website through Advanced, covering the current PHP 8.x line including 8.3 and 8.4 (checked 13 Oct 2026). That covers Laravel 11 and 12, Symfony 7 and modern custom PHP code. You can also toggle PHP extensions per site, which helps legacy apps.
SSH access is available on the higher shared plans, and Composer runs over that SSH connection. If you prefer the command line less, run composer install locally and upload the vendor folder, though SSH is the standard route. Cron jobs for scheduled tasks are available in hPanel on all shared plans.
No. Shared hosting forbids persistent background processes, so a Laravel queue worker or Horizon supervisor cannot stay running. The workaround is the cron-driven scheduler with the database queue driver, which suits low-volume jobs. Once queues matter, move to a KVM VPS with Supervisor, or to a managed PHP platform.
Move when you need what shared hosting forbids: persistent queue workers, WebSocket servers, custom PHP extensions, or server-level tuning. Consistent high traffic straining shared CPU limits is another signal, as is already needing your own server for compliance or isolation.
Shared hosting wins on sticker price but renews several times higher, so budget at the renewal rate. A VPS costs more monthly with steadier pricing, plus your time for management. A PHP platform like fortrabbit or Laravel Cloud bills monthly with no intro discount but removes server work. Count your hours before deciding.