Skip to main content
A Remix 3 application runs on Sevalla as an application: Nixpacks installs it from your Git repository, and the web process runs the starter’s server.ts with Node.js, which listens on the port that Sevalla sets in the PORT environment variable. Remix 2 applications continue as React Router: see Deploy a React Router application.

​
Before you begin

  • A Sevalla company with a payment method, and a GitHub, GitLab or Bitbucket account for the repository. See Git providers.
  • Node.js 24.3 or later on your computer. Remix 3 needs it.

​
Create the project

Create a project with the Remix CLI and install its dependencies:
The starter comes with a .gitignore and the scripts Sevalla uses. Its start script runs the TypeScript server directly, with no build step:
package.json

​
Prepare the project for Sevalla

The starter is ready to deploy:
  • server.ts takes its port from PORT, which Sevalla sets to the web process’s port (8080 by default), and server.listen(port) listens on all network interfaces. Without PORT, it uses port 44100.
  • Nixpacks, the default build strategy, starts the web process with npm run start. The project has no build script, so Nixpacks skips the build step.
  • The starter’s engines field makes Nixpacks install Node.js 24 (24.10.0) instead of its default, Node.js 18.
Run npm start and open http://localhost:44100 to check the server locally. Then commit everything, including package-lock.json, and push it to your Git provider:

​
Deploy to Sevalla

1

Create the application

In the sidebar, click Applications, then click Create > Application. Under Source, click Private repository, then choose the Git provider, the Repository and the Branch. Under Location, choose a Data center. Keep the Size at H1 or choose a larger one, then click Create application. The application opens on its Overview tab with the status Not deployed yet: creating an application doesn’t deploy it.
2

Deploy

Click the Overview tab, then click Deploy now under Recent deployments. Check the Branch and click Deploy.
3

Turn on auto-deploy

To deploy every push to the branch automatically, click the Settings tab, then click Update auto-deploy in the Auto-deploy section. Turn on Auto-deploy and click Update auto-deploy. See Deployments.

​
Verify the deployment

  1. On the Deployments tab, wait for the deployment’s status to change to Deployed. The application’s status next to its name changes to Running.
  2. Click the domain under the application’s name, for example storefront-x7k2m.sevalla.app. The Remix starter’s home page opens.
The application header with its name, Running status, repository, branch and the domain that opens the applicationThe application header with its name, Running status, repository, branch and the domain that opens the application
If the deployment fails, open it on the Deployments tab and read its build log, then see Troubleshoot builds and deployments. If the server doesn’t start, read the application’s runtime logs.

​
Deploy changes

With Auto-deploy on, every push to the branch starts a deployment; otherwise, click Deploy now for each change. Each deployment builds the image, then replaces the web process’s instances. See Deployments.

​
Store sessions and files outside the instance

Remix’s memory session storage and local upload folders only work while one instance runs and until the next deployment. Use Remix’s Redis session storage with a Sevalla Redis database, and its S3 file storage with Sevalla object storage, before you run more than one instance.

​
Deploy a React Router application

Remix 2 continued as React Router, so an application upgraded from Remix 2, or created with create-react-router, uses React Router’s server:
  • npm run build runs react-router build, and the start script runs react-router-serve ./build/server/index.js. react-router-serve takes its port from PORT and listens on all network interfaces.
  • engines.node makes Nixpacks install Node.js 24 instead of Node.js 18. React Router 8 needs Node.js 22.22 or later.
  • Nixpacks doesn’t treat the project as a single-page app, because it depends on @react-router/node.
Commit and push the project, then follow the steps in Deploy to Sevalla. The starter’s home page opens on the application’s domain. A Remix 2 application that still uses @remix-run/* packages deploys the same way: its start script runs remix-serve, which also reads PORT.

​
Add a custom domain

To serve the application from your own domain, such as shop.example.com, add the domain on the application’s Domains tab and create the DNS records that Sevalla shows. Custom domains need a web process larger than H1, so scale the web process first. See Custom domains.

​
Connect a database

Create a database in the same location as the application, then connect the application to it with Add environment variables to the application turned on. Sevalla adds DB_URL, DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME and DB_PASSWORD to the application (what each one holds), and they apply at the next deployment. Read them in server.ts or in actions with process.env.DB_URL.