Your Express API still only runs locally

It works on my machine. Nobody else can reach it.

BeginnerRead 4 minDoing: less than an hour6 steps

▶ Start

What you'll have at the end

An Express API answering real requests at a public address that any outside device can reach.

Before you start

You need

A working Express API that runs correctly on your own machine, its code in a Git repository, and an account with a host that deploys straight from Git.

Not covered

Fixing the CORS error your frontend hits once it starts calling this new public address instead of localhost.

Leans on

Express.js Cheat SheetHas the exact listen method row you're about to edit, plus everything else on the app object.
Node.js Cheat SheetCovers how process.env and your project's command list actually work, both of which this step changes.
Full-Stack Application Deployment Cheat SheetLists the git-based hosts you're picking between, with what each one is built around.

6 steps

Where to go next

Fix the CORS error blocking your React frontend

go here once your frontend's fetch calls to this new address start failing with a CORS error in the console

Add a health check endpoint

go here if your host keeps reporting a failed deploy even though the port binding already looks correct in your code

Checked 25 Aug 2026

Part of the Full-Stack Application Deployment cookbook