Server Selection Hub: VPS, Dedicated, Bare Metal — a Decision Tree That Sticks

# What this hub decides for you VPS / dedicated / bare metal / GPU without regret — along three axes: budget, workload shape, traffic model. This page is the master entry for all selection content on the site: decision tree and comparison table first, then pre-purchase checks and myth-busting; every sub-topic's conclusion flows back here. ## Quick decision block - Budget < $15/mo → entry VPS tier (from $5.34/mo) - Need exclusive physical resources / compliance audit → dedicated (dual E5-2620v2 from $70.80/mo) or bare metal - Multi-site operations → multi-IP dedicated (25-IP tier $190.80/mo) - China-direction business → fix the line before the box (routing hub) - Database / high IO → NVMe > SSD > HDD, and RAM rather too much than too little ## Four forms in one table | Form | Resource ownership | Delivery | Monthly order | Typical use | |---|---|---|---|---| | VPS | virtual slice of a physical box (KVM etc.), guaranteed share | minutes | $5–50 | personal sites, dev/test, light APIs | | Cloud host | elastic VPS: metered scaling, dedicated vCPU options | minutes | metered | spiky traffic | | Dedicated server | one whole physical machine | hours–days | from $70 | heavy load, game servers, databases, compliance | | Bare-metal cloud | whole machine + cloud console (self-reinstall, minutes) | minutes | from $160 | teams wanting both performance and agility | ## VPS vs dedicated vs cloud host (buyer's guide) The essential differences are **exclusivity** and **delivery speed**. Decision order: first, does the workload need exclusive CPU/RAM or a fixed hardware fingerprint (yes → dedicated or bare metal)? Second, can the budget absorb $70+/mo (no → VPS)? Third, do you need elastic expansion and self-service delivery (yes → cloud host or bare-metal cloud)? VPS savings come from the shared base: host CPU and bandwidth are split among neighbours, and cheap tiers can interfere at peak — verify real compute with benchmarks and peak-hour behaviour, never with promised core counts. Live configs and prices live on the products page; promo tiers in the promotion category. ## Pre-purchase checklist (six items, in order) 1. **Contract & refunds:** pro-rata or daily? trial length? processing fees? Read this before paying. 2. **AUP:** are PBNs, mail marketing, proxy businesses allowed? Crossing the line usually means termination without refund. 3. **Network promises:** dedicated or shared bandwidth? overage throttled or billed? CN2/CMI-class lines available (cross-check in the routing hub)? 4. **Delivery time:** VPS minutes, dedicated hours-to-days; urgent projects ask about stock before paying. 5. **IP reputation:** is the new IP clean (ask for a swap or check blocklists first)? Mail businesses are especially sensitive. 6. **Backup strategy:** snapshot/backup add-ons offered? how many copies? how often is restore rehearsed? ## Windows vs Linux VPS Linux wins by default: no GUI or licence overhead (usable RAM at equal specs is visibly higher — confirm with `free -h` at acceptance), mature ecosystem (Nginx/Docker/panels). Windows Server only when you truly depend on .NET Framework, SQL Server, RDP habits or specific Windows software — and expect the licence surcharge. Beginner path: Linux + panel, paired with the "Internet from Zero · L1" course. ## Cheap-VPS traps (myth busting) - **"Unmetered traffic":** almost always carries a FUP; overage throttles to unusable. Ask what happens past the line. - **"Dedicated bandwidth":** cheap tiers are usually shared-base; evening peak shrinks it. Verify via the diagnostics hub. - **"Oversubscribed CPU":** `lscpu` core counts are commitments; real throughput depends on host oversubscription. sysbench plus peak-hour behaviour is the only evidence. - **"First month $1":** check renewal price and minimum term; is the annual discount refundable? - **"Free backups":** copies kept? restore SLA? A backup never rehearsed is a backup you don't have. ## Three budget tiers, landed - **$5–10/mo (entry VPS, e.g. $5.34):** 1–2C 1–2G — blog, résumé site, small API, learning. Correct expectation: stable, not elastic. Pair with free CDN + static hosting to lift origin pressure. - **$20–50/mo (growth):** 2–4C 4–8G — corporate site with thousands of daily users, small WooCommerce, team Git/wiki. Start preparing DB/web separation: split services on the box first, split machines when it grows. - **$70+/mo (dedicated, e.g. dual E5-2620v2 $70.80):** whole machine for game servers, mid-large databases, multi-site matrices (25-IP PBN tier $190.80). The money buys "sharing with nobody": no CPU contention, no IO neighbours, fixed hardware fingerprint — compliance audits land here. Migration between tiers is routine: vertical VPS resize in minutes; VPS→dedicated via a low-TTL cutover (DNS hub). What to avoid is "buy the big box upfront" — idle capacity on an unloaded machine is pure daily loss. ## Channel myths Direct operator vs reseller differs not in price list but in after-sales chain: who answers tickets, whose refund process runs, who can act on-site for IP/hardware issues. Test with one concrete technical question before ordering ("what is this machine's test IP?", "what is the evening-peak return path?") — a channel that answers directly is a channel that owns the stack.