--- title: "Building a Personal Homepage Server: Why I Wandered Around Looking for a VPS That Accepts Bank Transfers" date: 2026-10-11 time: "21:30" model: admin category: setups author_type: human summary: "Wanting to pay server costs by bank transfer instead of auto-charged credit cards, I compared YourIT and EggHosting. A record of the actual server selection, weighing specs, traffic, and payment method together." tags: server,VPS,homepage,bank-transfer,account-transfer,YourIT,EggHosting,traffic,nginx,server-selection --- # Building a Personal Homepage Server: Why I Wandered Around Looking for a VPS That Accepts Bank Transfers Deciding to build a homepage doesn't mean you're done. You need a server to put the site on the internet. At first I thought buying any decent server would do. But once I started looking, there turned out to be a lot more to weigh than I expected. How much spec do I actually need? What does it cost every month? Can it handle traffic from overseas? And how do I pay for it? One condition mattered more to me than the others. **Finding a place where I wasn't dependent on auto-charged credit cards — ideally somewhere I could pay by bank transfer or account transfer.** Here's the story of that search. ## 1. Payment Method Came Before the Server Most cloud services I looked at charged by credit card based on usage. It's convenient. But running a personal site, I wanted direct control over the monthly bill. Especially starting out, unexpected charges are stressful. Compared to having a card on file with ongoing usage billing, I preferred checking the cost each month and paying it myself. So from the very beginning, my criteria were: - A place that accepts bank transfer or account transfer - A monthly cost that isn't a burden - A VPS I can install Linux on and manage with root access - Specs enough to run a personal site and APIs - Somewhere I can predict and manage costs even as traffic grows The goal wasn't finding the cheapest server. It was finding one I could actually run in a way I could afford. ## 2. I Started by Looking at Servers in the 10,000–30,000 Won Range I compared several hosting providers. Two caught my eye: YourIT and EggHosting. The products I compared looked like this: | | YourIT VPS Standard | EggHosting Medium | |---|---|---| | CPU | 4 Core | 2 vCPU | | RAM | 4GB | 4GB | | Storage | SSD 80GB | NVMe 50GB | | Monthly Traffic | 2TB | 300GB | | Listed Price at the time | 18,000 won/month + VAT | 24,000 won/month + VAT | *Prices and specs are from the products I compared at the time and may differ from current offerings.* Just looking at the numbers, the monthly traffic gap stood out as much as the CPU and storage. First-time server buyers often compare only CPU and RAM. But to actually run a site, you need to check storage and traffic too. Especially once you account for overseas AI crawlers visiting the site, it's worth checking how much data transfer is allowed per month. ## 3. How Much Spec Does My Site Actually Need? The site I wanted to run was different from a video service or a heavy image site. It delivered AI knowledge and reviews through Markdown, JSON, and APIs. It needed a database, but serving large video or image files wasn't the point. So I figured there was no reason to spend big on a high-end server from the start. My top candidate was a VPS with 4 cores, 4GB RAM, and an 80GB SSD. Of course, the right specs depend on the stack and the visitor count. If the database grows or image processing increases, you might need more memory and storage. So rather than buying the max spec up front, starting at what the workload actually needed and adjusting as usage grew seemed more sensible. ## 4. What About Traffic from Overseas AI Crawlers? Traffic was another thing that worried me during the search. My site wasn't only for Korean users. It provided AI-related material and had to account for crawlers from overseas AI services. Websites get hit by search engines and automation programs, not just people. And they don't just request one page — they may pull a sequence of related pages and material. So the monthly traffic cap mattered. Even if the server is cheap, overage fees can change the monthly bill I was planning for. So I didn't just look at the monthly fee. I also checked: - Monthly traffic allowance - What happens when you exceed it - Whether speed limits or QoS apply - What triggers extra charges - How to monitor usage The key point: lots of traffic isn't inherently bad. You just need to distinguish real visits from crawl requests and confirm the server can handle it. ## 5. What Actually Mattered Was a Server I Could Manage Myself Comparing all those conditions taught me something. When choosing a server, you don't just look at CPU and RAM. You look at payment method, traffic policy, and administrative control. I didn't necessarily need the most famous cloud service. I needed an environment where I could configure Nginx on Linux, run my site, and check server logs. And I wanted to predict and manage the monthly cost myself. By those criteria, YourIT's VPS Standard stood out. At the time, it offered 4 cores, 4GB RAM, an 80GB SSD, and 2TB of monthly traffic. The ability to pay by account transfer or virtual account was a key factor. Choosing a server wasn't just about picking the biggest numbers on a spec sheet. It was deciding what I'd run, what I could afford, and how I'd manage problems when they came up. ## 6. Once I Had the Server, a Whole New Learning Curve Started Having a server didn't mean I was done running a site. There was always something new to learn: Nginx configuration, HTTPS, API connections, file permissions, checking server logs. At first, the IP addresses and HTTP status codes in the logs were foreign to me. But running the site myself, I needed to see what requests were coming in and what pages were being asked for. Eventually I even built a dashboard to check real-time access records, AI crawler collection records, cumulative stats, and a crawling-by-hour graph. Cutting the monthly cost mattered when choosing the server. But once I started operating, understanding what was happening inside the server mattered just as much. Experiencing it all one step at a time, I came to see a server not as a place to dump homepage files — but as an operating environment I could manage and learn from. ## The Takeaway: You Don't Need an Expensive Server from Day One If you're preparing a personal homepage, you don't need to go straight for high specs or a famous brand. First define what the site is for, then look at the CPU, RAM, storage, and traffic you need. And check not just the monthly fee but the payment method and overage policy. If auto-charged credit cards feel risky, it's worth confirming whether the provider supports account transfer or virtual account payment. I started the same way — looking for a cheap server that met my conditions. I compared providers and built out the features I needed as I ran the site. You don't need everything perfect from the start. Start with a server that fits your purpose and budget, then adjust as you see real usage and real problems. **The most important thing in choosing a server isn't picking the most expensive plan — it's setting up, at a reasonable cost, the environment that fits the site you're actually going to run.**