01
Composer and Artisan
Business, Pro, and VPS paths include SSH so the deployment can install dependencies and run framework commands.
Two Laravel hosting paths
Laravel hosting
Use Business or Pro shared hosting for a straightforward PHP and MySQL application. Choose an unmanaged VPS when Laravel needs persistent workers, Redis, Octane, or custom server services.
Bitfoo opens for orders soon.
- Shared path
- Business or Pro
- VPS path
- Full root
- Runtime
- PHP 8.x
- Storage
- NVMe SSD
SSH access included
Unmanaged server
Compatibility still needs checking
Across both product lines
Choose by responsibility
Shared hosting or VPS?
Choose from what the application must keep running—not from the framework name alone.
Managed hosting platform
Choose Business or Pro shared hosting
Use the supported PHP, MySQL, cron, and SSH workflow without operating Linux.
- No persistent background workers
- No Redis or Octane requirement
- Composer, Artisan, cron, and MySQL cover the deployment
Custom server environment
Choose an unmanaged VPS
Operate the full Laravel stack when the application depends on persistent services.
- Queue workers or Horizon must stay running
- Redis, Octane, or custom extensions are required
- Your team can administer and monitor the server
Production foundation
Build the deployment around Laravel’s processes
The web request, scheduler, queue, cache, database, and release workflow may each need a different operating pattern.
02
Scheduler
Configure Laravel’s scheduler through hosting cron or the VPS system crontab, then monitor whether scheduled work completes.
03
Queue workers
Continuously running workers need supervision and a VPS; they also need deliberate restart behavior during deployments.
04
Environment and storage
Protect the application key and secrets, expose only the public directory, and make writable storage and backups explicit.
Plan comparison
Compare the two Laravel paths
Shared hosting minimizes server operations. VPS adds persistent services and full control, along with full server responsibility.
Managed shared hosting
Swipe horizontally to compare every plan.
| Specification | Business A straightforward production Laravel application Recommended starting point | Pro More capacity or several Laravel applications |
|---|---|---|
| Storage | 50GB NVMe SSD | 150GB NVMe SSD |
| RAM | 1GB | 2GB |
| Bandwidth | Unmetered | Unmetered |
| Sites | 10 | Unlimited |
| Backups | Daily | Daily |
| SSH access | Yes | Yes |
| Price | Coming soon | Coming soon |
| Availability | Join waitlist → | Join waitlist → |
Exact prices will appear when ordering opens. Shared hosting includes platform management; application maintenance remains with you.
Unmanaged KVM VPS
Swipe horizontally to compare every plan.
| Specification | VPS-1 Development, staging, or a light application | VPS-2 Production with queues and Redis Recommended starting point | VPS-4 More workers, Horizon, or higher traffic | VPS-8 Larger Octane or multi-application workloads |
|---|---|---|---|---|
| vCPU | 1 | 2 | 4 | 6 |
| RAM | 1GB DDR5 | 2GB DDR5 | 4GB DDR5 | 8GB DDR5 |
| Storage | 25GB NVMe | 50GB NVMe | 100GB NVMe | 200GB NVMe |
| Bandwidth | 1TB | 2TB | 4TB | 6TB |
| IPv4 | 1 | 1 | 1 | 1 |
| Price | Coming soon | Coming soon | Coming soon | Coming soon |
| Availability | Join waitlist → | Join waitlist → | Join waitlist → | Join waitlist → |
Exact prices will appear when ordering opens. VPS plans are unmanaged and do not include an automated backup service.
Before deployment
Define every long-running process
The correct product becomes clearer once each process and dependency has an owner.
- 01
List runtime dependencies
Confirm the PHP version, extensions, Composer packages, database, cache, and system packages the release requires.
- 02
Classify background work
Separate scheduled tasks from continuously running queue workers and choose hosting that can support each pattern.
- 03
Coordinate deployments
Put maintenance mode, migrations, cache clearing, worker restarts, and rollback in a documented order.
- 04
Protect and restore state
Back up the database and user files, protect the application key and secrets, and test a restore.
Related hosting guidance
Common questions
Can Laravel run on shared hosting?
Yes, on Business or Pro when the application fits the supported PHP, MySQL, SSH, and cron workflow and does not require persistent background services.
Why is Starter excluded?
Laravel deployment normally depends on SSH for Composer and Artisan. Starter does not include SSH access, so this page does not present it as a Laravel plan.
When does Laravel require a VPS?
Use VPS when queue workers must remain running, Redis or Octane is required, custom system packages are needed, or the application has moved beyond the shared environment.
Does Bitfoo manage Laravel on VPS?
No. The VPS is unmanaged. Your team operates Linux, PHP, the web server, workers, Redis, deployments, monitoring, security, and backups.