Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

Laravel application hosting

Laravel application hosting in Canada

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

Compare the services for your project.

Your requirements

What does your project need?

01

Runtime and processes

Check Laravel applications that may need PHP extensions, Composer deployments, queues, schedulers, workers, database access, writable storage, and controlled environment secrets.

02

Data to protect

Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.

03

Network access

List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.

04

Deployment and maintenance

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

Running Laravel queues, scheduler, and web together

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.

01

Worker restart policy

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.

02

Scheduler single entry

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.

03

Storage permissions check

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

Access, backups and handover

Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.

Free guide

Laravel application hosting in Canada: planning checklist

Use the detailed checklist to plan setup, access, migration and recovery with your team.

Download PDF →
Help choosing

Tell us about your project.

Send us the software you use, your storage needs and your launch or moving date.

Ask about hosting

We will handle the move. You check it first.

Your 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.

Start my free moveSee plans and prices
See pricesFree move