One push. Every region.
See the difference now.
Sebelum · sesudah
Lihat sendiri selisihnya.
Simulasi deploy ke 9 node. Kiri: tanpa Node Sync (SSH manual, build per node, serial). Kanan: dengan Node Sync (build sekali, rsync paralel, restart serempak).
Tanpa Node Sync
SSH manual, satu node satu waktu
0/9
- sgp1(Singapore)idle
- nrt1(Tokyo)idle
- itm1(Osaka)idle
- bom1(Mumbai)idle
- syd1(Sydney)idle
- fra1(Frankfurt)idle
- lax1(Los Angeles)idle
- ord1(Chicago)idle
- ewr1(New York)idle
XessOne Node Sync
Build sekali, rsync paralel
0/9
- sgp1(Singapore)…
- nrt1(Tokyo)…
- itm1(Osaka)…
- bom1(Mumbai)…
- syd1(Sydney)…
- fra1(Frankfurt)…
- lax1(Los Angeles)…
- ord1(Chicago)…
- ewr1(New York)…
Menjalankan simulasi…
~9m
→~30s
18× lebih cepatSimulasi. Nilai real bervariasi tergantung ukuran build + bandwidth tiap node.
Active on every tier · the more nodes, the more value you feel.
How it works
Build once, rsync many.
01
Build on sgp1
Git push or drag & drop. The master node builds Next.js / Astro / static via Bun + auto framework detection. Once.
02
Parallel rsync
Transfer `.next/` + `public/` to every active edge simultaneously. No per-node rebuild — 9× efficient.
03
Synchronized restart
`systemctl restart xessone-web` on every edge. Caddy keeps serving old requests until Next starts — zero-downtime.
04
Verify probe
HTTP HEAD probe to each node. Failures are auto-rolled back, you get a notification of which node broke.
Deploy once, live everywhere.
Node Sync is on every tier. Trial first, pay when it fits.
