RunCloud

RunCloud is a hosted management service for servers supplied by the customer. Its documentation starts with connecting a fresh compatible server, after which the dashboard manages web applications and hosting configuration. Paying for RunCloud does not by itself rent the underlying compute instance.

Key features

• Server connection. A supported server is connected to the RunCloud account using its installation workflow.
• PHP applications. Documentation covers PHP web applications, Laravel and WordPress deployment.
• Release workflows. Git and atomic-deployment tools support application updates.
• Operations. Backup, monitoring, user-management and API features are documented, with availability tied to the subscription.

Who it is for

Developers and agencies running PHP or WordPress sites on cloud servers who want a shared administration interface. The model suits teams that choose their own infrastructure but prefer dashboard-based hosting operations.

Pricing at a glance

RunCloud uses paid monthly or annual subscriptions with server allowances. The infrastructure provider charges separately, and backup or other additions may affect cost. Check the current plan page for any trial rather than assume a permanent free tier.

Pricing model checked on 15 October 2026; confirm current terms on the official product page. No currency conversion or fixed price estimate is used in this profile.

Things to consider

• Connected inactive servers can still count towards a plan’s server allowance.
• The getting-started guide requires a compatible fresh server and excludes OpenVZ virtualisation.
• Customers still need to plan server access, recovery and application security.

Before connecting a production server, make an inventory of its applications, runtime versions, storage and external services. Decide who will maintain the operating system and who can access the panel. Test the software on a compatible non-production server first, and confirm that a failed deployment or panel outage will not prevent you from restoring the applications.

Getting started

1. Read the official documentation and plan information, then write down the features and costs your project needs.
2. Prepare a compatible test server and follow the official installation or connection documentation.
3. Configure restricted access, domain settings and certificates; keep secrets out of source repositories.
4. Test deployment, backups and restoration with representative data before changing production DNS.
5. Review usage and recurring charges after the pilot, and document a migration or cancellation path.