Runtime and processes
Check Laravel applications that may need PHP extensions, Composer deployments, queues, schedulers, workers, database access, writable storage, and controlled environment secrets.
Laravel application hosting
Plan the PHP version, database, queue workers and scheduled jobs your Laravel application needs. Choose a VPS when it needs server-level services.
Hosting options
Shared hosting for websites, email and PHP applications, with Virtualmin included.
See Web hosting →02Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check Laravel applications that may need PHP extensions, Composer deployments, queues, schedulers, workers, database access, writable storage, and controlled environment secrets.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Field guide
A Laravel deployment has three moving parts that need supervision: the web process through PHP-FPM, the queue workers that handle jobs, and the scheduler that fires the schedule:run command every minute. Size memory by counting FPM children plus queue workers, since each process holds its own copy of the framework.
Run php artisan config:cache and route:cache in production, and keep .env values out of version control. The common failure is a queue worker running old code after a deploy, so configure your supervisor to restart workers on each release and watch the failed_jobs table as part of daily checks.
Set queue workers to restart after a defined number of jobs or on each deploy. Long lived workers accumulate memory and keep stale code and stale configuration.
Add one cron entry that runs schedule:run every minute and let Laravel decide which tasks are due. Multiple cron entries per task drift out of sync with the application.
The web and worker users both need write access to storage and bootstrap/cache. Permission errors here appear as blank pages and silently failed jobs.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.