Nineteen hosting locations in four markets. Korea carries primary hosting — Chuncheon and Seoul — with Japan, Hong Kong and Singapore serving cached copies.
Primary hosting sits in Chuncheon and Seoul: two independent fibre entries, generator-backed power and enough cooling headroom that a heatwave is not an incident. Japan, Hong Kong and Singapore run edge caches, so a buyer in Osaka or Singapore gets the page from a nearby machine rather than from Seoul.
Seoul ×3, Chuncheon, Busan, Incheon, Daegu, Daejeon.
Tokyo ×2, Yokohama, Osaka, Nagoya, Fukuoka.
Kwai Chung, Tseung Kwan O, Chai Wan.
Tai Seng and Jurong, both carrier-neutral.
Uplink figures are port capacity, not a bandwidth allowance. Each location is monitored separately on the status page.
| Location | City | Country | Facility | Role | Uplink | Live since | Status |
|---|---|---|---|---|---|---|---|
| KR-Chuncheon-01 | Chuncheon | South Korea | Chuncheon IDC (Gangwon) | Primary hosting | 2 × 10G | 2023-11 | Operational |
| KR-Seoul-01 | Seoul | South Korea | Gasan IDC | Primary hosting | 2 × 10G | 2021-03 | Operational |
| KR-Seoul-02 | Seoul | South Korea | Gasan IDC (hall B) | Secondary / DR | 2 × 10G | 2025-02 | Operational |
| KR-Seoul-03 | Seoul | South Korea | Sangam | Edge cache | 1 × 10G | 2024-06 | Operational |
| KR-Busan-01 | Busan | South Korea | Busan IDC | Edge cache | 1 × 10G | 2022-09 | Operational |
| KR-Incheon-01 | Incheon | South Korea | Incheon DC | Edge cache | 1 × 10G | 2023-04 | Operational |
| KR-Daegu-01 | Daegu | South Korea | Daegu DC | Edge cache | 1 × 10G | 2024-10 | Operational |
| KR-Daejeon-01 | Daejeon | South Korea | Daejeon DC | Edge cache | 1 × 10G | 2024-03 | Operational |
| JP-Tokyo-01 | Tokyo | Japan | Otemachi | Primary hosting | 2 × 10G | 2021-11 | Operational |
| JP-Tokyo-02 | Tokyo | Japan | Shinjuku | Secondary / DR | 1 × 10G | 2024-05 | Operational |
| JP-Yokohama-01 | Yokohama | Japan | Yokohama DC | Edge cache | 1 × 10G | 2025-04 | Operational |
| JP-Osaka-01 | Osaka | Japan | Namba | Edge cache | 1 × 10G | 2022-06 | Operational |
| JP-Nagoya-01 | Nagoya | Japan | Sakae | Edge cache | 1 × 10G | 2023-08 | Operational |
| JP-Fukuoka-01 | Fukuoka | Japan | Hakata | Edge cache | 1 × 10G | 2023-02 | Operational |
| HK-KwaiChung-01 | Hong Kong | Hong Kong SAR | Kwai Chung | Edge cache | 1 × 10G | 2022-01 | Operational |
| HK-TseungKwanO-02 | Hong Kong | Hong Kong SAR | Tseung Kwan O | Edge cache | 1 × 10G | 2024-08 | Operational |
| HK-ChaiWan-03 | Hong Kong | Hong Kong SAR | Chai Wan | Edge cache | 1 × 10G | 2025-06 | Operational |
| SG-TaiSeng-01 | Singapore | Singapore | Tai Seng | Edge cache | 1 × 10G | 2022-03 | Operational |
| SG-Jurong-02 | Singapore | Singapore | Jurong | Edge cache | 1 × 10G | 2024-12 | Operational |
Live latency for every location is on the status page. Clients can benchmark their own site from the site check.
No mystery box. This is the stack, and you can ask us to change any part of it.
nginx with HTTP/2 and HTTP/3, PHP-FPM or Node depending on the build, per-site resource limits so one client cannot slow another.
CDN in front of every site, per-site cache rules, instant purge via the portal, and image resizing at the edge.
Managed WAF rule set, rate limiting, bot filtering and DDoS absorption. Rules are reviewed after every incident.
Encrypted database storage, daily offsite snapshot with 30-day retention, monthly restore test with a written result.
Staging environment per site, deploy log in the portal, rollback in one click, maintenance windows agreed 72 hours ahead.
Synthetic checks every 60 seconds from three regions, real-user Core Web Vitals, alerting to our on-call engineer.
Thirty minutes on a call, screens included. No slide deck.