qwik build, and the web process runs the adapter’s serve script, node server/entry.node-server, which listens on the port that Sevalla sets in the PORT environment variable.
At a glance
Environment variables
The application needs no environment variables of its own. Sevalla setsPORT for the web process.
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 or later on your computer.
Create the project
Create a project from Qwik’sempty starter, which includes Qwik City’s routing, and install the dependencies:
src/entry.node-server.tsx, a server built on Node.js’s http module, and two scripts: build.server, which npm run build runs, and serve, which starts the server. The project comes with a .gitignore.
Prepare the project for Sevalla
Stop the server gracefully
When Sevalla replaces an instance, during a deployment for example, it sendsSIGTERM. The adapter’s server doesn’t handle it, so requests in progress would be cut off. At the end of src/entry.node-server.tsx, after server.listen(...), close the server on SIGTERM:
src/entry.node-server.tsx
server.close() stops accepting connections and lets the requests in progress finish, then Node.js exits.
Pin the Node.js version
Qwik’s starter lists every package in
devDependencies, including the ones the server imports when it runs, so Ingot keeps the devDependencies in the image. The build plan’s DevDependencies row says so.
Run npm run build && npm run serve and open http://localhost:3004 to check the production build locally. Then commit everything and push it to your Git provider:
Deploy to Sevalla
These steps build with Ingot. To build from your own Dockerfile instead, see Deploy with a Dockerfile.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
-
On the Deployments tab, click the deployment. Its Build log shows Ingot’s build plan: Node.js 24 from
engines.node, npm frompackage-lock.json, Qwik City frompackage.json, and the start command from theservescript.Build log - Wait for the deployment’s status to change to Deployed. The application’s status next to its name changes to Running.
-
Click the domain under the application’s name, for example
storefront-x7k2m.sevalla.app. The starter’s page shows Hi 👋, rendered by the server.


Qwik City has no server adapter, so its build makes nothing to run means the project has no adapter: run npx qwik add node-server --skipConfirmation=true, commit and push.
Deploy with a Dockerfile
Ingot needs no Dockerfile. Write one when you want full control of the image: the base image, the system packages and every layer. The server build imports one package at runtime,undici, which the starter lists in devDependencies. Move it to dependencies, so the Dockerfile can leave every other development package out of the image:
Dockerfile and a .dockerignore to the root of the repository:
Dockerfile
.dockerignore
Dockerfile and adds your .dockerignore patterns to its own, so you can keep both files in a repository that builds with Ingot. Then switch the application to the Dockerfile build strategy:
1
Choose the Dockerfile build strategy
On the application’s Settings tab, in the Build strategy section, click Update build strategy. Click Dockerfile, keep the Dockerfile path
Dockerfile and the Docker context ., then click Update build strategy.2
Deploy
Click the Overview tab, then click Deploy now under Recent deployments. Check the Branch and click Deploy.
📦 Building and pushing docker image using Dockerfile... instead of Ingot’s build plan, and its Dockerfile tab shows your file. When the status changes to Deployed, the domain shows Hi 👋. If the runtime logs show Cannot find package 'undici', undici is still in devDependencies: run npm install --save-prod undici, commit and push. See Dockerfile for build arguments and private base images.
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, and the old instances finish their requests before they stop. See Deployments.Use environment variables
Add configuration on the application’s Environment variables tab. Server code reads it withprocess.env at runtime; variables apply at the next deployment. See Environment variables.
Add a custom domain
To serve the application from your own domain, such asshop.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.
Deploy with the API
The Sevalla API makes the same deployment as Deploy to Sevalla without the dashboard. Run the steps in order in one shell: each step is one API call, and saves the IDs that later steps need in shell variables. Each step also names the CLI command and the MCP server tool that do the same. A variable that holdsnull means the call failed: run the curl command without its jq part to read the error.
You need:
- An API key with the Company developer role, or the
APP:CREATE,APP:READandAPP:UPDATEpermissions, in theSEVALLA_API_KEYenvironment variable. The CLI reads the key fromSEVALLA_API_TOKEN. - The repository on GitHub, GitLab or Bitbucket, and a Git account that can read it connected to your Sevalla user, which only the dashboard can do. See Git providers. Creating the application checks the access: if Sevalla can’t read the repository, the call returns
400withCannot access repository https://github.com/acme/storefront: Repository not found or you don't have access., followed by where to grant the access. curlandjq.
1
Find the location
List clusters (CLI:
listClustersV3) returns every location with its id, its name in display_name and its region ID in location. Pick one by its region ID, here eu-frankfurt-1 for Frankfurt, Germany. Locations lists them all.sevalla resources clusters. MCP: get_platform_options.2
Create the application
Create application (CLI:
createApplicationV3) creates the application with the Ingot build strategy and a web process, and doesn’t deploy it.sevalla apps create --name storefront --cluster "$CLUSTER_ID" --source privateGit --git-type github --repository https://github.com/acme/storefront --branch main. MCP: create_application with deploy set to false.3
Find the web process
List processes (CLI:
listProcessesV3) returns the web process that Create application added:sevalla apps processes list --app-id "$APP_ID". MCP: get_application, in processes.4
Find the H1 size
The API creates the web process with the S1 size, where the dashboard picks H1. List process resource types (CLI:
listProcessResourceTypesV3) returns the ID of each size:sevalla resources process-types. MCP: get_platform_options.5
Set the web process size
Update process (CLI:
updateProcessV3) sets the size, which applies at the first deployment:sevalla apps processes update "$WEB_ID" --app-id "$APP_ID" --resource-type "$H1_ID". MCP: scale_process with size_id, and apply_now set to false.6
Turn on auto-deploy
Update application (CLI:
updateApplicationV3) with auto_deploy deploys every push to the branch:sevalla apps update "$APP_ID" --data '{"auto_deploy":true}'. MCP: sevalla_api_update with updateApplicationV3, the application ID as path_params.id and the same body.7
Choose the Dockerfile build strategy
Skip this step to build with Ingot. To build from the Dockerfile instead, Update application (CLI:
updateApplicationV3) sets the build strategy:sevalla apps update "$APP_ID" --data '{"build_type":"dockerfile","dockerfile_path":"Dockerfile","docker_context":"."}'. MCP: sevalla_api_update with updateApplicationV3 and the same body.8
Deploy
Trigger deployment (CLI:
triggerDeploymentV3) deploys the latest commit of the branch:sevalla apps deployments trigger "$APP_ID". MCP: trigger_deployment.9
Wait for the deployment
Get deployment (The loop asks every 15 seconds, for up to 30 minutes, and keeps asking through an empty or failed reply.
getDeploymentV3) returns the deployment’s status: waiting, inProgress, then success, failed, cancelled or skipped. Poll it until the deployment ends:success means the application is deployed. CLI: sevalla apps deployments get "$DEPLOYMENT_ID" --app-id "$APP_ID". MCP: get_deployment.10
Read the build log
Get application deployment logs (With a Dockerfile, the log shows
getApplicationDeploymentLogsV3) returns the build log, one line per entry. With Ingot, the Start row of the build plan shows the start command:📦 Building and pushing docker image using Dockerfile... in place of the build plan. When a deployment fails, the end of this log says why. CLI: sevalla apps deployments logs "$DEPLOYMENT_ID" --app-id "$APP_ID". MCP: get_deployment_logs.11
Check the application
List application domains (CLI:
listApplicationDomainsV3) returns the application’s domains. Request the application on its domain:sevalla apps domains list --app-id "$APP_ID". MCP: get_application, in domains.