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.
React application hosting
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
Shared hosting for websites, email and PHP applications, with Virtualmin included.
See Web hosting →02Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
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.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
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
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.
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.
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.
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
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour 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.