What is RunCloud and how to manage PHP servers
Published on 2026-10-26 by frfrand
RunCloud to connect VPS and manage PHP, Nginx and websites
RunCloud doesn't primarily sell you the machine: it helps you manage servers you contracted yourself. That difference changes the comparison from the first minute, because you keep paying and maintaining the infrastructure provider.
The first question isn't "which platform wins?", but what problem you solve with it. A WordPress store, an API with PostgreSQL, and a system that generates videos don't need the same infrastructure.
What RunCloud is and what it really does
RunCloud is oriented toward managing sites and PHP applications on compatible servers, with configuration and deployment tools according to the plan. It's a panel connected to your infrastructure, not an automatic replacement for the VPS provider.
Think about it with this example
An agency has ten Laravel sites on different VPSs. A panel can simplify configurations and repetitive maintenance. If it also has Django, Redis, n8n, and persistent bots, it needs to check which pieces fit the panel's model.
How to test it without putting production at risk
- Contract a compatible server with the provider you prefer.
- Connect it to RunCloud following the official process.
- Configure domain, PHP, web server, and certificates.
- Deploy a test website, test staging if you need it.
- Document backups, SSH access, and the person responsible for updating the host.
After the last step, open the service from another network, run a real operation and check what the logs show. If you store data, verify that it survives restarts and application updates. There is nothing more misleading than a demo that works fine until the first redeploy.
The most common stumble
Compare the server cost and the panel subscription. Do not confuse "managed site" with "secure application" when you still have dependencies, permissions and databases under your responsibility.
VPS security does not consist of opening only port 443 and forgetting about it. It also includes permissions, system updates, backend credentials, database access, verifiable backups and a way to act if someone loses a key.
Doing the same project in ArduMaker
ArduMaker integrates the VPS and its deployment and operation tools. It is not identical to a PHP panel, but it can avoid hiring a separate tool when your projects use various stacks.
A typical walkthrough in ArduMaker would be: create a VPS, connect the GitHub repository, deploy an application, associate an HTTPS domain and, if necessary, install PostgreSQL or Redis within the infrastructure. For client projects, separation by Company avoids mixing permissions and invoices. And if the service needs to stay active, it is configured and supervised as a process, not as a temporary demo.
Clear comparison, without weird promises
| Aspect | RunCloud | ArduMaker |
|---|---|---|
| Main product | RunCloud focuses on managing sites and PHP applications on compatible servers, with tooling | VPS with integrated infrastructure and application management |
| How you publish | Depends on the product's tools and services | Git, services, and domains from the platform |
| Databases and containers | Depending on edition, installation or additional services | PostgreSQL, Redis and Docker available in the VPS environment |
| Who maintains the app | Your team and the provider, depending on the management level | Your team maintains the app; VPS management via the panel |
What I would consider before deciding?
RunCloud is interesting when you already have servers and need specific PHP management. ArduMaker when you are looking for infrastructure and management of several types of apps in the same environment. But first, calculate the full cost: infrastructure, panel licenses, storage, backups, traffic, and maintenance time. The cheapest rate on the cover can end up being expensive if you end up spending hours recovering services.
It is also worth distinguishing hosting from management. There are panels that need an external VPS, providers that give you an almost empty server, and managed platforms that limit access to certain layers. They are different problems, so comparing them only by monthly price is a trap.
Questions I would ask myself before migrating
- Can I extract my data and restore it without relying on the panel?
- Where do I check logs when a request fails?
- What happens when I restart or update the server?
- Can I separate each client's access without sharing passwords?
- Does the service support the runtime, ports, and processes I actually need?
To keep reading: RunCloud Documentation · RunCloud vs ArduMaker Comparison · ArduMaker Documentation.
In short: choose the tool that lets you deploy, maintain, and recover the project with the least reasonable risk for your team. Everything else is a list of features worth checking with a real test.