WordPress hosting does not require every site to share the same runtime identity. Linux already provides the primitives needed to separate ownership, processes and application files; automation can make those primitives practical to use consistently.
Give each site its own operating-system boundary
A dedicated system user and a separate PHP-FPM pool reduce accidental cross-site access and make resource ownership clearer. Files do not need to be writable by one shared web account.
Automate the surrounding infrastructure
The WordPress archive is the easy part. A production deployment also needs a database, PHP runtime, web-server configuration, HTTPS, file ownership and backups. Those steps benefit from a single repeatable workflow.
Keep standard components
Nginx or Apache, PHP-FPM, MariaDB or MySQL and Let’s Encrypt remain familiar operational components. The automation layer coordinates them rather than replacing them.
Plan for day-two operations
Backups, staging, SSL renewal and runtime inspection matter after initial deployment. Treat them as part of the application lifecycle instead of separate utilities.