Cloud servers · models and regions

State the workload first,
then the cores and bandwidth

A cloud server is not better for being cheap, nor stabler for more cores. Fix the site type, concurrency and filing need first, then the model and region follow. Setup is self-service: about three minutes.

Site and load Pick the model Pick a region Install and run

Five misreadings about cloud servers

All of them start with buying before thinking, and all show up once traffic arrives.

What people say

  • One core and 1GB is enough
  • More bandwidth is always faster
  • A Hong Kong box means compliant
  • Cloud servers are just VPS
  • Backups are the provider job

Reality

  • Cores cap concurrency; one core cannot run a database site
  • Bandwidth is egress only; memory and disk IO bite first
  • Offshore eases access, compliance still follows the business
  • Cloud gives snapshots and live resizing; a VPS rarely does
  • The provider keeps the box up; your data needs your own plan

Four models, entry to luxury

Model names are bundles, not limits. CPU, memory, disk, bandwidth and defence all adjust online at any time.

Feature
Entry 1 core · small sites ¥79/mo
Recommended Standard 2 cores · corporate sites Priced by config
Business 4 cores · database workload Priced by config
Luxury 8 cores · high concurrency Priced by config
Typical use Personal, staging Corporate, app backend Shops or booking with a DB Many sites, high concurrency
CPU 1 core 2 cores 4 cores 8 cores
Memory 1–2G 2–4G 4–8G 8–32G
System disk 40G SSD up 40G SSD up 70G SSD up 70G SSD up
Bandwidth 1–5M 3–10M 5–20M 10–100M
Defence 30G up 30G up 50G up 100G up
Monthly ¥79 By config By config By config
Live resize Yes Yes Yes Yes
Snapshots Yes Yes Yes Yes
Regions Any of the six Any of the six Any of the six Any of the six

Up to 16 cores, 32G memory, 500G disk, 100M bandwidth and 500G defence. Only entry has a public price (¥79); others quote by config.

Six regions we use most

The region sets latency and whether filing is needed, but the network path matters more than the city.

Central BGP multi-line

One IP across all three carriers; no detours for mixed audiences.

Shanghai Telecom · 10G

Dedicated IP with 10G protection, best for East China traffic.

Hong Kong

No filing needed; nearest for HK, Taiwan and Southeast Asia.

Hong Kong CN2

Filing-free plus CN2 back to the mainland, low latency both ways.

Tokyo

Low latency for Japan and East Asia, filing-free as well.

Los Angeles / Washington

CN2 direct at about 130–160ms, for North American and export sites.

Against a VPS or a dedicated box

All three host a site; they differ in provisioning, change cost and failure surface.

Feature
Cloud host Fast setup, live changes By config
VPS Shared host, manual setup By config
Dedicated Whole box, manual racking Per box
Provisioning About 3 minutes Manual, about an hour Manual, about 1 day
CPU and RAM About a minute Often a rebuild or swap Stop and add hardware
Password reset About a minute Depends on the panel Ask the datacentre
OS reinstall About 3 min Depends on the panel Manual reinstall
Snapshots About fifteen seconds Usually none Build your own
Network security IP/MAC binding, 10G Depends on the host Bare metal, do it yourself
Entry monthly From ¥79 Tens to hundreds From about a thousand

A cloud box wins on fast setup and fast changes; a VPS or dedicated box leans on people. Sustained high load favours a dedicated server.

Four steps to go live

From stating the workload to monitoring, usually within the same day.

01

Model by workload

Site type, daily visits and whether it runs a database decide the model.

Model by workload
02

Region and path

Where your visitors are and whether filing is needed pick the region.

Region and path
03

Install the system

Pick the image, partitions and initial password; reinstalls stay free.

Install the system
04

Monitor and back up

Resource charts, alerts and scheduled snapshots set once, then sleep.

Monitor and back up

Before you buy

Five things to accept first

A cloud server is cheap because it is shared and self-service, and that is also the cost. Align on these before ordering.

  • Model names are bundles, not limits: cores and memory adjust online
  • Bandwidth is metered at peak; spiky sites need headroom
  • Filing-free only solves access; content rules follow the business
  • A snapshot is not an offsite backup; a box failure takes both
  • The entry model carries no SLA; put critical work higher
Describe workload

Tell us the site and the workload

Send the site type, daily visits, whether it runs a database and whether you need filing. We will size the model and region, and outline how to scale later.

  • Estimate daily visits on a normal day and give the peak if a campaign is planned. A database, a control panel or several sites raise memory needs, so say so up front.
CAPTCHA image