Changelog

Usage alerts#

Set spending limits for your company or individual projects and get notified by email when usage crosses your chosen thresholds.

You can configure:

• A spending limit in USD.
• One or more threshold percentages of the limit (up to 10 per alert), for example 50%, 75%, and 90%.
• One or more email recipients.

Each threshold fires once per billing period, and thresholds reset automatically when the next period starts. See the usage alerts documentation for details.

Custom headers for static sites#

You can now add custom HTTP headers to your static sites by including a _headers file in your repository's root directory. Sevalla parses the file and applies matching header rules to responses automatically.

Supported features include:

• Wildcard patterns - Apply headers to broad path matches like /* or /assets/*.
• Placeholders - Match single path segments with :name syntax for dynamic routes.
• Rule combining - When multiple rules match a path, their headers are merged automatically.
• Common use cases - Easily configure security headers, caching policies, CORS rules, and more.

Certain platform-managed headers (e.g., Content-Encoding, Server, Transfer-Encoding) are restricted and cannot be overridden. See the headers documentation for the full list and detailed examples.

Project Admin role for user management#

Project Admins can manage user access within their projects, giving scoped control over who can access project resources without needing company-level permissions.

As a Project Admin, you can:

• Invite users -- Add new or existing users directly to your project with a project-admin or project-developer role.
• Manage project roles -- Promote, demote, or remove users within your project.
• Manage service roles -- Grant or revoke access to apps and databases that belong to your project.
• Convert access levels -- Move a single-project user between project-level and service-level access within your project scope.

Project Admins cannot modify company-level users, or affect users with access outside their project.

Deploy paths for static sites#

Deploy paths are now available for static sites, giving you fine-grained control over which file changes trigger a deployment. This is especially useful for monorepos or repositories where not every commit should result in a new deployment.

In the Deploy section of your static site settings, click Update deploy paths and choose between:

• Allow paths - Only trigger deployments when changed files match specific glob patterns (e.g., /src/frontend/**).
• Ignore paths - Skip deployments when all changed files match specific glob patterns (e.g., **/*.md).

Deploy paths can also be managed via the Sevalla CLI, the Terraform Provider, and the REST API (available on the Get, Create, and Update static site endpoints).

Update source for static sites#

You can now change the source repository for your static sites directly from the settings page - no need to delete and recreate the site.

Click Update source in the Deploy section of your static site settings to switch between a private or public Git repository, change the Git provider (GitHub, GitLab, or Bitbucket), or point to a different repository URL.