Changelog

Database public access with IP restriction

Users can now enable external database access with fine-grained control. Previously, connections were either fully open or completely disabled, now you can allow or block access based on specific IPs or IP ranges.

We also introduced a new Networking tab under database, where you’ll now find the external connection toggle, IP restrictions, and connected apps.

Deployment updates log

You can now view application changes in the Deployments table. Each deployment shows when the updates went live, along with a small badge indicating the number of changes. Detailed information is available on the Deployment details page.

Create webhooks to receive service event notifications

You can now configure an endpoint to receive event notifications when changes occur in your apps, databases, or static sites.

Each webhook request includes an svl-signature header for verification, and failed deliveries are retried up to 12 times, with all attempts visible in the Event Deliveries view.

Initial supported event types include:

• APP_CREATE, APP_UPDATE, APP_DELETE, APP_DEPLOY
• DATABASE_CREATE, DATABASE_UPDATE, DATABASE_DELETE
• STATIC_SITE_CREATE, STATIC_SITE_UPDATE, STATIC_SITE_DELETE, STATIC_SITE_DEPLOY

Learn more in the documentation.

Pretty URLs for static sites

Static sites on Sevalla now support Pretty URLs, which automatically standardize URLs for cleaner paths and improved SEO.

When enabled, Sevalla will:

• Redirect paths like /about → /about/
• Rewrite paths like /about.html → /about/

This behavior helps ensure consistent URL structures and better caching performance across our CDN.

You can enable Pretty URLs in your project's Static Site > Settings > Redirects section.

_redirects file support for static sites

Static sites on Sevalla now support the _redirects file format. If your repository includes a _redirects file in its root, Sevalla automatically parses and applies your custom redirect rules.

Supported features include:

• Custom 404 pages: Add a 404.html page, and Sevalla will automatically serve it for missing paths.
• Force redirects: Use ! in your status code to override existing files, ensuring your redirect always takes effect.
• Splats: Use wildcards (e.g. /news/* → /blog/:splat) to match entire path segments.
• Placeholders: Dynamically capture path segments using variables like :slug or :id.
• Query parameters: Match redirects based on query strings (e.g. /store?id=:id → /blog/:id).

These additions make it easier to manage complex routing logic directly from your repository with no extra configuration required.

For single-page applications that rely on client-side routing, we recommend adding the rule /* /index.html 200 so that all paths correctly return index.html with a 200 status instead of a 404 on reload.