Cloud hosting for React and Vite projects # React hosting for React and Vite projects Build and deploy React.js or Vite projects from GitHub where supported. Review build settings, custom-domain options and current service availability. [Get started](https://panel.deplomo.com/signup)[React deployment guide](/guides/deploy-react) ## Why choose React hosting on Deplomo? Automated builds, SPA routing and cloud deployment for React teams. ### Git-based deployment Connect a Git repository and configure a deployment branch. Where supported, a commit or push can trigger a build and deployment; check the integration and workflow settings. ### Builds with Vite and modern package managers Configure projects using Vite, Webpack, npm, Yarn or pnpm where supported by the build environment. Build duration and dependency caching depend on project configuration and available tooling. ### Single-page app (SPA) routing For a React Router SPA, configure a server fallback to `index.html` so direct requests to client-side routes can load the app. Verify the hosting and routing settings for your project. ### Custom domains and automatic SSL certificates Connect a custom domain and configure DNS. SSL certificates are issued and renewed automatically via ACME where domain setup is supported; a platform subdomain may be available. ### Package registry access during builds Install npm dependencies and connect to external APIs using the credentials and network settings required by your project. External provider policies still apply. ## Frequently asked questions about React hosting Find answers about deployment, single-page app routing, Vite and custom domains. Does React hosting handle 404s when refreshing React Router routes? Are projects built with Vite and TypeScript supported? How do I configure React environment variables in `.env`? Can I connect a custom domain and issue an SSL certificate? What does the free React hosting plan include? ## A guide to React hosting and cloud deployment for single-page apps (SPAs) React is used for dashboards, interactive sites and web applications. Deploying a client-side React app typically involves building static assets and configuring routes. Check that the hosting package supports the build workflow and any server fallback your app needs. ### Why can traditional shared hosting be difficult to configure for React projects? With some cPanel or DirectAdmin setups, developers build locally and upload the `dist` or `build` folder through a file manager or FTP. Client-side routing may also need a rewrite rule such as `.htaccess`. The steps and available tools depend on the hosting provider. A cloud React host can automate parts of this workflow where Git integration is available. Connect a GitHub or GitLab repository, then configure the branch, package manager, Node.js version and build command. Routing and deployment behavior depend on the platform settings. ### How Vite fits into React development and builds Vite is a build tool used by many frontend teams, including projects that previously used Create React App. Configure the required Node.js version and package manager, such as npm or Yarn. Dependency caching may speed up repeat builds where available; build time depends on the project and environment. For a small SPA or a larger admin panel, choose a hosting package that supports the project’s Vite build and has suitable resource limits. Runtime performance depends on the app and its users’ devices. ### Compare React hosting, traditional shared hosting and a VPS The table summarizes common operational differences. Features and requirements vary by provider, package and project configuration.
| Feature | React hosting on Deplomo | Conventional shared hosting (cPanel) | Unmanaged VPS |
|---|---|---|---|
| Deployment method | Git integration and automated deployment may be available, depending on service settings | Manual upload of built files via FTP | Manual Nginx configuration, SSH cloning and deployment scripts |
| Handling React Router 404s | Configure a server fallback for single-page apps where supported | May require rewrite rules in `.htaccess` | May require `try_files` configuration in Nginx |
| Running the build in a cloud environment | Isolated builds with configured package access | Build support depends on the hosting package; check whether it can run `npm run build`. | Build environment and package access depend on your server configuration |
| Custom domains and certificates | Automation and included services vary by provider; review any plugin or license requirements | May require server extensions or separate licenses, depending on the provider | VPS deployments may require installing and maintaining Certbot on Linux |
| How pricing is calculated | Fixed monthly EUR packages with defined limits | Contract and refund terms vary by provider; review them before subscribing | Charges depend on the provider and selected plan; usage-based pricing availability varies |
| Availability and resource scaling | Container-based deployment; capacity and availability depend on the package, workload and configuration | Capacity under concurrent traffic depends on application resources and provider configuration | May require ongoing server administration and operations work |