VPS

Install WordPress on a VPS with Matrix: a real test and its cost

Updated Sep 12, 2026 · Versión en español

On September 12, 2026, we installed WordPress with Matrix on an AMD VPS with 1 vCPU, 1 GB RAM and 10 GB disk. Its homepage responded over HTTP from the internet, and the final conversation charge was EUR 0.414156 (approximately EUR 0.41). Here are the configuration, request, approvals and checks behind that result.

The video and this test are separate runs

The video published on August 5, 2026 starts with a request in Spanish: "Set up WordPress for me. Don't ask me questions, just do it." The demonstration covers the server proposal, connection approval and installation.

The original video is in Spanish. It lasts one minute; its running time does not measure deployment time. The resources, timings and charges in this article belong to the new test on September 12. We do not attribute them to the August recording.

The configuration we used

  • VPS: the AMD EPYC/Ryzen range in Madrid, with 1 vCPU, 1024 MB RAM, 10 GB disk and a dedicated IPv4 address.
  • Operating system: Ubuntu 24.04, kernel 6.8.0-139-generic.
  • Matrix: GPT-5.6 Terra, executing through Guest Agent. The connection test offered this channel; the VPS did not have the recovery key used by Matrix's SSH channel installed.
  • Starting state: the VPS already existed and had run a sysbench CPU test. It retained sysbench and its dependencies, but Nginx, PHP-FPM, MariaDB and WordPress were not installed. It was not an untouched operating system image.
  • Scope: a test site over HTTP, without a domain or HTTPS. We did not increase its resources.

This configuration completed the installation described here. The test does not measure WordPress visitor capacity or the resources needed by a shop, a site with plugins or a production application.

The request sent to Matrix

On the VPS Agent tab, we selected Terra, opened the intervention chat and clicked Test connection. After choosing Guest Agent, we submitted the following request in Spanish. This is its English translation:

Install WordPress on this test VPS with Nginx, PHP-FPM and a local MariaDB instance, and make its homepage work over HTTP on the IPv4 address. Do not configure a domain or HTTPS, and do not increase resources. Create an administrator with a random password and the email admin@example.invalid; store the credentials only in /root/wordpress-test-credentials.txt with permissions 0600, without displaying them or sending email. Keep the database inaccessible from the internet. Preserve all benchmark files and directories in /var/tmp without deleting or overwriting them. Show me the plan for approval and, when finished, check the HTTP response and installed versions.

What Matrix did and what we did

  1. Matrix inspected the server and proposed a plan. It detected that the platform firewall still blocked HTTP.
  2. We rejected the first proposal because it included the web preset, which opened ports 80 and 443. We asked Matrix to install WordPress and check HTTP locally without changing that firewall.
  3. We approved the revised plan using the panel's button. An acceptance message in the chat does not replace this approval.
  4. Matrix installed and configured the software. The initial password generation failed; Matrix corrected that step and completed the installation within the same plan.
  5. We opened only TCP/80 through MCP as a separate operator action. Matrix did not perform that opening. We did not open port 443 or the database port.
  6. We checked the result over HTTP and through independent server reads, without completing the installation through another channel. We then closed the conversation and verified its settled charge.

This was an assisted installation with operator review and approvals. The case does not demonstrate a deployment without operator involvement.

The verified result

The installation used WordPress 7.1, Nginx 1.24.0, PHP-FPM 8.3.6 and MariaDB 10.11.14. Nginx, PHP-FPM and MariaDB were active and enabled to start with the system.

Independent checks confirmed that:

  • WordPress was installed, rather than only downloaded or awaiting the initial setup wizard.
  • The homepage, titled "WordPress de pruebas", returned HTTP 200 from the internet.
  • MariaDB listened only on 127.0.0.1:3306.
  • The credentials file belonged to root:root and had permissions 0600; we did not publish or read its contents during independent verification.
  • All 91 files in the sysbench result retained exactly the same SHA-256 hashes after WordPress was installed.

How long this reproduction took

The plan record shows 66 seconds between approval and completion by Matrix (13:56:59-13:58:05, Madrid time).

There were approximately four minutes between the first request and our external HTTP check. That window includes reviewing the proposal, correcting its scope, approval, the operator's port opening and verification. The VPS had already been provisioned; its creation is outside this timing.

These are observations from this test. Package downloads, model response time, server state and waiting for approvals can change another run's duration.

The Matrix charge and VPS tariff

  • Matrix: the settled charge against the account balance was EUR 0.414156. It includes the whole conversation: initial review, plan correction, installation, verification exchange and final memory turn at closure. It matches both the usage record and the balance transaction.
  • VPS: the tariff for this configuration was EUR 0.0083 per hour, including IPv4. This is the hosting tariff, separate from the Matrix charge; it is not the total charge for every hour the server remains created. The AMD range starts at an advertised reference price of EUR 6/month.

Matrix showed the model's rates before the intervention was opened and the accumulated charge while it worked. The counter before closure was provisional: settlement added the final memory turn. This particular installation does not establish a fixed WordPress installation price; another request may use a different amount of AI.

What remains before using it as a production website

The result of this test is a homepage reachable over HTTP on an IP address. We did not configure a domain or HTTPS certificate, or test real traffic, plugins, backups or recovery. Those steps need to be defined and checked for the intended site.

See the AMD VPS configurations and how Matrix works with agentic VPS. The AMD and Intel E5 CPU comparison explains the earlier benchmark separately; its figures do not measure WordPress capacity.