From Home Server to Cloud Run
HTML + Node.js/Express → Naver Cloud → Google Cloud Run
A handful of small web tools I've built, including khz.kr, have moved through three different hosting setups as the needs — and the constraints — changed.
The journey
- Home server — the first version of everything ran on a plain HTML frontend with a Node.js/Express backend, hosted on a server sitting at home. No cloud provider involved — just enough stack to serve real traffic.
- Naver Cloud Platform — moved off the home connection onto a small, always-on VM instance, borrowed for about $20 a month. That's a flat fee whether the services on it get real traffic or sit idle, which most small side projects do most of the time.
- Google Cloud Run — moved again for the economics: each service is now its own container that scales to zero when nobody's using it and bills for actual usage, not uptime. Same lineup of services, running for a fraction of a fixed server's cost.
khz.kr
One of the services riding on this setup is khz.kr — practice tools for electric guitar and bass: scale and chord charts across the neck, a tab composer, a metronome, and a drum machine, all running in the browser.