Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

React application hosting

React application hosting in Canada

A static React build and a server-rendered application need different hosting. Choose around the build output and any backend services your project uses.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

Runtime and processes

Check React applications where the first decision is whether the output is a static build or a server-rendered application that actually needs a persistent runtime.

02

Data to protect

Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.

03

Network access

List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.

04

Deployment and maintenance

Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.

Field guide

Static build or server runtime, decided first

A React app built with Vite or a similar tool produces static files that any web server or shared hosting can serve, with no Node process at runtime. Server side rendering through a framework such as Next.js changes the requirement completely: now you need a persistent Node process, memory for rendering, and process supervision.

The classic failure for static React apps is routing: direct visits to client side routes return 404 because the server looks for a file that does not exist. Configure a fallback that serves index.html for unknown paths, and set long cache lifetimes only on hashed asset filenames, never on index.html itself.

01

Route fallback rule

Add a rewrite that serves the main HTML entry file for paths that are not real files. Test by loading a deep link directly, not by clicking through the app.

02

Cache header split

Give hashed JavaScript and CSS files a one year cache lifetime and give the main HTML entry file no cache or a short lifetime. This pairing lets new deploys appear immediately while assets stay cached.

03

Environment variable timing

Build time variables are baked into the JavaScript bundle and visible to every visitor. Keep secrets in a backend service, never in the front end build.

Planning

Access, backups and handover

Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.

Free guide

React application hosting in Canada: planning checklist

Use the detailed checklist to plan setup, access, migration and recovery with your team.

Download PDF →
Help choosing

Tell us about your project.

Send us the software you use, your storage needs and your launch or moving date.

Ask about hosting

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move