ALTERNATIVES
Alternative To RunCloud
Are you looking for a Runcloud alternative?
Ploi is the best solution to cover all your difficult server management tasks. Ploi helps you manage your servers securely without any difficult configuration.
Take a look at the features in the table below that we offer right out of the box to help you get started easily.
Already on RunCloud? Ploi can take that server over. Same machine, same IP, and your web apps move onto Ploi's own stack. See how the import works
| Feature | ploi.io | RunCloud |
|---|---|---|
| Flexible Load Balancing | ||
| DNS Management | ||
| Server Insights | ||
| Site Monitoring | ||
| Flexible Subscriptions | ||
| Unmodified Original Linux Repositories | ||
| Extensive Team Management | ||
| Beautiful Crafted Status Pages | ||
| Staging to Production Management | ||
| Rollback deployments | ||
| Whitelabel solution | ||
| Mobile App | ||
| Based in Europe 🇪🇺 | ||
| Docker Server Support | ||
| Scheduled Deployments | ||
| Website Isolation | ||
| Tenants | ||
| Marketplace | ||
| Notifications | Slack, Discord, E-mail, Telegram, Pushover, Microsoft Teams, Rocket.Chat, Google Chat, Custom URL, Native mobile push notifications | Slack, Telegram |
| Supported Server Types | Web server, Database server, Redis server, Valkey server, Worker server, Load balancer server, Storage server, MeiliSearch server, Elasticsearch Server, Plain server, Email server | Web server, Database server, Cache server |
| Support | E-mail, Ticket System, Discord |
Bring your RunCloud server to Ploi
You keep the server. Ploi connects over SSH, installs its own stack next to RunCloud's and moves your web apps onto it. The machine and the IP stay the same, so there is no DNS switch. Your apps go offline only for the short moment Ploi switches serving over to its own nginx, about a minute.
- 1 In Ploi, open Servers, click Create server and pick Import server.
- 2 Choose RunCloud, fill in the IP and run the command we show you as root on the server. It only adds Ploi's SSH key.
- 3 Ploi scans the server and lists the web apps and databases it found. You tick the sites you want to bring over.
- 4 Start the import. Ploi installs its stack, moves each app to its own layout and switches serving to Ploi's nginx. On a small server this takes a few minutes.
Questions first? Ask us.
- Each web app moves from RunCloud's /home/<user>/webapps layout to Ploi's /home/<user>/<domain> layout, keeps its PHP version and web directory, and its RunCloud user becomes a Ploi system user.
- Ploi installs its own nginx and PHP-FPM and serves each app through them. RunCloud's nginx, Apache and PHP-FPM are stopped, not removed.
- Databases and database users are registered. MySQL only stores password hashes, so you set a new password from Ploi when you need one.
- The cron jobs RunCloud scheduled are taken over and shown in the panel, with their app paths rewritten to the new location.
- RunCloud's Let's Encrypt certificates are registered so Ploi warns you before they expire. RunCloud stops renewing them once the server leaves it, so you request a Ploi certificate per site.
- RunCloud's NGINX + Apache stack reads .htaccess files. Ploi is nginx only, so apps that rely on custom .htaccess rules may need those translated afterwards. Servers on OpenLiteSpeed cannot be imported.
- Deploy settings live in RunCloud's panel, not on the server, so you connect the repository and set the deploy script per site in Ploi.
- The last step stops RunCloud's agent so it no longer manages the server. Its packages stay installed so the move can be reversed, and you can leave this step off in the wizard.