Nº 01Guide
How much RAM does a dev server for Laravel projects need?
We set up three large Laravel applications on an instance with 3 cores and 3 GB and measured memory at every step. The short version: an idle project needs little, the peak is the frontend build. The largest one needed 1.8 GiB and went through.
Updated:
02Guide
The test setup
We measured on 10 November 2026 on an Envbay instance on the Starter plan with 3 cores and 3 GB of memory (Envoryx 0.46.7). Memory applies to the whole instance: all projects share it. A single container on Starter may also use at most 3 GiB.
Each application came from its Git repository, with MariaDB 11, Redis and Mailpit as services. As memory use we give the peak value the kernel records for the application container (memory.peak), file cache included. Instance storage is HDD-based with a RAM cache. All values are single measurements, not averages.
03Guide
Templates: time and idle memory
| Template | Services | Time until “Running” |
|---|---|---|
| Laravel | MariaDB 11, Redis, Mailpit | 44 s |
| WordPress (PHP 8.5) | MariaDB 11, Redis, Mailpit | 38 s |
| Symfony | MariaDB 11, Mailpit | just under a minute |
| Next.js (Node 26) | none | 70 s |
| Django (Python 3.14) | PostgreSQL 18 | 36 s |
| Empty project without PHP (static site) | none | 5 s |
Measured on 10 November 2026 on the Starter plan with 3 cores and 3 GB, one run each, rounded to whole seconds.
Right after creation the Next.js project used 147 MiB, Django with PostgreSQL 159 MiB and the static site 10 MiB. Three projects side by side, which is what the Starter plan allows, added up to 540 MiB of 3 GiB when idle: Next.js, Django and the fully installed Monica application with its five containers.
04Guide
What the big steps need
| Application | Step | Duration | Peak |
|---|---|---|---|
| Monica | composer install | 40 s | 158 MiB |
| Monica | yarn install | 14 s | 1,549 MiB |
| Monica | vite build (client) | 15 s | 1,836 MiB |
| Monica | vite build --ssr | 6 s | 928 MiB |
| Firefly III | composer install | 31 s | 153 MiB |
| Firefly III | npm ci | 5 s | 357 MiB |
| Firefly III | npm run build --workspace resources/assets/v3 | 6 s | 844 MiB |
| Invoice Ninja | composer install | 74 s | 287 MiB |
| Invoice Ninja | ninja:create-test-data with memory_limit 1G | stopped by us after 40 min | 727 MiB |
Measured on 10 November 2026. Monica (as of 28 October 2026) with PHP 8.4 and Node 24, Firefly III (as of 26 October 2026) and Invoice Ninja (branch v5-stable, as of 18 October 2026) with PHP 8.5. The value for the SSR build is the highest one sampled once per second, because the client build before it peaked higher.
The full Monica build, vite build && vite build --ssr, went through without a cap on the Node heap. Of the 1,836 MiB at the peak, 1,660 MiB were process memory, the rest file cache. We repeated the build while a Next.js project and a Django project were running next to it: it went through again.
Everything PHP does stayed far below that: composer install needed no more than 300 MiB for any of the three applications, and the migrations were done after one or two seconds. Only Node needed a lot of memory, while installing packages and building the frontend, and each time for seconds.
05Guide
What we ran into
- Monica could not be installed with PHP 8.5:
composer installstopped with “Your lock file does not contain a compatible set of packages”, because three packages allow PHP 8.4 at most. With PHP 8.4 everything went through. You change the PHP version on the “Runtime” tab of the project. - Firefly III requires PHP 8.5 or newer. The frontend build lives in a subfolder: first
npm ci, thennpm run build --workspace resources/assets/v3. - The test-data generator of Invoice Ninja,
php artisan ninja:create-test-data, asks before it starts and takes a bare Return as “no”. With the default PHPmemory_limitof 256M it stopped after a good 16 minutes and 1,001 invoices: “Allowed memory size of 268435456 bytes exhausted”. - With
memory_limit1G the generator got past that point, and the PHP process stayed at about 720 MiB. After that it only created clients. We stopped the run after 40 minutes at 5,091 clients. - You set
memory_limiton the “Runtime” tab in the “PHP” section, from 64M to 2G or unlimited. After saving, the PHP container restarts. - Envoryx fetches Git repositories as a partial clone. That way Invoice Ninja was set up as a project in 32 seconds including the clone, and the project folder took 220 MB.
06Guide
What happens when memory runs out
We tried it. In the Node container of a Next.js project a script took more and more memory in steps of 100 MiB, with a Django project running next to it. After printing “2600 MiB” the kernel ended the process, recognisable by exit code 137. The container had used 2,746 MiB by then. In a second run with the Django project stopped it was 2,897 MiB.
Envoryx then shows a warning on the project that names the container, the time and the limit of 3072 MiB and says that a process was ended. Only the script was ended. Both projects kept running, and their pages loaded afterwards.
Two things are worth knowing. First, the end does not come at 3 GiB, because whatever other projects use is missing. Second, /proc/meminfo inside the container shows more memory than the limit allows. Tools that size themselves by it plan too large.
07Guide
Rules of thumb
- Idle counts for little: three projects side by side used 540 MiB.
- Plan for the peak. Installing packages and building the frontend with Node needed between 357 and 1,836 MiB for our three applications, each time for seconds.
- PHP is modest:
composer installstayed below 300 MiB. - Check the PHP
memory_limitbefore test data and imports. The default is 256M. - Not everything has to run: a project you stop in the project list has no running containers any more, and one click starts it again.
The Starter plan has 3 GB of memory, Team 6 GB and Agency 12 GB. All measurements on this page are from 10 November 2026 on the Starter plan.
| Free | Starter | Team | Agency | |
|---|---|---|---|---|
| Price per month (incl. VAT) | €0 (trial) | €12 | €29 | €59 |
| Instance cores | 1 | 3 | 4 | 6 |
| Instance memory | 1 GB | 3 GB | 6 GB | 12 GB |
| Storage | 10 GB | 30 GB | 75 GB | 150 GB |
| Projects | 1 | 3 | 10 | 25 |
| Users | 1 | 1 | 5 | 15 |
| Runtimes | PHP, Node, Python, static | PHP, Node, Python, static | all available | all available |
| Services Ollama and OpenSearch | not included | not included | included | included |
| Branch environments | no | no | yes | yes |
| Instance backups | local only | off site | off site | off site |
| Project backups off site | no | yes | yes | yes |
| Custom images | no | no | no | yes |
| Own backup targets | no | no | no | yes |
Beta: the first 6 months cost half the price. Annual payment equals 10 monthly prices. incl. 19% VAT.
07FAQ
Frequently asked questions.
Q.01Is 3 GB enough for a Laravel project?
Q.02Why is my build killed although memory still seems free?
Q.03Is there swap?
08Guides
Keep reading
- Laravel staging serverLaravel staging with database, Redis, Mailpit and an HTTPS address, without maintaining a server yourself.Laravel staging
- Rent a dev serverWhat matters when renting a dev server and what a ready development instance offers over a VPS.Rent a dev server
- Laravel in 10 minutesStep by step: open your instance, create a Laravel project, load the page and work through SSH in your IDE.Guides
Try it yourself.
Pick a plan, order, open your instance. Prices include 19% VAT.