Hexo hosting on a VPS — from €5.49/mo
Launch your Hexo blog in minutes — a light Node.js server on NVMe, with a 5-hour test period before payment, completely risk-free
Launch a Hexo blog
A Hexo VPS is a virtual server for a static blog generated by Hexo, which runs on Node.js. The requirements are minimal: the entry configuration Standard 1 — 4 vCPU, 4 GB RAM, 50 GB NVMe at €5.49/mo handles both building and serving a blog with hundreds of posts. Nginx serves the finished HTML: no database, no PHP, almost no load — which is where the speed and resilience to traffic spikes come from. Node.js is needed only at build time. A 5-hour test period before payment lets you compile your theme and verify the deploy. The full line-up is on the VPS hosting page; the general approach is covered in VPS for static sites.
Plans
VPS for Hexo
A personal Hexo blog fits on Standard 1 — 4 vCPU, 4 GB RAM, 50 GB NVMe at €5.49/mo. A large site with thousands of posts and a media library takes Standard 2 (6 GB, 60 GB) at €6.99/mo: it is the images that fill the disk, not the HTML. 5-hour test period before payment.
Compare all plansStandard 1
| 4 vCPU · AMD EPYC |
| 4 GB RAM |
| 50 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Standard 2
| 4 vCPU · AMD EPYC |
| 6 GB RAM |
| 60 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Node.js for builds
Install the Node.js and npm version you need — Hexo, themes and plugins compile right on the server.
Static files, real speed
The finished site is served by Nginx as static files from NVMe: pages open instantly and the load stays close to zero.
Git deploys and control
Root access, KVM and SSH: set up Git deploys, automatic builds and caching to match your workflow.
How to launch a Hexo blog
Choose a plan and image
Decide how many resources your blog needs and select an OS image (Ubuntu, Debian and others).
Install the OS
You deploy the operating system from the chosen image yourself — the environment stays fully under your control.
Set up Hexo and Nginx
Over the KVM console or SSH, install Node.js, Hexo and Nginx, build the site and configure deploys from Git.
Why host a static blog on your own VPS
Hexo generates static pages: no database and no heavy backend — the site is fast, shrugs off traffic spikes and is far less exposed to attacks, because there is simply nothing to break into.
Your own VPS gives you control over the environment: any Node.js version, your own plugins, automatic builds from Git, caching and SSL your way. If Ruby or Go suits you better, there is a VPS for Jekyll and Hugo; configurations and prices are compared on the VPS plan comparison page.
Ask a questionFrequently asked questions
Didn't find your answer?
Write to us via the contact page.
Yes, a Hexo blog builds and serves on 4 vCPU and 4 GB — Standard 1 at €5.49/mo. Even hundreds of posts open instantly, because it is pre-built static HTML with no database.
Yes, but only for builds: Hexo is written in Node.js, and you install the version yourself via nvm. After the build Nginx serves the site, and Node plays no part in serving it.
Via the hexo deploy command or a server-side hook: a push to the repository triggers the build and refreshes the static directory. The script is set up once and then runs by itself.
Hexo runs on Node.js, Jekyll on Ruby, and both produce the same kind of static output. The choice usually comes down to which ecosystem of plugins and themes you prefer.
Via Nginx, pointing the root at the public directory with the finished HTML. Enable HTTP/2, gzip and caching — that is all; no application needs to run behind the web server.
Yes — then only the finished public folder goes to the server, and Node.js is not needed there at all. Building on the server is handier when you publish from several devices.
You choose an image and deploy the system from the panel yourself. Besides SSH there is a KVM console — hardware-level access for installing and reinstalling the OS.
Yes. As the blog grows, you move to a bigger configuration — from Standard 2 at €6.99/mo and up — without migrating the site by hand.