RamNode®
Cloud VPS, RamNode Standard
The most popular VMs in our fleet. Highly capable, great value, and resource steps that make it easy for you to right size.
Standard VPS
Powerful virtual machines with great balance of performance and value
Standard VPS – VPS Hosting
Get a fully virtualized SSD compute instance with a great balance of price and performance.
| Memory | CPU | SSD | Bandwidth | Price, includes 1 IPv4 |
|---|---|---|---|---|
| 512MB | 1 Core | 20GB | 1TB | $4/mo ($0.006/hr) |
| 1GB | 1 Core | 40GB | 2TB | $5/mo ($0.007/hr) |
| 2GB | 2 Cores | 80GB | 4TB | $10/mo ($0.015/hr) |
| 3GB | 2 Cores | 100GB | 6TB | $15/mo ($0.022/hr) |
| 4GB | 4 Cores | 120GB | 8TB | $20/mo ($0.030/hr) |
| 6GB | 4 Cores | 160GB | 10TB | $30/mo ($0.045/hr) |
| 8GB | 4 Cores | 180GB | 12TB | $40/mo ($0.060/hr) |
| 16GB | 8 Cores | 260GB | 14TB | $80/mo ($0.119/hr) |
Premium VPS
- Top speeds, low price, generous disk and egress + IPv4 included
- Latest Xeon, DDR4 and NVMe Drives, fastest
- Balanced cost/higher performance
Starting at $14/mo
Storage VPS
- Great for large storage applications
- Join multiple together for redundancy
Starting at $4/mo
Dedicated CPU VPS
Use Cases & Why It Fits
Perfect for a wide range of applications and workloads
2vCPU / 3GB: Usually enough if you're managing a handful of apps with light/medium traffic. The RAM gives you headroom for Node/PHP-based apps plus a small database.
4vCPU / 8GB: Makes sense if you'll host many apps, need smoother builds/deployments, or expect spikes — more CPU improves Docker image builds and parallel deploys.
Control Panels
2vCPU / 3GB: Works well for running these control panels + a few apps. Great for agencies or devs managing client sites.
4vCPU / 8GB: Better if you're hosting heavier stacks (e.g. multiple WordPress + DB + caching + monitoring), since management panels can consume RAM over time.
2vCPU / 3GB: Solid for static React sites or light traffic.
4vCPU / 8GB: Better for SSR/Next.js or higher concurrency.
Backend (Node.js API + Postgres)
2vCPU / 3GB: Good for MVPs, testing, or low-traffic apps.
4vCPU / 8GB: Recommended for production use, more API calls, and heavier Postgres workloads.
Automation & AI
2vCPU / 3GB: Fine for light automation workflows or a few users.
4vCPU / 8GB: If workflows grow complex, run in parallel, or integrate many APIs. OpenWebUI (depending on model use) especially benefits from more RAM.
Coding Systems
AI-powered coding assistants and CLI tools
2vCPU / 3GB: Acceptable if these are run as command-line dev tools, mainly serving one user.
4vCPU / 8GB: Preferred if you're running them continuously in a shared environment, compiling often, or using them as hosted coding assistants where concurrency matters.
Docker & Containers
2vCPU / 3GB: Enough to run a handful of containers (e.g., web + db + cache). Good for personal projects or small dev environments.
4vCPU / 8GB: When running heavier stacks, multiple dev environments at once, or services like GitLab that need more resources.
Kubernetes
4vCPU / 8GB minimum recommended for a control-plane node or for any real workloads. With 2vCPU / 3GB you can only do learning/minikube/k3s single-node experiments.
Databases
2vCPU / 3GB: Handles small/medium datasets or dev/test workloads. Enough memory to keep indexes/caches in RAM.
4vCPU / 8GB: Better for production databases with higher concurrency, larger datasets, or when combining DB + app server on the same VM.
Content Management
2vCPU / 3GB: Supports a single mid-sized site or a couple of low-traffic sites with caching enabled.
4vCPU / 8GB: If hosting multiple CMS sites, expect plugins/themes that eat RAM, or need faster PHP/MySQL response under traffic.
2vCPU / 3GB: Enough for personal VPN use, small teams, or light routing. WireGuard and Tailscale are especially efficient.
4vCPU / 8GB: If you're routing many users, doing site-to-site mesh networking, or using OpenVPN (heavier on CPU for encryption).