Changelog
Keep yourself informed about the most recent additions and improvements
we’ve made to Sevalla.
Cron run history
Sevalla now records every run of a cron job, scheduled or started with Run now, and keeps it for 30 days. On the Processes tab, a cron job's card shows its last 30 runs at a glance, and its status is the status of its latest run: Running, Succeeded or Failed. Click Run history to see every run with when it was due, how long it took, how many times it was retried and why it failed (its exit code, its max run time, or replaced by the next run). Click a run's time to open its logs.
The List cron runs API operation returns the same history. See Check cron runs.
Ingot, Sevalla's own builder
New applications and preview apps from Git now build with Ingot, Sevalla's own builder. Ingot detects your language, framework, language version and package manager, writes a production Dockerfile and builds it: on official language images, from your lock file, running as a non-root user, with the same Dockerfile for the same commit. It supports Node.js, Bun, Deno, Python, PHP, Ruby, Go, Rust, Java, .NET, Elixir, Gleam, Zig, C and C++, static sites and shell scripts. Override what it detects with an ingot.json file or INGOT_* environment variables.
Existing applications keep their build strategy. To switch one, click Update build strategy on its Settings tab and choose Ingot; Move to Ingot lists what to check first. Nixpacks is deprecated, and applications that build with it keep working.
Applications that build with Ingot or their own Dockerfile also keep a Dockerfile history: every Dockerfile they were built from, which one is running, and what changed between any two. A deployment's new Dockerfile tab shows the file its image was built from, and the List Dockerfiles and Get Dockerfile API operations return the same history.
Preview apps and disks in the API and CLI
You can now set up preview apps without the dashboard. The Enable pipeline preview and Update pipeline preview settings API operations take the preview app settings as preview_app: location, build, hibernation, processes with their disks and TCP proxies, and environment variables. Create preview app creates a preview app for a branch or pull request and starts its first deployment. See Preview apps.
Disks have their own operations too: List disk resource types, Attach or update process disk and Detach process disk, with the same rules as the dashboard. See Persistent storage.
The CLI has matching commands: sevalla pipelines preview create-app, --preview-app on sevalla pipelines preview enable and update, sevalla apps processes disk update and delete, and sevalla resources disk-types.
Patched Node.js for Nixpacks builds
Nixpacks builds install Node.js 22.23.4 and 24.22.1, the releases that fix CVE-2026-111497 and 9 other vulnerabilities from the Node.js security release of Oct 21, 2026. CVE-2026-111497 is an out-of-bounds write in the Brotli decoder that can let an attacker run code. This covers Nixpacks 1.29, 1.39 and 1.41, and the Node.js that Nixpacks adds to PHP and Ruby applications.
When the repository doesn't set a Node.js version, Nixpacks installs Node.js 22 instead of Node.js 18. Node.js 18 and 20 are end of life and get no fix: an application that pins one of them keeps it, so pin 22 or 24 instead, with engines.node in package.json or NIXPACKS_NODE_VERSION. Node.js 24 needs Nixpacks 1.41: on 1.29 and 1.39, a request for 24 builds with Node.js 22. See Set the language version.
To upgrade a running application, redeploy its latest deployment with Skip build cache selected. This change covers Nixpacks builds only: Railpack, Buildpacks and Dockerfile builds install Node.js themselves.
Deploy a specific commit
The Manual deploy sheet of a Git application has a new Commit field, so you can deploy any commit of a branch, not only its latest one. Paste the commit's full SHA, or its link from GitHub, GitLab or Bitbucket, and Sevalla builds that commit with the application's current settings and environment variables. Browse commits opens the branch's commits in your Git provider to find one. Leave the field empty to deploy the branch's latest commit, as before.
The Trigger deployment API operation takes the same commit as commit_sha. See Deploy your application.