Skip to content
Mail Cabinet Choose a plan

Laravel Hosting: PHP 8.3, SSH, Cron and MariaDB from $8 a Month

Laravel Hosting: PHP 8.3, SSH, Cron and MariaDB from $8 a Month

Laravel hosting on a shared plan works when the account gives you a current PHP, a database, SSH and cron, and RichHost plans do. A Laravel application can be installed on any plan from $8 a month, with PHP 7.4 to 8.3 and switching between them, SSH access, MariaDB 10.11 and NVMe disks, and the current Laravel 13 supports PHP 8.3. Below: what a plan includes, the official Laravel requirements, how to deploy, and what to know about queues before you start.

What you get at RichHost

  • Plans: from A3 at $8 a month to A50 at $65, with 10% off for yearly payment.
  • PHP: versions 7.4 to 8.3 with switching and memory_limit 512 MB on every plan. Laravel 13 supports PHP 8.3 to 8.5, so choose 8.3; older applications can stay on the branch they were built for. See PHP version on hosting.
  • SSH on every plan (enabled on request): for Artisan commands, Composer and file work. Signing in with a key instead of a password is covered in the guide to SSH keys.
  • Databases and files: MariaDB 10.11 databases (MySQL compatible) created in the control panel, Redis, NVMe disks, unlimited websites, FTP accounts and mailboxes, unlimited traffic.
  • Security: free Let’s Encrypt SSL, basic DDoS protection on L3-L7 and continuous cloud backups.
  • Management and terms: our own control panel with an AI assistant, data centers in Helsinki, Warsaw, Paris and the USA, a trial period and a 14-day money-back guarantee.

One-click installation at RichHost is confirmed for WordPress only. A Laravel project is deployed by hand, which is how Laravel developers work anyway.

Laravel server requirements

The list is from the deployment page of the official Laravel 13 documentation and from its release notes and support policy, checked on 15 November 2026.

Component What Laravel 13 asks for At RichHost
PHP 8.3 or later (the support policy lists PHP 8.3 to 8.5) PHP 7.4 to 8.3 with switching: 8.3 fits
PHP extensions Ctype, cURL, DOM, Fileinfo, Filter, Hash, Mbstring, OpenSSL, PCRE, PDO, Session, Tokenizer, XML Check with php -m over SSH; ask support if one is missing
Web root The web server must serve the public directory; index.php must never be moved to the project root The document root can be changed to /public in the control panel, with a ready template for Laravel
Database First party support for MariaDB 10.3 or later and MySQL 5.7 or later MariaDB 10.11
Writable folders storage and bootstrap/cache Set over SSH or SFTP
Scheduler One cron entry that runs schedule:run every minute Cron jobs are added in the control panel, as often as once a minute
Queue workers Long-lived processes kept alive by a process monitor such as Supervisor Not available: no permanent background processes; queues run from cron every minute, see the section on queues

The first four rows are ordinary shared hosting work; the last two are where a Laravel project has to be honest about what it needs. Older applications on Laravel 10, 11 or 12 run on the PHP branch they were written for: switch the version in the panel.

How to deploy Laravel on hosting

  1. Add the domain in the control panel, issue the free SSL certificate and switch PHP to 8.3.
  2. Create a database and a user for it.
  3. Connect via SSH and upload the code over SFTP, or pull it with Git if the client is present on the server. Install the PHP dependencies with Composer, which is available once SSH access is enabled on your account.
  4. Point the site to the public directory: change the document root to /public in the control panel or apply the ready Laravel template. Do not copy index.php into the root as old tutorials suggest: the documentation warns that serving the project root exposes configuration files.
  5. Create .env with the application key, the database details and APP_DEBUG=false, then run php artisan migrate.
  6. Run php artisan optimize to cache configuration, routes and views. After config:cache the .env file is no longer read at runtime, so re-run the command after every change.
  7. Add the scheduler to cron with a job that runs every minute, as described in cron jobs on hosting.

The scheduler entry from the documentation:

* * * * * cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1

Front end assets built with Vite need Node.js at build time only. Node.js is possible on our hosting, but we do not publish versions or limits, so the dependable route is to build the assets locally or in your CI and upload the result.

Queues, workers and other limits

Laravel’s documentation describes queue:work as a long-lived process and says production needs a process monitor that restarts it. Permanent background processes are not available on our shared plans: no Supervisor and no long running workers. Queues still work through cron:

  • The sync driver runs jobs immediately inside the request, which is fine for light tasks.
  • The database driver stores jobs in your MariaDB database, and the documented --stop-when-empty option of queue:work makes a worker process the waiting jobs and exit, so it can be started from the scheduler instead of running forever. This is the setup for our plans: a cron job runs php artisan schedule:run every minute, and the scheduler starts php artisan queue:work --stop-when-empty.
  • Redis is available, so it can serve as the cache or queue backend; the file and database cache drivers need nothing extra, and our article on hosting cache with Redis, Memcached and OPcache explains the layers.
Project What to do
Company site, admin panel, API or small SaaS on Laravel A shared plan fits; start with A5 or A10
Several Laravel sites or a busier application A20 or A30; plan resources are shared by all sites on the account
WebSockets with Reverb, Octane, permanent queue workers A server of your own; RichHost does not sell VPS or dedicated servers

If you are unsure which side of that line your project is on, use the trial period: the hosting free trial page explains how it is activated.

How to order

Choose a plan on the RichHost hosting plans page, add the domain in the control panel and deploy with the steps above. An existing project can be moved by our support as part of free website migration.

Laravel hosting FAQ

Can Laravel run on shared hosting?

Yes. It needs PHP 8.3 or later with a standard set of extensions, a database, the public directory as the web root and one cron entry. Permanent workers and WebSocket servers are the exception.

Which PHP version does Laravel need?

Laravel 13 requires PHP 8.3 or later according to the official documentation, and its support policy lists PHP 8.3 to 8.5. RichHost offers PHP 7.4 to 8.3 with switching, so Laravel 13 runs on our PHP 8.3.

Is Composer available?

Yes. Composer is available once SSH access is enabled on your account; SSH is part of every plan and is turned on at your request.

Can I run the Laravel scheduler?

Yes, with a cron job. The documentation asks for one entry that runs every minute, and at RichHost cron can run as often as once a minute.

More on this topic

All articles
PHP Hosting with MySQL: PHP 7.4 to 8.3, SSH and NVMe from $8
Hosting Types15.11.2026

PHP Hosting with MySQL: PHP 7.4 to 8.3, SSH and NVMe from $8

PHP and MySQL hosting at RichHost: PHP 7.4 to 8.3 with switching, MariaDB 10.11 (MySQL compatible), SSH and NVMe from $8 a…

Nextcloud Hosting: Your Own Cloud on NVMe with SSH from $8 a Month
Hosting Types15.11.2026

Nextcloud Hosting: Your Own Cloud on NVMe with SSH from $8 a Month

Nextcloud hosting at RichHost: what the plans include, the official Nextcloud server requirements, manual installation and honest limits. From $8 a month.

Moodle Hosting: PHP 8.3, MariaDB, Cron and SSH from $8 a Month
Hosting Types15.11.2026

Moodle Hosting: PHP 8.3, MariaDB, Cron and SSH from $8 a Month

Moodle hosting at RichHost: what the plans include, the official Moodle 5.3 server requirements, manual installation, cron and honest limits. From $8…