PHP hosting with a version and a configuration per website
Every PHP website on a Dashmox server gets its own interpreter version, its own settings and its own pool of processes, running as its own Linux account. One server, one site on an old version and the one beside it on the newest, and neither can read the other's files.
What you get per website
The decisions that usually belong to the server.
Shared PHP hosting normally settles these once, for everybody on the machine. Here each is a choice per website.
Its own version
Chosen per website from the versions installed on the server, so an application that will not move yet does not hold back the one next to it.
Its own extensions
Turn the extensions a website needs on and off for that website, all at once rather than one switch at a time.
Its own settings
Memory, upload size, execution time and the rest, as a form or as the file itself. A line PHP would refuse is refused before it is saved rather than after.
Its own account
PHP runs as the website's own Unix account with no shell. It reads and writes its own files and reaches its own database, and nothing else on the server.
Databases that belong to it
MySQL, MariaDB or PostgreSQL, each database with its own accounts, its own size limit and its own backups.
Applications in one step
WordPress, Joomla, Laravel and the rest install with their database made, their files owned correctly and their certificate issued.
Which versions
What the server has, not what we promise.
Which PHP versions a website can choose depends on the Ubuntu release the server runs, and that is a real constraint rather than a shrug: Ubuntu ships one version per release and the rest come from a third party archive. A server installed on 24.04 can hold several majors side by side. A newer release may offer only the one it ships until that archive catches up.
The panel is straight about it in the place it matters, which is the installer: it says which versions this machine can offer before you commit to the machine. The installation guide says the same thing in writing, and it is worth reading before choosing a release for a server you intend to put customers on.
Being honest about it
What a pool per website is and is not.
PHP hosting here is isolation by Linux account and by process: a website's PHP cannot read another website's files, and a site that fills its own pool queues its own requests rather than everybody's. It is not a virtual machine, and nothing here will tell you it is. What the boundary actually is, and what it does not cover, is written out in full.
A pool also costs memory, which is why the static runtime exists: a website that is three hundred HTML files does not need an interpreter sitting behind it. Choosing what a website runs is a decision per site, and PHP is one of five answers.
Your servers, with nothing on them counted.
The whole panel is free on one server, with no limit on websites, mailboxes, DNS zones or customer accounts. Pro, for up to five servers, is not available yet.