Laravel VPS
- Prices include VAT
- From $11.43/month
- FrankenPHP and Octane preinstalled
- Caddy with WAF and automatic HTTPS
Laravel VPS plans
STARTER
Suitable for a first application, a test environment, and small websites
$11.43/month
- CPU cores2
- Dedicated RAM2GB ECC
- Disk space50GB
- TrafficUnlimited
- IP address1
- FrankenPHP, Octane, and Caddy: Installed and configured
- Snapshot backup: One per month
- BASIC management: Included
- Setup fee: Free
- Server location: Israel
BASIC
RecommendedSuitable for most applications, such as a Laravel website or an API service with a database
$28.57/month
- CPU cores2
- Dedicated RAM4GB ECC
- Disk space100GB
- TrafficUnlimited
- IP address1
- FrankenPHP, Octane, and Caddy: Installed and configured
- Snapshot backup: One per month
- BASIC management: Included
- Setup fee: Free
- Server location: Israel
PRO
Suitable for an application with a database, Redis, and queues running on the same server
$57.14/month
- CPU cores3
- Dedicated RAM8GB ECC
- Disk space200GB
- TrafficUnlimited
- IP address1
- FrankenPHP, Octane, and Caddy: Installed and configured
- Snapshot backup: One per month
- BASIC management: Included
- Setup fee: Free
- Server location: Israel
BUSINESS
Suitable for SaaS platforms and production environments with many users and a steady load
$114.29/month
- CPU cores4
- Dedicated RAM12GB ECC
- Disk space250GB
- TrafficUnlimited
- IP address1
- FrankenPHP, Octane, and Caddy: Installed and configured
- Snapshot backup: One per month
- BASIC management: Included
- Setup fee: Free
- Server location: Israel
ENTERPRISE
Suitable for heavy loads, with many worker processes and queues running in parallel
$142.86/month
- CPU cores8
- Dedicated RAM16GB ECC
- Disk space300GB
- TrafficUnlimited
- IP address1
- FrankenPHP, Octane, and Caddy: Installed and configured
- Snapshot backup: One per month
- BASIC management: Included
- Setup fee: Free
- Server location: Israel
PREMIUM
Suitable for memory-intensive applications, such as large databases and in-memory caching
$257.14/month
- CPU cores8
- Dedicated RAM32GB ECC
- Disk space400GB
- TrafficUnlimited
- IP address1
- FrankenPHP, Octane, and Caddy: Installed and configured
- Snapshot backup: One per month
- BASIC management: Included
- Setup fee: Free
- Server location: Israel
Included in every plan
- FrankenPHP and Laravel Octane - installed and configured
- Caddy with WAF - installed and configured
- SSL certificate - issued and renewed automatically
- PHP, Composer, Redis, Supervisor and Node.js - installed
- Personal support via HelpDesk
- BASIC management - included
- Full root access over SSH
- Traffic - unlimited
- Snapshot backup - one per month
- Firewall - preconfigured
- Migration from another provider - free
- AI service connections - supported
Tip from our team
As a leader in cloud services, we have learned over the years that it is always best to start with a small plan rather than ordering the largest plan right away, even for a large business.
Our VPS plans are built to grow with your business: at any stage, you can add CPU cores, memory, and disk space as your needs change. Every plan comes with no commitment beyond the current month of service, no fine print and no cancellation fees.
Not sure which plan to choose? Talk to us, and we will build a plan tailored to your business needs.
What is installed on your Laravel server
The server comes ready to work: FrankenPHP, Laravel Octane, and Caddy with a WAF module are preinstalled and configured, along with PHP, Composer, Redis, Supervisor, and Node.js. The components below show how the server is built, from your application down to the infrastructure, and each component is marked as yours or maintained by us.
Yours
- Your application, packages, and dataYou develop your Laravel application, install the packages it needs with Composer, configure the .env file, and manage the database and the files your users upload.
- FrankenPHP and Laravel OctaneFrankenPHP, a modern application server for PHP, runs Laravel through Octane in worker mode: the code loads once and stays in memory, so the application is not bootstrapped again on every request, and responses are faster. FrankenPHP and Octane are installed and configured when the server is set up, and from then on they are fully under your control.
- Caddy with WAF and automatic HTTPSCaddy, built with xcaddy with a WAF module, receives requests over HTTP/2 and HTTP/3, filters malicious requests before they reach your application, and automatically issues and renews the SSL certificate for your domain. Caddy is installed and configured when the server is set up, and from then on it is fully under your control.
- PHP, Composer, and Node.jsPHP and Composer, for installing your application's dependencies, and Node.js, for building your CSS and JavaScript files with Vite, are installed and configured when the server is set up, and from then on they are fully under your control.
- Redis, Supervisor, and the schedulerRedis is used for caching, sessions, and queues, Supervisor keeps the queue background processes running continuously, and cron runs the Laravel scheduler. These components are installed and configured when the server is set up, and from then on they are fully under your control.
Looked after by us
- Operating systemWhen you order, you choose from a range of Linux distributions, including AlmaLinux, Rocky Linux, Ubuntu, and Debian. We install the operating system updates, and you get full root access over SSH.
- Virtual server with guaranteed resourcesThe CPU cores and ECC memory are guaranteed to your server alone, and its disk space is allocated on high-speed storage.
- Infrastructure, network, and backupThe server runs on infrastructure with dual power supplies, gets a dedicated IPv4 address, and DDoS protection helps protect it. A Snapshot backup is created for it automatically at the start of every month.
From your order to your first application
We set up the server and install FrankenPHP, Laravel Octane, and Caddy with a WAF module on it, so you go straight from choosing a plan to deploying your application, with no runtime environment to install and no server configuration.
-
Choose a plan, an operating system, and a domain
Choose the plan that fits your application and the operating system from a range of Linux distributions, including AlmaLinux, Rocky Linux, Ubuntu, and Debian. You also decide which domain or subdomain your application will run on.
-
The server is set up with FrankenPHP, Octane, and Caddy
Once your order is confirmed, our team sets up the server and installs FrankenPHP, Laravel Octane, and Caddy with a WAF module on it, along with PHP, Composer, Redis, and Node.js. Once your domain's DNS record points to the server, Caddy issues an SSL certificate for it automatically.
-
Connect to the server over SSH
When setup is complete, you receive your access details and can connect to the server over SSH with full root access.
-
Deploy your Laravel application
Pull your code from a Git repository, install the dependencies with Composer, configure the .env file, build your CSS and JavaScript files with Vite, and run the migrations. Finally, reload the Octane worker processes so they run the new version of your application.
What you can run on your own Laravel server
Laravel is used to build web applications, API services, and management systems. On your own server, your application runs in Octane worker mode, and its queues and scheduled tasks run continuously, with guaranteed resources. Here are six examples of applications that developers and businesses run on their own Laravel server.
-
Web applications and SaaS platforms
Systems for managing customers, orders, and subscriptions, and SaaS services with user accounts, permissions, and monthly billing, built with Laravel and running on your own domain.
-
REST API services
API services that serve data to mobile apps, websites, and other systems, with authentication through Laravel Sanctum or Passport, while Octane handles every request without bootstrapping the application again.
-
Livewire and Inertia applications
Interactive interfaces that update without reloading the page, built with Livewire or with Inertia and Vue or React, as part of the Laravel application itself.
-
Admin dashboards with Filament
Admin dashboards and internal business systems with tables, forms, permissions, and reports, built with Filament on top of your Laravel application.
-
Online stores and commerce systems
Online stores and ordering systems built with Laravel, with a product catalog, a shopping cart, and payment processing, while the WAF layer filters malicious requests before they reach your forms and checkout.
-
Queues and scheduled tasks
Sending messages, processing files, and generating reports in the background, from Laravel queues in Redis, in processes that Supervisor runs, or on a fixed schedule with the scheduler.
Why run Laravel applications on an ErezNet server
We are a leader in cloud services, and over the years we have gained extensive experience working with business customers in a wide range of fields. Our Laravel servers run on infrastructure with ECC memory and dual power supplies, and we maintain the server as described on this page, so you can focus on developing your application.
-
FrankenPHP and Octane ready to work
Our team installs and configures FrankenPHP, Laravel Octane, and Caddy with the WAF layer when the server is set up, and from then on maintains the server on an ongoing basis. Your application runs in worker mode from day one, and your time goes into development, not into server maintenance.
-
Layered protection
The WAF layer filters malicious requests before they reach your application, the firewall and DDoS protection help protect the server, and your application is available over an encrypted HTTPS connection. A Snapshot backup of the entire server, including your code and databases, is created automatically at the start of every month.
-
Guaranteed resources
Your plan's cores and memory are guaranteed to your server alone and available to the Octane worker processes, the queues, and the database at any hour. As your application grows, you move to a larger plan, and your code, data, and settings stay in place.
-
Personal support and free migration
Our support team is available in our HelpDesk system most hours of the day for any question about the server and the infrastructure. If your Laravel application currently runs with another provider, we will move it to the new server at no cost.
Tools and vendors we work with for servers and hosting
- Dell
- HPE
- Juniper
- Fortinet
- pfSense
- OPNsense
- Cisco
- Check Point
- Citrix
- CloudLinux
- Microsoft
- Intel
- LiteSpeed
- DirectAdmin
- AlmaLinux
- Cloudflare
- Node.js
- Docker
- MariaDB
- MySQL
- NGINX
- cPanel
- Plesk
Services that complement your Laravel server
Free Laravel application migration from another provider
Our team moves your Laravel application from your current provider to the new server at no cost, along with its data. The migration is coordinated with you, and your application keeps running on the previous server until the switch.
- Your application keeps running as usual throughout the move
- Your code and database are copied to the new server
- The switch to the new server happens at the time we agreed with you
Laravel VPS FAQ
Before ordering a Laravel server, it helps to know what is installed on it, who maintains it, and how to deploy your application on it. The answers also cover FrankenPHP, Laravel Octane and worker mode, Caddy, automatic HTTPS and the WAF layer, Redis, queues and scheduled tasks, connecting AI services, and migration from another provider.
What is a Laravel VPS, and who is it for?
A Laravel VPS is a virtual private server that works like an independent computer with its own operating system and resources, with a ready runtime environment for Laravel applications: FrankenPHP and Laravel Octane run your application in worker mode, and Caddy with a WAF module issues the SSL certificate and filters malicious requests. Laravel, a PHP framework, is used to build web applications, API services, and SaaS platforms, and on your own server, your application, queues, and scheduled tasks run continuously, with a fixed IP address and full root access.
The server suits developers, development teams, and businesses that build applications with Laravel and prefer to focus on the code rather than on server maintenance: our team installs and configures the runtime environment, maintains the server, and takes care of the monthly backup.
Which components are installed on the Laravel server?
When the server is set up, we install and configure the complete runtime environment for a Laravel application on it:
- FrankenPHP, a modern application server for PHP, which runs your application.
- Laravel Octane, which runs your application on FrankenPHP in worker mode.
- Caddy, built with xcaddy with a WAF module, for filtering malicious requests and automatically issuing and renewing the SSL certificate.
- PHP, the programming language Laravel and your application are written in, and Composer, the PHP package manager.
- Redis, for caching, sessions, and queues.
- Supervisor, which runs the queue background processes, and cron, which runs the Laravel scheduler.
- Node.js, for building CSS and JavaScript files with Vite.
- Firewall rules, and the operating system you chose from a range of Linux distributions, including AlmaLinux, Rocky Linux, Ubuntu, and Debian.
Once the server is ready, you upload your application code, install the dependencies with Composer, and configure the .env file, with no runtime environment to install. You can install a database on the server, such as MySQL, MariaDB, or PostgreSQL, according to your application's needs.
What is FrankenPHP, and why does the application run on it?
FrankenPHP is a modern application server for PHP, built on the Caddy web server and officially supported by The PHP Foundation. FrankenPHP runs PHP inside the web server itself, so no separate component is needed between the web server and PHP, and requests reach your application by a shorter path.
Together with Laravel Octane, FrankenPHP runs your application in worker mode, where the application loads once and stays in memory. FrankenPHP also supports Early Hints, which lets the server tell the browser which files to load, such as CSS and JavaScript files, before the page is ready, which shortens loading time. Our team installs and configures FrankenPHP for you when the server is set up.
What is Laravel Octane, and how does it improve application performance?
Laravel Octane is an official Laravel package that runs your application on a high-performance application server, which on our Laravel server is FrankenPHP. In a regular PHP application, the framework is loaded again on every request: configuration files, service providers, and routes are read and initialized over and over. Octane loads the application once, keeps it in memory, and passes requests to it, which saves the repeated bootstrapping.
The result is shorter response times and the ability to handle more requests with the same resources, an advantage that stands out especially in API services, high-traffic applications, and interfaces that make many background requests. The actual improvement depends on the application itself, for example on the number of database queries and calls to external services, so we recommend measuring response times before and after moving to Octane.
What is worker mode, and what should I know about it when writing code?
In worker mode, each worker process loads the Laravel application once and handles many requests in a row, instead of loading the application again on every request. Several worker processes run in parallel, and between requests, Octane resets the state of the framework's own components.
Because the application stays in memory, your code needs to account for it:
- Data kept in static variables or in shared services (singletons) can carry over from one request to the next, so do not inject the current request, the logged-in user, or the data of a specific request into a shared service.
- Data that builds up on every request, for example in a static array, gradually increases memory usage. As a safeguard, Octane can restart each worker process after a preset number of requests.
- After every deployment of a new version or change to the .env file, reload the worker processes with the php artisan octane:reload command, so they run the updated code and settings.
We recommend testing your application in worker mode in a test environment before deploying it to production, and making sure the third-party packages it uses support Octane.
How does Caddy enable HTTPS and renew the SSL certificate?
Caddy enables HTTPS automatically: when the DNS record of your domain or subdomain, for example app.example.com, points to the server's IP address, Caddy issues a Let's Encrypt SSL certificate for it, renews it before it expires, and redirects HTTP requests to the HTTPS address. There is no need to install the certificate, renew it manually, or track its expiry date.
Caddy also accepts requests over HTTP/2 and HTTP/3, modern protocols that shorten loading times, especially on mobile connections. In the .env file, set your application's HTTPS address in the APP_URL field, so the links your application generates point to it. An encrypted connection is also required for modern applications to work properly: secure session cookies, OAuth login, such as signing in with a Google account through Laravel Socialite, and payment service webhooks all require an HTTPS address.
Who maintains the server, and who updates FrankenPHP, Octane, and Caddy?
Our team installs and configures FrankenPHP, Laravel Octane, and Caddy with the WAF layer when the server is set up, and from then on maintains the server and updates the operating system throughout your service. Maintenance is included on every plan.
The runtime environment and your application are fully under your control: you write the code, choose the Composer packages, and decide when to update FrankenPHP, Caddy, and Laravel and deploy a new version of your application. For questions about the server and the infrastructure, our support team is available in our HelpDesk system most hours of the day.
What is Composer, and how do I use it to install my application's dependencies?
Composer is the PHP package manager: it reads the list of dependencies in the composer.json file, downloads Laravel and the other packages from the Packagist repository, and records the installed versions in the composer.lock file. This way, every installation of your application, on your development machine and on the server, uses exactly the same versions.
On the server, install the dependencies with the composer install command, according to the versions in the composer.lock file, and in production, add the --no-dev option, which skips installing the development and testing tools. We recommend keeping the composer.lock file in your Git repository and updating packages on your development machine, not directly on the server.
Can I deploy my application directly from a Git repository?
You can clone your application's code repository to the server from GitHub, GitLab, or any other Git service, and pull each new version from it. For access to a private repository, we recommend setting up a deploy key: a dedicated SSH key for a single repository, with read-only access.
A typical deployment of a new version includes pulling the code, installing the dependencies with Composer, building the CSS and JavaScript files with Vite, using the Node.js installed on the server, running the database migrations, caching the configuration and routes, and reloading the Octane worker processes and the queue background processes. You can also deploy automatically on every update of the main branch, with GitHub Actions or GitLab CI connecting to the server over SSH.
Where do I keep the .env file, passwords, and API keys?
Laravel reads environment-specific settings, such as database login details, API keys, and the APP_KEY encryption key, from the .env file in the project folder. The file is created on the server itself and is not included in the Git repository, so the same code runs in your development environment and on the server, each with its own settings.
In production, set APP_ENV=production and APP_DEBUG=false in the file, so technical error details are not shown to visitors. Because Octane loads the settings once, reload the worker processes after every change to the file. We recommend limiting read permissions on the file to the user that runs the application, and keeping a copy of APP_KEY in a safe place: without the key, data your application encrypted cannot be decrypted.
Can I install a database on the server, such as MySQL, MariaDB, or PostgreSQL?
You can install the database your application needs on the server, such as MySQL, MariaDB, or PostgreSQL, which Laravel supports out of the box. A database running on the same server is available to your application at a local address, so there is no need to expose it to the internet. Alternatively, you can connect your application to an external database through the connection settings in the .env file.
The table structure is managed with Laravel migrations, so every change to the structure is kept in the code and applied on the server during deployment. For small applications, SQLite may be enough, with no separate database server. The databases on the server are included in the monthly Snapshot backup, and for an active database, we recommend also keeping a regular backup of the database itself (a dump).
How does my application use Redis for caching, sessions, and queues?
Redis, an in-memory data store, is installed on the server, and Laravel supports it out of the box as a cache, a session store, and a queue backend. Redis shortens your application's response times, because frequently read data is fetched from memory rather than from the database.
You choose which backend your application uses in the .env file, with settings such as CACHE_STORE, SESSION_DRIVER, and QUEUE_CONNECTION. Because Redis keeps its data in memory, take it into account when choosing a plan, and we recommend not exposing it to the internet.
How do queues and background processes work, and can I manage them with Laravel Horizon?
Laravel queues run long tasks in the background, such as sending email, processing files, and calling external services, so your users do not wait for them to finish. The server has Redis installed, which holds the queued jobs, and Supervisor, which keeps the background processes (queue:work) that pull and run the jobs running continuously, and restarts them after a failure and after a server reboot.
In applications that use Redis, you can also install Laravel Horizon, an official Laravel dashboard for configuring the background processes and tracking jobs, run times, and failed jobs. After every deployment of a new version, restart the background processes, for example with the php artisan queue:restart command, so they load the updated code.
How do Laravel scheduled tasks run on the server?
The Laravel scheduler runs on the server through a cron entry that runs the Artisan command schedule:run every minute. On each run, Laravel checks which tasks are due and runs them. This way, you define all of your application's scheduled tasks in code, such as generating reports, cleaning up old data, and sending reminders, with no need for a separate cron entry for each task.
Because the server runs continuously, the tasks run on time at any hour of the day, including weekends and holidays. The time zone of the tasks is set in your application's settings, and you can also set a different time zone for each task.
Does the server include full root access over SSH?
Full root access over SSH is included on every plan, alongside the ongoing server maintenance we provide. With this access, you run Artisan and Composer commands, view logs, and install additional tools. You can also log in with SSH keys, which protect access better than a password.
We recommend running your application and its commands as a dedicated user without root privileges. A Laravel application writes files to only two folders, storage and bootstrap/cache, so only they need write permission, and the rest of the application files should be read-only. We recommend coordinating changes to operating system settings, such as the firewall rules, with our team in advance, so operating system updates continue as usual.
Can I connect my application to ChatGPT, Claude, and Gemini and build AI agents?
Laravel applications connect to ChatGPT, Claude, Gemini, and other AI services through SDKs and dedicated PHP packages, installed with Composer, and an API key issued by the provider. This is how you build AI agents, chatbots, document summarization tools, and smart search over your business information inside your application. We recommend running long requests to the models in a queue, so your users do not wait for the answer, and keeping your API keys in the .env file.
In addition, the official Laravel MCP package lets you expose tools and data from your application to AI agents over MCP (Model Context Protocol). The models themselves run on the AI providers' infrastructure, so the server does not need a graphics processor (GPU), and usage of the models is billed directly by the provider.
For software development with coding agents, such as Claude Code or Codex, an AI coding VPS is a good fit, and for no-code AI automations, an n8n VPS.
Can I upgrade the server as my application grows?
You can upgrade the server to a larger plan at any time, with more cores, memory, and disk space, by opening a ticket in our HelpDesk system. The upgrade needs only a short reboot, after which the server is back up with your application, data, and settings, and Supervisor restarts the queue background processes.
After the upgrade, you can increase the number of Octane worker processes and queue background processes, so your application uses the additional cores. On request, you can also reduce cores and memory, but disk space cannot be reduced. For applications that need a different combination of resources than the plans offer, you can order a custom configuration by opening a ticket in our HelpDesk system.
How do I track my application's resource usage and performance?
The monitoring graphs in the client area of our HelpDesk system show CPU usage and load average, memory usage, disk activity, network traffic, and the number of users logged in to the server.
At the application level, you can install Laravel Pulse, an official Laravel package that shows slow requests and queries, queued jobs, and application errors in a dashboard. For external monitoring of your application's availability, our website and server monitoring service is available for an additional fee.
Which operating systems can I choose for the Laravel server?
When you order, you choose from a range of Linux distributions, including AlmaLinux, Rocky Linux, Ubuntu, and Debian. FrankenPHP, Laravel Octane, and Caddy with the WAF layer are installed on each of them, and your Laravel application works the same way on all of them.
We install and update the operating system, so you need no prior Linux administration knowledge. If you have no preference, choose AlmaLinux, the default option in the order form. Developers who are used to Ubuntu can choose it and work in a familiar environment.
Will you migrate my Laravel application from another provider?
Our team will move your Laravel application from your current provider to the new server at no cost, along with its data. Your application keeps running on the previous server until the switch, and the switch date is set together with you.
When the migration is complete, point your domain's DNS record to the new server's IP address. To arrange the migration, open a ticket in our HelpDesk system.
Do you guarantee server availability?
Yes. We do everything we can to keep our servers available at all times, and we commit to at least 99% availability on an annual average, from the first day of service.
Is there a commitment, and do prices include VAT?
The service is billed monthly, with no commitment beyond the current month of service, no fine print and no cancellation fees. All plan prices include VAT.