| Capability | Runex | a VPS |
|---|---|---|
| Primary model | Deployment platform / PaaS-style app shipping | Virtual machine you administer |
| Host OS & packages | Managed by the platform | You install and patch |
| GitHub deploy workflow | GitHub App + branch deploy + webhooks | DIY (CI scripts, SSH, systemd, etc.) |
| HTTPS | Provided for *.runex.cloud and attached custom domains | Usually configure yourself (e.g. reverse proxy + certs) |
| Custom domains | CNAME to cname.runex.cloud | Point DNS to your VPS and configure the web server |
| Isolation | Containerized deployments with resource controls | You design isolation (users, containers, VMs) |
| Flexibility | Constrained to supported deploy paths | Very high — full machine control |
| Best when | You want easy application deployment from GitHub/Docker | You need full OS control or unusual system dependencies |
How to read this comparison
- Runex is not marketed as a raw SSH VPS product.
- A VPS can still be the right choice for specialized infrastructure needs.
- See the blog: PaaS vs VPS for a longer educational comparison.
Competitor capabilities change. Verify against official a VPS documentation before making a purchasing decision. See also Runex features and security.
Next step
Deploy your first application
Connect a GitHub repository, deploy with Runex, and get a production HTTPS URL on *.runex.cloud.