Changelog

Preview deployments now build in parallel#

Static site pull request previews no longer wait in line behind each other. Previews for different branches now build at the same time, and they run alongside your production deployments instead of queueing behind them. Pushes to the same preview branch still run one after another, so the latest commit on a branch is always the one you end up previewing.

Production deployments are unchanged. They still run one at a time per site, so the most recent deployment is always the one that goes live.

Preview builds also no longer affect your site's status. A failed or in-progress preview will not mark your site as failed or block updates to the site.

Maintenance mode for applications#

You can now put an application into maintenance mode from Settings > Maintenance mode. While it is on, every visitor on every domain of the application sees a maintenance page with a 503 status and a Retry-After header instead of your application. The application keeps running and you can still deploy, so it is ideal for database migrations and other planned work.

By default we serve a simple maintenance page. Point Maintenance page URL at any HTTPS page, for example a free Sevalla static site, and we serve that page's content on your own domain instead.

Maintenance mode is also available through the API - see Get maintenance mode and Update maintenance mode. Read more in the Settings docs.

Database Studio now works with Redis and Valkey#

The Database Studio is no longer SQL only. Open Studio on any Redis or Valkey database and you get a full key-value workspace - no redis-cli or third-party GUI needed.

Browse the keyspace - scan keys with pattern and type filters, switch between a flat key list and a namespace tree, and select multiple keys to delete them or set their TTL in one go. A database selector lets you move between logical databases.

Edit every key type - dedicated editors for string, hash, list, set, sorted set, stream, and JSON keys, with JSON highlighting, bracket matching, and folding in the value editor. Add, rename, and delete keys, and manage TTLs with a live countdown.

Run commands - a redis-cli style console with autocomplete, command history, and an inline command reference.

Inspect the server - an overview of memory, clients, throughput, and keyspace, every INFO field in a searchable view, the slow log, and the list of connected clients.

You can also export the loaded key list to .csv or .json. See Database Studio for more.

Sevalla is moving to Oracle Cloud Infrastructure#

Starting in early September, Sevalla will begin gradually moving workloads from Google Cloud Platform to Oracle Cloud Infrastructure.

The migration happens in waves, beginning with static site builds. For most customers, no action is needed.

Read the full announcement for migration details, expected impact, location changes, IP changes, and FAQs.

More control over how cron jobs run#

Cron jobs now expose two Kubernetes scheduling controls, so a run that hangs can no longer quietly wedge your schedule - the exact situation that used to leave a cron job stuck after a deploy until you recreated it.

Concurrency policy - decide what happens when a run is triggered while the previous one is still going:

• Forbid (default) - skip the new run until the current one finishes. Nothing changes for your existing cron jobs.
• Replace - cancel the still-running job and start a fresh one. This is the self-healing option: a stuck run gets cleared on the next tick instead of blocking every run after it.

Max run time - optionally cap how long each scheduled run may take. If a run exceeds it, Kubernetes terminates it. Leave it empty (or set 0) for no limit.

Both settings live in your process settings and through the API - see Create process and Update process. They apply to cron processes only.