Skip to main content

Developer hosting

Node.js Hosting on SteboHost

Node runtime with process management, SSL and logs — run Express, Fastify, NestJS or any Node app.

  • Git push to deploy
  • Build & deploy logs
  • Health checks
  • One-click rollback

Node.js Hosting

Node.js hosting provides a managed runtime for server-side JavaScript applications. Unlike static hosting or generic PHP environments, a proper Node.js setup requires a persistent process that stays alive between requests, a process manager that restarts the process on crash, and a reverse proxy that terminates SSL and forwards traffic. SteboHost handles all of this so you can focus on application code rather than process supervision. This hosting is built for developers running Express, Fastify, NestJS, Hapi or any framework that produces a Node.js server. It covers REST APIs, WebSocket servers for realtime features, microservices that each run as their own environment, and SSR frameworks like Nuxt and Remix that need a running Node process for server-side rendering. What sets SteboHost apart is the process management layer. Your processes run as systemd units with Restart=always and RestartSec=1, so a crashed worker is restarted within one second, and cgroup memory limits (MemoryMax) are enforced per unit from your plan. Logs stream from journald to the portal with level filters and keyword search, CPU and memory metrics are collected every minute, and you configure the number of worker processes per environment up to your plan's memory budget. The reverse proxy upgrades HTTP to WebSocket automatically, so realtime features work without additional configuration. Package manager detection is automatic — we read your lockfile and use npm, pnpm or yarn accordingly.

What is included

Everything you need to run and deploy

Each feature is part of the product — not an add-on or an upsell.

Managed Node.js LTS runtime

systemd-supervised processes with one-second restart on crash

Automatic SSL certificates on custom domains

Logs streamed from journald with level filters and keyword search

Git-based deployment with build logs

Environment variables encrypted at rest

NPM or pnpm install during build

One-click rollback to any previous release

WebSocket support on all plans

Node.js 18, 20 and 22 LTS support

Worker scaling up to your plan memory budget with live usage

CPU and memory metrics collected every minute

Why Node.js Hosting

Why developers choose SteboHost for node.js hosting

Specific reasons — not generic marketing claims.

Automatic package manager detection

We read your lockfile — package-lock.json, pnpm-lock.yaml or yarn.lock — and use the correct package manager during the build. No configuration needed, and switching from npm to pnpm is as simple as committing a new lockfile.

Realtime WebSocket support

The reverse proxy upgrades HTTP connections to WebSocket automatically on every plan. You can run Socket.io, ws or any WebSocket library without special configuration or port forwarding.

systemd supervision with one-second restarts

Each process runs as a systemd unit with Restart=always and RestartSec=1, so a crashed worker is back within one second. cgroup memory limits (MemoryMax) are enforced per unit from your plan, preventing leaks from taking down your application or neighbouring environments.

TypeScript build pipeline

If your project includes a TypeScript build step, we run it automatically during deployment. The compiled JavaScript output is what runs in production, so your source TypeScript never needs to be on the server.

Streaming logs in the portal

Application logs stream from journald to the portal in real time. You can filter by level, search by keyword and download logs for offline analysis without SSH access.

How it works

From repository to production in five steps

The deployment workflow, end to end — visible, automated and reversible.

1

Connect your repository

Link your GitHub, GitLab or Bitbucket repository. We read your package.json to detect the framework, entry point and start script. The Node.js LTS version is selected based on your engines field or portal setting.

2

Build and install

On every push, we install dependencies using the package manager detected from your lockfile, then run your build script if one is defined. Build logs stream in real time so you can watch compilation and catch errors.

3

Process starts under systemd

The compiled application starts as a systemd unit with the worker count you configured. systemd supervises the process, restarts it within one second of a crash, and stdout and stderr stream to journald and then to the portal.

4

Reverse proxy serves traffic

The reverse proxy terminates SSL, forwards HTTP traffic to your Node process and upgrades WebSocket connections automatically. Health checks poll your application every 60 seconds to confirm it is responding.

5

Rollback on failure

If a release causes errors, click rollback in the portal. systemd stops the current workers and starts the previous release immediately. No rebuild is needed — the previous build output is retained on disk.

Use cases

What people build with Node.js Hosting

Common workloads our customers run on this stack.

REST APIs

Express, Fastify or NestJS APIs with CORS, rate limiting and JWT authentication. systemd keeps workers alive under load with one-second restarts, and the journald-backed log stream lets you trace request latency and errors in real time without a separate APM tool.

Realtime apps

WebSocket servers for chat, notifications and live dashboards with persistent connections. The reverse proxy handles the HTTP-to-WebSocket upgrade automatically, so Socket.io and ws work without additional configuration on any plan.

Microservices

Container-friendly Node microservices with health checks. Each microservice runs as a separate environment with its own worker count, environment variables and journald log stream, and each release pipeline stays independent.

SSR frameworks

Nuxt, Remix and custom SSR Node apps with server-side rendering and hydration. The Node process handles rendering on every request, and systemd restarts it within one second if a memory leak in the SSR layer crashes the process.

Developer plans

Transparent pricing, honest limits

Every plan publishes its exact resources. No burst limits buried in a footnote.

Dev Launch

For side projects and portfolios

KES 19,188 /year

  • 3 applications
  • 10 GB storage
  • 500 build minutes
  • 2 environments
  • Git deploy
  • SSL included
Choose Dev Launch
Most popular

Dev Build

For production apps with CI/CD

KES 35,988 /year

  • 10 applications
  • 30 GB storage
  • 2,000 build minutes
  • 5 environments
  • Git deploy
  • SSL included
  • Staging + production
  • Priority support
Choose Dev Build

Dev Team

For teams and agencies

KES 71,988 /year

  • 50 applications
  • 100 GB storage
  • 10,000 build minutes
  • 20 environments
  • Git deploy
  • SSL included
  • Staging + production
  • Priority support
  • Team collaboration
Choose Dev Team

Performance

Built for speed, not benchmarks

Concrete performance guarantees — not vague promises.

Worker scaling within your memory budget

Scale worker processes up to your plan's memory budget from the portal — live budget usage and scaling history are shown as you adjust. Each worker runs as its own systemd unit with a cgroup memory limit, and connections are distributed across all workers. Scaling is multi-worker within one server; multi-server load balancing is planned for a later phase.

CDN caching for static assets

Static files served by your application — images, CSS, prebuilt JavaScript — are cached by the built-in CDN layer. Fingerprinted assets get immutable cache headers, and the cache is purged automatically on every deploy, reducing load on the Node process for static requests.

Response-time metrics

Uptime and response-time metrics are collected for every environment and visible in the portal, alongside CPU and memory usage sampled every minute. Trends in response time surface slow endpoints and regressions before they become outages during traffic spikes.

Health-check monitoring

A configurable health endpoint is polled every 60 seconds. If the application stops responding or returns errors, systemd restarts the process and alerts you, reducing mean time to recovery without manual intervention.

Security

Security is included, not optional

SSL, isolation, backups and monitoring — on every plan.

Automatic SSL termination

SSL certificates are provisioned and renewed automatically on every custom domain. The reverse proxy terminates SSL before forwarding to your Node process, so your application code does not need to handle certificate files or renewal logic.

Web application firewall with the OWASP Core Rule Set

The built-in web application firewall protects every deployment with the OWASP Core Rule Set — SQL injection, XSS and brute-force protection in detection or prevention mode, with per-deployment custom rules and a blocked-request log in the portal. For DDoS absorption at the network edge, put Cloudflare in front of your domain.

Encrypted environment variables

Environment variables — API keys, database URLs, secrets — are encrypted at rest and injected at runtime. They are never written to disk in plaintext, never exposed in logs and never visible to other environments on the same server.

Process isolation

Each Node.js environment runs in its own container with isolated filesystem and process space, and cgroup limits keep one environment from starving another. Environment variables are never visible to other environments on the same server.

Migration

Migrating to SteboHost

Move your existing application without downtime or data loss.

From Heroku or Render

If you are moving from Heroku or Render, your Procfile and start script work as-is. Set your environment variables in the portal, connect your repository and push. The build and start commands are detected automatically.

From a VPS with PM2

If you are running PM2 on a raw VPS, point your repository at SteboHost and systemd takes over the process management. Your ecosystem.config.js worker settings translate directly into portal worker counts and cgroup memory limits.

DNS and SSL cutover

We provision SSL on your domain before you switch DNS, ensuring the new endpoint is secure and working. Our support team assists with the DNS cutover timing to minimise downtime during the transition.

Free migration support

Contact support@stebohost.com or call +254 703 610 464 for migration assistance at no extra cost. We help with environment variable setup, build configuration and DNS cutover, and verify everything works before you cancel your old provider.

Node.js Hosting FAQ

Node.js Hosting questions, answered

The details that matter when choosing a hosting provider.

We support Node.js 18 LTS, 20 LTS and 22 LTS. You can select your Node version per environment from the portal or set it in your package.json engines field. Switching versions does not require downtime — the change takes effect on the next deploy.

Ready to deploy your node.js hosting app?

Tell us your stack and we will get you from repository to production — usually within a day.