A stack is the set of services an environment runs. Some of it arrives with your project type and some of it you pick.
What arrives with the project type
Choose a project type: Drupal, Laravel, WordPress, Django, Node.js, PHP, Python, Ruby, Go, Rust or a static site. The web bundle comes with it, whole:
- the runtime for that language: PHP-FPM, a Node.js server (or Bun, when your repository asks for it), your Go or Rust binary, your Python application under Gunicorn or Uvicorn, or your Ruby one under Puma
- Nginx, serving static files and passing requests to PHP: PHP projects only. A Node, Go, Python, Ruby or Rust application gets Nginx in front only where its repository names it. A static site is Nginx and its files, and nothing else
- a queue worker container: Laravel only
- OpenSMTPD, so the application can send mail: every project but a static site
The schedule comes with it too, but not as a container. Your framework's
cron runs on the machine itself, against the application already running
there. Declare your own jobs in vallic.yaml.
These are not tick-boxes. They run on the machines you already pay for, at no extra charge.
Every PHP project (Drupal, Laravel, WordPress or plain PHP) runs on the same PHP-FPM image. The platform sets what differs: the Nginx configuration, the document root, the default cron and the directories kept between releases.
What you choose
Drupal, Laravel and WordPress require two:
- A database. MariaDB, MySQL or PostgreSQL. Choosing MySQL or PostgreSQL replaces MariaDB; you never run two.
- A cache. Redis, Valkey or Memcached, one of them.
A PHP, Go, Node.js, Python, Ruby or Rust project needs neither, and gets either only by asking. A static site is offered neither, nor anything else below but its build tools.
Your database, its user and its password are created for that environment alone. Your application is handed them in its environment file. You never set them and you never need to know them.
The rest are optional and cost a machine or a container each:
- Search: Solr or Meilisearch, one at a time
- Time series: InfluxDB, beside the database, for metrics, sensor readings and events
- Queue: RabbitMQ, when jobs need a real broker rather than the database
- Proxy: Vinyl Cache (Varnish), in front of the web servers
- Build tools: Node.js for builds, for a PHP site whose
theme or assets need
npm. It runs only during a build, never beside the site
What each service needs
The Memory, at least column below says how much memory a service needs on its machine. The configurator adds up what will run on each machine and offers only the sizes with room for it; a size too small says so in the list.
- The smallest machine, with 768 MB to give, carries a PHP site with its database and a cache.
- Solr needs another 1.5 GB with the ZooKeeper that comes with it, beside the site or on a machine of its own.
The vCPU column is what a service wants of the machine's cores, and RabbitMQ wants 1 GB of its disk free. A machine with fewer cores or less disk than what runs on it wants is still sold, and runs more slowly than it should. The estimate and the configurator say so. The Resources tab says it of each machine you have.
The same figures hold after you have bought:
- A service named in
vallic.yamlis not started on a machine without room for it. The deploy says which machine and how much it has. - Adding a service on a machine of its own, or moving one, refuses a size too small for what will run there.
- A machine is not resized down below what runs on it.
- A Valkey or Redis that keeps its data counts twice its figure. It is not told to keep it under Service settings on a machine without room for that.
On a shared plan each site has its share of the machine, and its stack has to fit that share. On the preview machine each environment runs the whole stack in its share, so every environment needs room for it.
The PHP-FPM figure counts the whole web bundle: Nginx, the mail relay and the queue worker run in it.
Everything, with versions
The version in bold is what you get if you do not choose one.
| Service | Kind | What it does | Versions | Memory, at least | vCPU |
|---|---|---|---|---|---|
| Bun | Application | A Node.js application run by Bun rather than Node: the same project, chosen when it is ordered or with bun: under runtime in vallic.yaml, which decides. Replaces PHP-FPM and nginx: it is the web server too. |
1.4, 1.3 | 256 MB | 0.25 |
| Go | Application | A compiled Go binary serving its own HTTP. Replaces PHP-FPM and nginx: it is the web server too. | 1.27, 1.26, 1.27.0, 1.26.7, 1.26.6 | 64 MB | 0.25 |
| Node.js | Application | A Node application serving its own HTTP. Replaces PHP-FPM and nginx: it is the web server too. | 26.13, 26.11, 26.12, 24.21, 24.22, 22.23 | 256 MB | 0.25 |
| PHP-FPM | Application | The platform's PHP-FPM image, for every PHP project: Drupal, WordPress, Laravel or anything else. | 8.5, 8.4, 8.3, 8.2 | 320 MB | 0.25 |
| Python | Application | A Python application serving its own HTTP through a WSGI or ASGI server — Gunicorn, Uvicorn. Replaces PHP-FPM and nginx: it is the web server too. | 3.15, 3.14, 3.13, 3.12 | 256 MB | 0.25 |
| Ruby | Application | A Ruby application serving its own HTTP through Puma — Rails, Sinatra, Hanami. Replaces PHP-FPM and nginx: it is the web server too. | 4.0, 3.4 | 384 MB | 0.25 |
| Rust | Application | A compiled Rust binary serving its own HTTP — Axum, Actix Web, Rocket. Replaces PHP-FPM and nginx: it is the web server too. | 1.99, 1.98 | 64 MB | 0.25 |
| Static site | Application | nginx serving the files a build writes, with nothing behind it: the web server is the application. | 1.31, 1.30 | 16 MB | — |
| MariaDB | Database | The database. The same service on the web server or on a machine of its own. | 11.8, 11.4, 10.11 | 320 MB | 0.25 |
| MySQL 8 | Database | Oracle's MySQL rather than MariaDB, where an application or a team is committed to it. | 8.0, 8.4 | 320 MB | 0.25 |
| PostgreSQL | Database | The other relational database. Chosen instead of MariaDB, never beside it. | 18.6 | 256 MB | 0.25 |
| Queue worker | Application | Laravel's queue worker. The same container again, running the worker. | — | — | — |
| Nginx | Application | Serves static files and passes PHP to FPM, behind the shared edge proxy. | 1.31, 1.30 | — | — |
| Valkey | Cache | Cache and sessions. Not needed for several web servers, but faster for both. | 9.0, 9.1, 8.1, 8.0 | 128 MB | — |
| Redis | Cache | In-memory cache, for what expects Redis by name. Valkey is the fork most stacks now take. | 8.6, 8.10, 8.4, 8.2 | 64 MB | — |
| Memcached | Cache | A simpler cache than Redis: keys and values, nothing else, and nothing kept when it restarts. | 1.6 | 64 MB | — |
| Meilisearch | Search | A lightning-fast search engine API, with AI-powered hybrid search for your sites and applications. | v1.56.2, v1.56.1, v1.56.0, v1.53.3, v1.55.1, v1.55.0, v1.53.1, v1.53.0, v1.52.4, v1.52.3 | 384 MB | 0.5 |
| RabbitMQ | Background work | A message broker for work that outlives the request that asked for it. | 4.3.8, 4.3.7, 4.4.1, 4.4.0, 4.3.6, 4.3.5, 4.3.4, 4.3.3 | 1 GB | 0.5 |
| Vinyl Cache (Varnish) | Reverse proxy | Varnish. Caches whole responses in front of the site, so a hit never reaches it at all. | 8.0, 9.1 | 192 MB | — |
| Solr | Search | Search. Needs zookeeper, which is added automatically. | 10.1, 10.0, 9.10, 9.11 | 1.25 GB | 1 |
| InfluxDB | Time series | Time series: metrics, sensor readings and events, written and queried by time. | 2.9, 2.9.1, 2.8.0 | 1 GB | — |
| ZooKeeper | Search | Coordination for Solr. Never selected on its own; Solr pulls it in. | 3.9 | 256 MB | — |
| OpenSMTPD | Application | Outbound mail relay for environments not using a hosted provider. | 7.8 | — | — |
| Node.js | Build tools | Node.js and npm for build steps, such as compiling a theme. Runs in the build, on no machine. | 26.13, 26.11, 26.12, 24.21, 24.22, 22.23 | — | — |
Each service has its own page under Software in the sidebar: the full version list, the versions on their way out, and the variables you may set.
Changing a version
Versions are per environment, so try a runtime or database upgrade on staging first. Staging is an environment you add to a project, on either plan: see Environments. Without one, the first environment to run a new version is production.
Data on disk survives a container image changing, so an upgrade is not a restore from backup.
Treat a major version change as one-way unless you have checked otherwise. A database that has opened its files with a newer version will usually refuse an older one.
Next
- Environments: where these versions are set
vallic.yaml- Service settings
Thank you. Good to know it helped.
Thanks — tell us what was missing. Open a ticket from Support in the console, and we answer on the ticket. Open the console