Sevalla Changelog #0086 New Website, New Improvements

Establishing connection…

Signal detected.

Link established.

Baud here with a 56k Sevalla changelog transmission.

Seven product updates shipped over the last two weeks. But before we get to those, there's another change worth mentioning.

A new front door for Sevalla#

This week we launched the new Sevalla website.

The update isn't about a new color palette or a different navigation menu. Although, we did add a Use case menu item.

It's about clarity.

Over the last year, Sevalla has become a much more capable platform. We've added pipelines, preview environments, load balancers, API automation, MCP support, RBAC, and a long list of production-focused improvements. The platform evolved. The website didn't always keep up.

The new site does a better job explaining who Sevalla is for and why it exists.

Sevalla is built for teams running production applications that want the benefits of cloud infrastructure without becoming infrastructure operators. Teams that understand AWS, Google Cloud, or Azure, but would rather spend their time shipping products than managing cloud services.

The platform keeps getting more capable, and now the website now tells that story more clearly.

And the last two weeks brought seven updates that reinforce the same direction.

Less operational work. More time building.

Quick links to the updates:

• Bandwidth charts in analytics
• Git LFS support
• Restart a database
• Header-based conditions in redirects
• Restore a backup to a different database
• Delete non-empty object storage
• Roll object storage secrets

Better visibility into real traffic#

Bandwidth charts for applications and static sites#

Request counts tell you how busy a service is. They don't tell you how much data it's actually serving.

Applications and static sites now include bandwidth charts alongside request rate, response time, and status code analytics.

This makes it easier to:

• Spot bandwidth spikes before they become surprises
• Understand traffic patterns over time
• Correlate traffic volume with performance changes
• Identify unusually large responses or asset delivery issues

If you're responsible for production workloads, visibility into traffic volume matters just as much as request volume.

Deploy repositories that use Git LFS#

Git LFS support#

Applications and static sites now automatically pull Git LFS-tracked files during deployment.

Previously, deployments from Git LFS repositories completed successfully, but only the pointer files were checked out. Teams still needed workarounds to access the actual assets.

Now Sevalla fetches the real files during the build process.

This is especially useful for projects that include:

• Large media assets
• Machine learning models
• Datasets
• Design resources
• Generated artifacts

Git LFS support is enabled by default and is available through the dashboard, API, CLI, and Terraform provider.

Infrastructure should adapt to your workflow. Your workflow shouldn't adapt to infrastructure.

More control over production databases#

Restart databases on demand#

Sometimes a database simply needs a clean restart.

You can now restart managed databases directly from the Sevalla dashboard, API, or CLI.

The restart process safely stops and starts the database while preserving stored data.

For production teams, this removes another operational task that previously required support involvement or manual intervention.

When something needs attention, you can handle it yourself and move on.

Restore backups into a different database#

Database backups are no longer limited to restoring over the original database.

You can now restore a backup into a different database instance.

This makes several common workflows significantly easier:

• Clone production into staging
• Create test environments using real data
• Validate backup integrity
• Recover data into a fresh instance without touching production

Instead of treating backups purely as disaster recovery tools, teams can now use them as part of their everyday development workflow.

Better static site routing logic#

Header-based conditions in _redirects#

Static site redirects can now evaluate incoming request headers.

This allows routing decisions based on client behavior rather than URL patterns alone.

For example:

• Serve alternate content formats
• Route requests based on client capabilities
• Support advanced documentation workflows
• Create more flexible content delivery patterns

The result is more control without introducing additional infrastructure layers.

Less object storage housekeeping#

Delete non-empty object storage buckets#

You no longer need to manually empty a bucket before deleting it.

Delete the bucket and Sevalla automatically removes the contents as part of the process.

Small change.

Large reduction in operational busywork.

Roll object storage secrets without downtime#

Security tasks often create operational risk.

Rotating credentials shouldn't.

Object storage credentials can now be rotated while allowing existing credentials to remain valid during a configurable grace period.

This enables:

• Safer credential rotation
• Better security hygiene
• Zero-downtime migrations
• Reduced risk during key updates

Production systems stay online while your security posture improves.

Transmission complete#

Seven updates focused on removing friction from deployment, database management, storage operations, and production visibility.

More improvements on the way.

Awaiting next transmission.

Link closed.