Laravel hosting built for how you ship

Yes. A full SSH shell comes with every plan, so deploying uses the same Git-based routine you already run locally. Clone the repository straight out of GitHub, GitLab or Bitbucket into your account, run composer install for the vendor packages, then drop your production values into .env. Artisan handles the rest: php artisan key:generate sets the app key, php artisan migrate builds the schema. Later releases go out just as fast as the first. Fetch the new commits with git pull, update dependencies with composer install, run php artisan migrate for any fresh migrations, then refresh the cache to clear the stale config. Having a genuine shell instead of a locked-down panel means you can tail logs, fix storage permissions and re-run any command that needs a second look. Point the document root at the public folder and the site answers over HTTPS.

Yes. Composer is installed on every account and already on your PATH, which means nothing to download, unpack or configure before the first deploy. From the moment the account is provisioned, an SSH session gives you composer install, composer update, composer require and composer dump-autoload, all running against the right PHP binary. For Laravel that matters, because the framework and very nearly every package you bolt on, from the starter kits through to Sanctum and Horizon, arrive through Composer rather than sitting committed in your repository. Your composer.json and composer.lock stay yours, so the versions you tested at home are the versions that land on the server. Need Composer to run under one specific PHP release? You can, since the PHP version is selectable per site. Put plainly, the dependency workflow behaves the way it does on your own machine, start to finish.

Modern PHP 8.x is what you get, and the control panel lets you pick which release each site runs. That flexibility earns its place, because every Laravel version names a minimum PHP requirement: recent releases want PHP 8.1 or newer, while an older long-term-support app might be pinned to an earlier 8.x build. Nobody is forced onto one runtime for everything. Set the version per domain and a legacy client project can share an account with a brand-new app, no conflict. Next to the selector sit the settings Laravel actually cares about: memory_limit for heavier Artisan commands and imports, max_execution_time for tasks that run long, OPcache to keep compiled code hot in memory. Switching is instant, and reversible, which takes the risk out of testing a PHP upgrade. Flip a staging domain up first, watch the test suite pass, then move production across with one click.

Both are properly supported. Queued work starts with a persistent worker, php artisan queue:work, so jobs, notifications, mailables and heavy exports run off the web request rather than holding up somebody's page load. Back that queue with Redis and jobs get picked up and drained quickly even when traffic is real. Scheduled work needs no long list of separate cron lines. Register everything inside Laravel's scheduler in your application code, then add a single cron entry running php artisan schedule:run every minute. From that one task Laravel works out what is due and fires it: hourly digests, nightly clean-ups, weekly reports, whatever you have defined. After each deploy, run php artisan queue:restart so the workers pick up your new code. It is the standard Laravel arrangement, behaving exactly as the documentation says, with no platform-specific workarounds to learn.

Yes. Redis is there for caching, session storage and queues, which is the trio most production Laravel apps end up using. Aim the cache driver at Redis and expensive query results, rendered fragments and computed values come from memory rather than being rebuilt on every hit. Shift sessions onto Redis and logged-in state stays quick and consistent as traffic climbs. Set the queue connection to Redis and background jobs are enqueued and processed with barely any overhead, keeping workers responsive through a spike. All of that gets wired up in your .env using the standard cache, session and queue driver settings, and nothing bespoke is needed at our end. Since Redis holds the working set in RAM instead of on disk, pages that used to feel heavy get noticeably snappier, and background processing keeps pace rather than stacking up into a backlog when a burst of traffic lands.

Yes, and it is the right way to serve a Laravel app. Laravel keeps one entry point in its public directory and holds the application code, .env and storage above the web root, so nothing sensitive is reachable from a browser. In the control panel you set the domain's document root to your project's public folder, and requests then flow through index.php exactly as the framework intends. Pair that with free auto-renewing SSL and the app answers over HTTPS with clean, pretty URLs and no index.php cluttering the address bar. Permissions on storage and bootstrap/cache are simple enough to set over SSH, so caching, sessions and uploads work first time. Running several apps on one account? Each domain gets its own document root aimed at its own public folder, which keeps projects separate while they share the same fast NVMe server underneath.

Yes. Our team transfers your codebase, exports and imports your MySQL database, and carries over your storage folder so uploaded files and cached data aren't left behind. We bring everything up on a temporary address first so you can confirm queues, the scheduler and Redis-backed sessions all still work, and only then do we walk through the DNS cutover.

Yes, daily backups cover your database and storage directory, giving you a restore point that sits alongside your own Git-based code rollbacks. If a migration or seed command goes wrong, you can restore the previous day's snapshot rather than trying to reverse the damage by hand.

Yes. Addon domains let you point a staging subdomain and your live domain at the same account, each with its own document root and database. Push and test on staging first, run your Artisan migrations there, and only promote to the production domain once you're confident.

Higher tiers support up to 100 MySQL databases, which in practice means room for several Laravel projects — a mix of client sites, side projects and staging copies — on a single account, each with its own domain, database and .env.

Every plan is covered by a 30-day money-back guarantee, so you can deploy your actual project, run it under real traffic, and check queue throughput and Redis caching behave the way you expect before committing beyond the trial period.

Plans are priced in USD starting at $2.42/mo, and geo-currency detection displays that price converted into your local currency at checkout, so what you see is what gets billed rather than a rate you have to calculate yourself. Billing itself runs through Bohzo Ltd (UK).