Node.js Hosting
Deploy Node apps without a VPS
Express, Next.js, NestJS or a plain HTTP server — push your code, pick the entry file, and we keep it running behind HTTPS.
The gap between "it works locally" and "it is online"
Running Node in production normally means renting a VPS, installing a process manager, writing an nginx config and remembering to restart things after a reboot. That is a lot of work to put one API online.
Here you point us at a folder and an entry file. We install your dependencies, run the app under systemd so it restarts on crash and on boot, and put it behind nginx with a real certificate.
Node.js Hosting
What you get
Git or upload
Clone straight from a repository, or upload a zip and extract it in the browser.
Dependencies handled
npm install runs for you on every deploy, including build steps for framework projects.
Kept alive
Managed by systemd — restarted if it crashes, started again after a reboot.
Your domain, HTTPS
Bind an app to any domain you own and get a free certificate for it.
Build-step aware
Vite, Next, Nuxt, Astro and SvelteKit are detected and built before they are served.
Diagnose button
If an app will not start, the panel reads the logs and explains why in plain language.
How it works
- 1Upload or git-clone your project into your account.
- 2Create an app: runtime Node, app root, entry file, domain.
- 3We install dependencies, build if needed, and start it.
- 4Issue SSL and your API or site is live.
Where it runs
On our own hardware, inside Nepal
Not a reseller account on someone else's platform. Your Node.js workload runs on machines we own and operate in Kathmandu — which is why the round trip below is what it is.
- NVMe storage on every plan
- Isolated account per customer, at the OS level
- Nightly backups you can restore yourself
Typical round-trip a visitor inside Nepal sees, by server location. Your results will vary by network and route.
Read the port we give you
We assign the port and pass it in as PORT. An app with a hardcoded port starts fine but nginx cannot reach it, so your domain shows the placeholder page instead of your site.
// We set PORT in the environment — always read it.
const port = process.env.PORT || 3000;
app.listen(port, () => {
console.log('listening on ' + port);
});While you are there
Your package.json needs a real start script — "start": "node server.js". Frameworks that ship their own config (ThinkJS, some Nest setups) may hardcode a port in a production config file; that file wins, so check it too.
If a deploy still will not come up, the panel reads the service log and explains the cause in plain language — you do not have to interpret systemd output yourself.
Under the hood
- Runtime
- Node.js LTS
- Process manager
- systemd, auto-restart on crash and boot
- Frameworks
- Express, Next.js, NestJS, Nuxt, Astro, SvelteKit and more
- Reverse proxy
- nginx with free SSL
- Logs
- Readable from the panel, with an AI diagnose helper
Plans
Plans are being updated — see all hosting.
Common questions
Which port should my app listen on?+
Read process.env.PORT. We assign the port and pass it in; a hardcoded port cannot be reached by your domain.
Can I run a background worker?+
Yes, either as a second app or as a cron job, depending on whether it needs to run continuously.
Do you support WebSockets?+
Yes. The proxy is configured to upgrade connections.
Ready when you are
Set up in minutes, with support from people in your timezone.