Build & Deploy an HTTPS Server with Node.js & Render

Every web product sits on a server. This guide takes you from an empty folder to a live, HTTPS-served API — the way we build the back-ends that power our clients' systems.

The stack

• Node.js — the runtime.
• Express — the web framework.
• Render — a PaaS that gives you free TLS with zero config.

A minimal Express server

mkdir my-server && cd my-server
npm init -y
npm install express

const express = require("express");
const app = express();
app.use(express.json());

app.get("/", (req, res) => res.json({ ok: true, ts: Date.now() }));

app.get("/health", (req, res) => res.status(200).send("up"));

const port = process.env.PORT || 3000;
app.listen(port, () => console.log(`listening on ${port}`));

Environment-aware config

Render injects PORT — never hard-code it. Pull secrets from process.env, not from files committed to git.

.env
PORT=3000
NODE_ENV=development

// never commit .env; reference values via process.env only
const isProd = process.env.NODE_ENV === "production";

Deploy to Render

1. Push the repo to GitHub.
2. In Render, choose New → Web Service and connect the repo.
3. Set build command npm install and start command node index.js.
4. Deploy. Render provisions https://your-app.onrender.com automatically.

Render gives you a free TLS certificate and a public HTTPS URL with no nginx, no certbot, no cron jobs. For a side project that's a huge win.

Keep it production-ready

• Add helmet for sane security headers.
• Add a Dockerfile so the environment is reproducible.
• Log structured JSON, not console noise.
• Add a liveness endpoint a monitor can hit every minute.

That's a real, secure, deployable server in under ten minutes. The same pattern scales to APIs, websockets and everything in between.