React VPS HostingYour Front End and API on One Server
A React app is a set of static files and, usually, an API. On a VPS, NGINX serves the build with proper caching and routing while your Node.js, PHP or Python API runs next to it. We set up NGINX with HTTPS and the runtime your API needs.
Static hosting services are fine for a front end alone. Once you add an API, a database and background jobs, one server is simpler to run and to pay for.
01
Front end and API on one domain
Serve React at / and proxy /api to your back end, so there is no CORS setup and cookies just work.
02
Caching under your control
Long cache headers for hashed assets, no-cache for index.html and compression on everything.
03
Any back end beside it
Node.js, NestJS, Laravel, Django or FastAPI, with the database on the same server.
04
A flat monthly price
No per-seat or bandwidth tiers, with unlimited traffic in Europe and North America.
The stack
How a React App Is Served
React is built once into static files; NGINX serves them and passes API calls to your back end.
Request from a browser or app (HTTPS)
Front end
React build (Vite)
index.html plus hashed JavaScript and CSS from npm run build.
Web server
NGINX
Serves the build, falls back to index.html for client-side routes and proxies /api.
API
Your back end
Node.js, PHP or Python on a local port or socket.
Data
Your database
PostgreSQL, MySQL or MongoDB on localhost.
Worth knowing
Client-side routing needs try_files $uri /index.html so deep links work on refresh.
Cache /assets for a year (file names are hashed), but never cache index.html.
Environment variables in a React build are public: keep secrets in the API.
Need server-side rendering for SEO? Next.js runs as a Node server on the same kind of VPS.
What you can run
What You Can Run
Single-page applications
Dashboards and tools built with React Router or TanStack Router.
Admin panels
React Admin or Refine front ends over your API.
Front ends for headless back ends
React on top of Strapi, Directus or your own API.
Several front ends
Customer app, admin and marketing site on separate domains.
Staging copies
A build per branch on its own subdomain.
Static marketing sites
React-based sites built with Vite or Astro.
Shared hosting vs VPS
Outgrown shared hosting? A VPS has no shared limits.
Shared hosting is a good place to start. When a busy site keeps hitting its account limits, a VPS removes them.
On shared hosting
CPU, memory and processes are capped per account, so traffic spikes hit the ceiling.
You share the server with other sites.
No root access, and only the software the host supports.
Background workers, queues and WebSockets are limited.
On your own VPS
CPU, RAM and NVMe storage are dedicated to your server, not shared with neighbours.
Your plan's resources are yours, with no per-account caps to hit.
Full root and SSH access: install any software you need.
Run workers, cron jobs, queues and WebSockets freely.
A VPS is unmanaged: we install and secure it for you, then you run it. Prefer us to run everything? See managed hosting.
VPS Plans
VPS Plans for React Apps
Serving a React build takes very little; the plan is about your API, database and builds. VPS-1 suits most apps, VPS-2 if you build on the server and run a database.
VPS-1
Small websites, APIs, bots and development servers.
* Unlimited traffic in Europe and North America. In Mumbai, Singapore and Sydney a monthly allowance applies (VPS-1 500 GB, VPS-2/VPS-3 1 TB, VPS-4 3 TB), then speed is limited to 10 Mbps until the next month.
Prices exclude 18% GST, which is added to invoices for customers in India.
Sizing guide
Which Plan for Your React Project
NGINX serves static files with almost no CPU. Size for the API and database behind it, and for builds if they run on the server.
Recommended VPS plan for each React workload
Workload
Start with
Why
React front end only, built in CI
VPS-12 vCores · 4 GB RAM
Plenty for NGINX and several sites.
React plus an API and a database
VPS-24 vCores · 8 GB RAM
8 GB for the API, database and builds.
Busy app with background jobs
VPS-36 vCores · 12 GB RAM
More vCores for the API and workers.
Several apps and environments
VPS-48 vCores · 24 GB RAM
Staging and production side by side.
A starting point, not a limit: every plan upgrades in place, keeping your data, IP address and configuration.
Static Hosting Service or a VPS for React?
A static host serves the front end from a CDN. A VPS serves it next to the API and database it talks to.
Example shell commands; adjust paths, names and versions to your project.
Example commands; adjust names, paths and versions to your project. Deploying and maintaining your application is yours to do (or ask us for a quote).
Free one-time setup
Installed and Secured Before You Log In
The VPS is unmanaged: after handover the server is yours to run. Before that, our engineers
do the first setup once, free, so you start from a hardened server with React in place.
1
Choose a plan and location
Pick the resources you need and the datacentre closest to your users.
2
Tell us your React setup
Versions, database and domain: at order or right after.
3
We install and secure it
Server hardened, React installed and tested, HTTPS on your domain.
4
You take over with root
SSH access to a working server, ready for your code and data.
Your React setup
NGINX with HTTPS for your domain
A server block with client-side routing and asset caching
Node.js LTS for builds and Node APIs
Your API runtime and database, if you choose them at order
HTTP to HTTPS redirects and compression
Yours to run after handover
Ongoing server administration
Application maintenance and updates
Debugging your code
Migrating existing sites or data
Not included in the free setup, but we can quote for it.
No control panel by default: CloudPanel, HestiaCP or Virtualmin on request at no cost;
cPanel and Plesk need their own licence.
Under the hood
Platform Specs and Locations
The same KVM platform on every plan; only the CPU, RAM, storage and port speed change.
VPS platform specifications
Virtualisation
KVM with reserved vCores and RAM
Storage
NVMe SSD on every plan
Network
Dedicated IPv4 and IPv6, 500 Mbps to 3 Gbps per plan
Operating systems
Ubuntu 26.04, 24.04 and 22.04 LTS · Debian 13, 12 and 11 · AlmaLinux · Rocky Linux · Fedora · FreeBSD
Access
Full root over SSH, key-based login
Backups
Automatic daily backup of the previous 24 hours; snapshots and longer retention on request
Protection
Always-on anti-DDoS mitigation
Availability
99.9% uptime SLA
Secured before we hand it over
Non-root sudo user created for daily work
SSH key login, password login for root disabled
Firewall (UFW) open only for the ports you use
Fail2ban blocking repeated login attempts
Automatic security updates enabled
Free Let's Encrypt SSL on your domain
Timezone, swap and hostname configured
Asia-Pacific
Mumbai
Singapore
Sydney
Europe
London
Limburg
Roubaix
Gravelines
Strasbourg
Milan
Warsaw
North America
Beauharnois
Availability per location changes with demand; we confirm your location before setup. In Mumbai, Singapore and Sydney each plan includes a monthly traffic allowance (VPS-1 500 GB, VPS-2 and VPS-3 1 TB, VPS-4 3 TB); beyond it, speed is limited to 10 Mbps until the next month.
Who it's for
Who a React VPS Suits
Front-end developers with an API
You want the React app and its back end deployed together.
Product teams
One server for the app, the API and the admin panel.
Agencies
Client front ends on separate domains, on one server.
Running it well
Security and Performance for React Apps
Security
Treat everything in the bundle as public: no API keys in front-end code.
Set security headers in NGINX: Content-Security-Policy, HSTS and X-Content-Type-Options.
Authorise every request in the API, never only in React.
Keep build dependencies updated with npm audit.
Performance
Long cache headers on hashed assets, no-cache on index.html.
gzip text assets in NGINX.
Code-split routes with lazy loading.
Serve images in modern formats at the size they are shown.
React VPS FAQs
Questions Before You Deploy
Not covered here? Ask an engineer before you order.
Not for a front end alone. A VPS makes sense when you also run an API, a database or background jobs and want them on one server with one bill.
With a try_files rule that falls back to index.html, so refreshing /dashboard/settings loads the app instead of a 404. We configure this when we set up your site.
Yes. NGINX serves the React build and proxies /api to your Node.js, PHP or Python back end on a local port. Tell us the runtime at order and we install it.
Only if search engines or link previews must see content without JavaScript, or first-load speed is critical. For that, Next.js runs as a Node server on a VPS.
The free setup prepares NGINX, HTTPS and your runtimes. Building and uploading the app is yours to do, by rsync or from your CI pipeline.
Any build that outputs static files works. Create React App is deprecated, so new projects usually start with Vite or a framework.