Changelog

Purge your CDN cache in one click#

Serving stale content after a deploy or an upload? You can now clear it yourself — no need to wait for the cache to expire or reach out to support.

We've added a new Cache section to the settings of both static sites and object storage. Head to Settings → Cache and hit Purge cache to instantly clear the cached assets served from our global CDN.

• Static sites — purges the CDN/Edge cache for your site. Reach for it right after a deploy when updated assets aren't showing up yet.
• Object storage — purges the CDN cache for your bucket, so freshly uploaded or replaced objects are served immediately.

The purge takes effect right away, and you'll get a confirmation the moment the cache is cleared. Available to anyone with update access to the service.

Faster deploys with clearer upload progress#

We've made a round of optimizations to how static sites are deployed, and your deploys are now noticeably quicker. Across 264 sites, deploy time dropped by 32.84% on average - the typical deploy went from 82.51s down to 56.6s. Nothing changes in how you deploy. Push your code as usual and the speedup is automatic.

Deploy logs are clearer, too. You'll now see a live upload progress bar so you can follow exactly how far along your upload is, instead of waiting on a silent step. Each deploy prints the total number of files being uploaded, a progress bar that advances with file count and total size, and a closing summary with the final count, size, and how long it took. If any files fail, they're clearly flagged.

⬆️  Uploading 1842 files...
   [████████████░░░░░░░░]  60% · 1105/1842 files · 24.3 MB
✅ Uploaded 1842 files (41.2 MB) in 18.7s

AI support agent#

You can now chat with an AI support assistant directly from the Sevalla dashboard. The assistant answers questions about the platform and, with your permission, about the services running in your account - it can check deployment status, error logs, database backups, and more, and help you troubleshoot issues. You can also attach screenshots to your messages.

To enable it, go to Help > AI support, review the data processing terms, and choose what the assistant can access. Permissions work like API key permissions: pick a predefined role or scope custom permissions to specific resources. Once enabled, every member of your company can chat with the assistant, so grant only the access you are comfortable exposing to all members. Only company owners and admins can enable AI support or change its permissions.

A few things worth knowing:

• The assistant is powered by Anthropic Claude. Prompts and account data are sent to Anthropic only to generate responses and are not used to train their models.
• Enabling AI support creates a dedicated, managed API key for your company. Disabling it revokes the key immediately.
• The assistant hands the conversation over to our human support team whenever needed.
• Without account access, the assistant still answers questions using the Sevalla documentation.

Bandwidth chart in analytics#

Application and static site Analytics tabs now include a Bandwidth chart alongside the existing request rate, response time, and status code charts. Use it to see how much traffic your service is serving over time and to spot bandwidth spikes.

The same timeframe and filter controls that apply to the other charts apply to bandwidth as well.

Git LFS support#

Applications and static sites can now pull LFS-tracked files when deploying from repositories that use Git Large File Storage (LFS). Large assets tracked by LFS - such as images, videos, datasets, or model files - are fetched during the build. Previously, deploys from LFS repositories succeeded but only the LFS pointer files were checked out, not the actual file contents.

Git LFS is enabled by default. You can disable or re-enable it from the application or static site Settings tab. The same flag is available through the public API as git_lfs_enabled on update application and update static site.

You can also toggle the flag with Sevalla CLI v1.10.0:

sevalla apps update {id} --git-lfs-enabled true
sevalla static-sites update {id} --git-lfs-enabled true

And in the Terraform provider v1.1.0.