Node.js hosting in Saudi Arabia — your app running in Riyadh, without running a server

The gap between "it works on my laptop" and "it is live"

Most Node.js projects that small teams in Saudi Arabia build are not huge. A REST API for a mobile app. A webhook that receives payment or delivery notifications. The backend of a WhatsApp or Telegram bot for a restaurant chain. A booking widget that a clinic in Khobar embeds on its website. The code takes a week; putting it online used to take a server.

A server means choosing a Linux image, installing Node, writing a process-manager config, setting up a reverse proxy, issuing a certificate, remembering to renew it, and watching memory at two in the morning. For an agency that delivers dozens of such projects a year, that administration costs more than the hosting itself. Hosting that runs Node.js removes that layer: you bring the app, the panel does the plumbing.

A minimal app that is ready to deploy

Express, listening on the right port

// app.js   (npm install express)
const express = require('express');
const app = express();

app.get('/health', (req, res) => res.json({ ok: true, city: 'Riyadh' }));

app.listen(process.env.PORT, () => {
  console.log('listening on', process.env.PORT);
});

Settings in a .env file

Create .env in the app folder. Each line becomes an environment variable for the app, so there is no need for an extra package to load it.

NODE_ENV=production
DATABASE_URL=postgres://acme_api:the-password-shown-once@127.0.0.1:5432/acme_api
PAYMENT_WEBHOOK_SECRET=change-me

Talking to the database

// npm install pg
const { Pool } = require('pg');
const pool = new Pool({ connectionString: process.env.DATABASE_URL });

app.get('/orders/:id', async (req, res) => {
  const { rows } = await pool.query('SELECT * FROM orders WHERE id = $1', [req.params.id]);
  res.json(rows[0] ?? null);
});

The database lives on the same server, so the host is always 127.0.0.1. PostgreSQL 16 and MySQL are both on every plan — see PostgreSQL hosting in Saudi Arabia for the one-click setup.

The limits, in one table

An agency example

A Riyadh agency hosts a client's Arabic-English company site on WordPress. The client now wants a branch-locator API for its new app. The agency adds a Node.js app at /api on the same website, stores the branches in a PostgreSQL database on the same plan, and puts the map provider's key in .env. No new server, no new invoice line, and the client's data stays in the Kingdom.